Section 2.2.1 of the JSP 1.2 spec states that if the url path starts with
"/" is is interpreted by the application to which the JSP page belongs. When
it doesn't start with "/", it is interpreted relative to the current JSP
page. This final path is interpreted through the ServletContext object.
The uribase is used for the relative uri references. If it does not exist,
it is derived from the location of the file relative to the declared or
derived value of uriroot.
Justy
----- Original Message -----
> Hi,
>
> the JSP engine behaves quite interestingly when it generates the classname
> for a servlet generated from a JSP (in Tomcat 3.2.x):
>
> The name of the class for a page included in another page depends on the
uri
> used in the jsp:include action, so the same page may generate multiple
> classes.
>
> So if I have for example a page called "/pages.moo.jsp", then including it
> in another page using
>
> <jsp:include page="/pages/moo.jsp" flush="true"/>
>
> produces class
>
> _0002fpages_0002fmoo_0002ejspmoo.class
>
> whereas including it (from a page "/pages/foo.jsp") using
>
> <jsp:include page="../pages/moo.jsp" flush="true"/>
>
> produces class
>
> _0002fpages_0002fmoo_0002ejspmoo.class
> _0002fpages_0002f_0002e_0002e_0002fpages_0002fmoo_0002ejspmoo.class
>
>
> Do you know what is the reason for this ? I know I may be able to find an
> explanation in the spec, but I don't really know where... Is this somehow
> related to the "uribase" parameter of JspC ? Any help would be
appreciated.
>
> Thanks
> Petr
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
