Relatiive Path problem when using JSP:include in web portlet

Question

Hi
I am using Oracle Portal 9.0.2, and thus OC4J as the J2EE platform.
I have created a JSP web portlet that is supposed to inlude a specific static html file, which name is passed to it using a portlet parameter. It works, but I had to create a symbolic link from the applicable J2EE applications's htdocs directory in order to access the content:
/j2ee/OC4J_Portal/applications/<application>/htdocs/<portlet>/content/
where /content/ is a symbolic link to another directory altogether.
I can then access the content from within the portlet with a JSP include tag that looks like :
docPath = "/htdocs/<portlet>/html/"+doc_path;
%>
<br>Include:
<jsp:include page="<%=docPath%>" flush="true"/>
I would like to access the content using the JSP include without having to use the symbolic link. Is there a way to do this. I tried using an Apache alias, but that did not work.
Regards
Harry

Answer 1

Hi
Thanx
In the end we build up a static URL to the document to be included using:
String contentLocation="content/";
docPath = contentLocation+getAdditionalDocPath();;
out.println("docPath="+docPath);
String docPathAndName = portletRequest.getParameter("doc_path");
%>
<!--
This java script function calls the display content page with the
page parameter doc_path (which is in return passes it to the display
content portlet) in order to retrieve and display specific document
with a JSP:include tag
-->
<script language="JavaScript">
function generateSectionPath(docName) {
this.location="http://<%=portletRequest.getServerName()%>:<%=portletRequest.getServerPort()%>/pls/portal/url/page/<%=getPageGroup()%>/content?doc_path="+"<%=docPath%>"+docName;
<script language="JavaScript">
function generateRelativePath(docName) {
this.location="http://<%=portletRequest.getServerName()%>:<%=portletRequest.getServerPort()%>/pls/portal/url/page/<%=getPageGroup()%>/content?doc_path="+docName;
</script>
<br>Include:
<%
if (portletRequest.getParameter("doc_path") == null) {
out.println("Error - no doc path specified");
} else { 
try { %>
<jsp:include page="<%=docPathAndName%>" flush="true"/>
<% } catch (Exception e) {
out.println("Error retrieving document:"+e.toString());
} // end if
%>
Each link from one included HTML file to another becomes a JS function that points the browser to the portal page that includes the portlet that includes thwe JSP that has the include tag to include the html document that is to be displayed.
The current relative path the the html document (from a predefined root in the file system that is symbolically linked to the same directory as where the including JSP lives) is stored in a session variable, and appended to the document name that is passed to the page.
If a full document path, as opposed to just the name, is stored, that no appending is done. However, the path is stripped out and stored in a session variable.
Ths thing is, sometimes a document name, and sometimes a path is passed to the page. Therefore the requirement to know the path when it is not available. A name only will always be passed subsequent to a request for a document with the full path specified, therefore the session variable mechanism works.
Thanx for the input
Harry