https://bz.apache.org/bugzilla/show_bug.cgi?id=69135
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |NEEDINFO
--- Comment #5 from Mark Thomas <ma...@apache.org> ---
Ah. We need to clarify the behaviour for absolute paths in an include directive
first then.
My reading of the specification is as follows (all references to Pages 4.0):
<%@ include file="/META-INF/include.jspf"%>
is an include directive as defined by section 1.10.3. As per 1.10.3, the
behaviour of the file attribute is defined by section 1.2.1.
1.2.1 states that paths starting with "/" are context relative.
Further, 8.4.1 requires that all tag files packaged in a JAR file are packaged
under /META-INF/tags or a sub-directory of /META-INF/tags. While not explicitly
stated, it seems reasonable to me that tag file segments should be subject to
the same restriction.
What is your justification, with specification references, for absolute paths
used within a tag file or tag fragment in tag package in a JAR to be relative
to the JAR root rather than the context root?
What is your justification, with specification references, for it to be
permitted for tag file fragments packaged in a JAR file to be located outside
of /META-INF/tags ?
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
