Thursday, November 02, 2000, 7:00:25 PM, you wrote:
> If you don't mind I would like to ask you a question or two..
That's what it's all about! =)
> How exactly is the XSL, XML output of a JSP (using text/xml) being passed to
> the XSLT engine (servlet I assume), and then how is your code returning the
> HTML output back to the browser? I assume you do something like so (in
> psuedo code):
Here is my understanding of how it works.
1. Request calls JSP... or to a servlet which preps some beans and hands control to
JSP.
2. JSP Processess and produces XML with content-type text/xml
3. Orion's Servlet-Chaining features captures the text/xml output before sending
to client and re-directs it to another servlet. In this case XSLTServlet.
Servlet-chaining is specified in the global-web-application.xml A very nice
feature!
4. XSLTServlet takes the XML input, reads the XSL specified in the XML input
(just like IE would do) and loads the XSL.. applies the XSL.. and whatever is
output from THAT is fed to the client.
I think my process is alittle more automated then what you describe.. the
servlet-chaining is what makes it all come together... no backtracking.
Dylan Parker
> 1) Request comes in to servlet
> 2) Servlet makes a URL connection to a JSP page
> 3) JSP output sent to servlet in XML format
> 4) Servlet then loads XSL text
> 5) Servlet calls upon another servlet (XSLT Servlet) passing to it the xml
> output of the JSP page and the xsl it loaded.
> 6) The return (in a response I assume) is the HTML output from the servlet
> that rendered the xml and xsl into html
> 7) The servlet then sends this response back to the browser.
> IS that the general idea? Or is there some other way of doing this? I would
> assume rather than loading the xsl, it tells the XSLT engine the
> path/filename of the xsl text and that engine loads it.
> Thanks.
