Tomasz Ratajczak wrote:
> Hans, Craig,
> Thank you for responding. Jakarta Taglibs <xsl:apply> and <xsl:include> tags
> is exactly what we needed.
> One remark about the <xsl:include> tag. A penalty that we incur for using it
> is that we loose attributes at the request scope, since it opens a new URL
> connection to the server, I am assuming that session is fine. Is it not?
> Currently there is not much else that one can do and I fully appreciate
> usefulness of your solution.
> Tomasz Ratajczak
>
The original session is still fine, but the internal request generated by the
<xsl:include> does not include the session id, so it will not be considered to be
part of that session by the server. It would probably be feasible to add a
mechanism to propogate the current session ID if there is one.
The whole need for a separate connection inside <xsl:include> in the first place is
because of the limitations on <jsp:include> in JSP 1.1. Fortunately, these issues
go away in Servlet 2.3/JSP 1.2, and the implementation of <xsl:include> will be
able to do use a request dispatcher instead. In that scenario, session affinity
will be maintained.
Craig
====================
See you at ApacheCon Europe <http://www.apachecon.com>!
Session VS01 (23-Oct 13h00-17h00): Sun Technical Briefing
Session T06 (24-Oct 14h00-15h00): Migrating Apache JServ
Applications to Tomcat
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
