One last question though. As much as I know, setting page session to false only means that there is no need to create an additional session. What's this have to do with c:imports? Why does an additional session prevent our c:imports?
Asim
On Mar 2, 2004, at 1:15 PM, Remy Maucherat wrote:
Asim Alp wrote:
Thank you for your prompt replies. I just read the bug, and understood what the problem was.
Now, though, I have another question. Is there a way of setting page session to false at a higher level. For example somewhere from the server.xml file? My problem is that we have over 100 websites with tens of thousands of jsp pages. Every single one of these JSP pages rely on these <c:imports... It's almost impossible for us to manually go over each one of these jsp pages and add the <%@ page session="false"%> line to each of them. Can you think of an an easier solution to my problem?
Yes, take advantage that this is OSS and patch your Tomcat ;)
Or use the replacement class (put in server/classes/org/apache/catalina/core).
-- xxxxxxxxxxxxxxxxxxxxxxxxx R�my Maucherat Developer & Consultant JBoss Group (Europe) S�RL xxxxxxxxxxxxxxxxxxxxxxxxx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
