Some time ago, I posted a message about problems with filters and a struts--application that I was trying to make work as a portlet.
We changed the implementation by replacing the filter by a RequestListener. Basically, the listener opens a connexion when the request is initialized and closes it when the request is destroyed. Everything works fine in the standalone application. I now tried to configure it to use the struts-bridge 0.2, and I started getting Exceptions. The Exceptions were caused because there was an attempt to close the connexion more than once. After some tests, I discovered that every <jsp:include page="header.jsp"> <jsp:param name="title" value="Delete Public Events"/> </jsp:include> generated a new Request. Indeed, I removed all the jsp:include tags and got no more Exceptions (because the connexion was only closed once). The question is: Why does a jsp:include generate a new Request ??? I can replace some jsp:include by some <[EMAIL PROTECTED] file="footer.jsp"%>, but some includes like the first one, 1 need a parameter. Anyway, the Requerst listener is at the level of the webapp. Why would the webapp generate extra requests because of the jsp:include ?? Note that all the tests I made so far were by accessing the application as a webapp and not as a portlet. Thanks in advance. Xavier -- -------------=[ xlawrence at jahia dot com ]=------------- Jahia : A collaborative source CMS and Portal Server www.jahia.org Community and product web site www.jahia.com Commercial services company www.collaborativesource.org Jahia's collaborative license --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
