Apparently,
The page attribute (as in <jsp:forward page=���/> is
interpreted relative to the location of the current page if
it does not start with /. In other words the path is page-
relative. You can refer to pages in other directories
by /dir1/page1.jsp or ../dir1/page1.jsp or
dir1/page1.jsp. If starting with /, path is appended on
the end of the app dir (/dir1/page1.jsp will become
{tomcat_home}/webapps/yourapp/dir1/page1.jsp)
If your passing control onto beans, if I understand
correctly after you put your package in
{tomcat_home}/java, you access it by qualifying the full
package name, e.g.
com.xyz�.beans.someFunc.SomeBean.
Hope this helps,
Mike
>my web app directory structure is as follows:
>
>webapps/myapp/..........
>
>If I have a jsp and a bean in the root directory, and
my bean refers to >a file without a full path(ie. just the
file name, no absolute or >relative path), where does it
loook for the ?
>WAIT.........
>This happens in jsp/servlets AND beans. With jsp
servlets the default >directory should be the root
directory of the app. The bean however >seems to look
for a file with an unqualified path in the
>/tomcat/bin/directory.
>
>I just want some rules of thumb to follow when I am
using beans and >jsp/servlets that read and write files.
How should I refer to these >external files. Where are
their default directories in the context I >mentioned
above?
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
