You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/10/31 08:45:14 UTC
DO NOT REPLY [Bug 4362] -
Reading init-params from a JSP should not need a servlet-mapping
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4362>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4362
Reading init-params from a JSP should not need a servlet-mapping
efussi@gmx.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
Summary|Cannot read init-params from|Reading init-params from a
|within a JSP |JSP should not need a
| |servlet-mapping
------- Additional Comments From efussi@gmx.net 2001-10-30 23:45 -------
I just checked the Servlet Spec again. Although it does not specifically state
how <init-param>eters are accessible from within JSPs, it on the other hand
does not require a <servlet-mapping> to be given.
Another hint that this should work without <servlet-mapping> is that <init-
param> is a subelement of the <servlet> element, not of the <servlet-mapping>
element.
Furthermore, I still don't think that implementation details like the <init-
parm>eters of the JSP invoker servlet should be exposed as easily.
Therefore I am re-opening this bug with a changed summary line.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>