tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 33564] - Servlet Init Params for a jsp cannot be obtained
Date Tue, 15 Feb 2005 17:13:49 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33564>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33564





------- Additional Comments From b_basham@yahoo.com  2005-02-15 18:13 -------
Created an attachment (id=14289)
 --> (http://issues.apache.org/bugzilla/attachment.cgi?id=14289&action=view)
New webapp with new behavior.

Hello again,

We are getting closer.	Bruce discovered that the 'fork' and 'xpoweredBy' init
params are coming from the JSP invoker servlet defined in conf/web.xml.  So...
it seems clear that Tomcat is using this servlet definition rather than our
servlet definition.

So, I concluded that I needed a servlet mapping (to override the primary JSP
invoker mapping).  So in this WAR file I have added a servlet-mapping element
for the /index.jsp servlet.  Now... I am seeing both sets of init params in my
JSP page.  Is that really how it should work?  Should every JSP page include
the init params for the JSP invoker?  This seems odd, but easily worked-around.


-Bryan


-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message