Hi D.J.,
We use:
.- Framework specific (which is itself container independent)
implementation of the model 3 for PL/SQL -> XML -> XSL transformation. I
just created another base class for my action classes of the model 2
architecture so it fits pretty well in our already built model 2
framework, thus we can enjoy customizable security and application-wide
event handling just as if it were model 2.
.- For the JSP -> XML -> XSL, we use a custom JSP1.1 taglib that
transforms its whole body. It is also container independent and it is
transparent to the model 2 arquitecture so it also fits nicely into our
framework.
We discarded your first option because it is container specific and we
try to avoid this kind of things as long as possible.
Cocoon is focused in transformation of static XML so we learn from it
but we are not using it. We are basically doing what he does but using
dynamic XML sources. We hope to learn also from it when we get to the
point of caching XSLTProcessors but so far we create them each time.
Regards,
Dan
-------------------------------------------
Daniel Lopez Janariz ([EMAIL PROTECTED])
Web Services
Computer Center
Balearic Islands University
-------------------------------------------
"D. J. Hagberg" wrote:
>
> This is certainly an interesting solution, and I can certainly see the
> benefits when generating content for different display devices/browsers.
>
> The primary question I have for Daniel and the other folks out there
> using XSLT is -- what specific tools and techniques are you using for
> this transform? Is it:
>
> - container-specific implementations of servlet chaining?
> - jsp 1.1 taglets that transform their whole contained body?
> - relying on cutting-edge browsers that actually do XSLT?
> - some other mechanism like Cocoon?
>
> -=- D. J.
>
> Daniel Lopez wrote:
> [ . . . ]
> > .- The JSP page formats the result in XML, which is more easily
> > understood by designers, can be used as documentation, and for which
> > fake document sets are easily generated. The JSP can also determine "on
> > the fly" which XSLT sheet will be used to generate the UI.
> > .- The XSLT sheet transforms the XML into HTML, WML, PDF and result is
> > sent to the client.
===========================================================================
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
