>There's a XSLT tag in the Jakarta TagLib project.
>From what I gather from the documentation on the website of the project:
http://jakarta.apache.org/taglibs/doc/xsl-doc/index.html
The tag looks a little weak in that it's not very pluggable, and doesn't
have too many options for conversion. Also, the transform tag I proposed
would be plugged into an underlying transformation service in Struts.
>Also, the concept is similar
>to what Cocoon is doing.
I'm slightly familiar with cocoon, but could you elaborate?
"Schachter, Michael" wrote:
>
>
> Well, it's the same basically for XSLT. Instead of using jsp taglibs, the
> presentation designer could possibly be given a specification for an xml
> format to work with, such as:
>
> <document>
> <title>The title</title>
> <body>A bunch of content</body>
> </document>
>
> And all the designer would have to know is pretty basic XSLT to produce
the
> view for each device. It'll probably be up to the business logic guy to
> develop the JSP that spits out the XML. Inside of XSLT the presentation
> designer embeds whatever presentation language their using, HTML, WML,
pure
> XML, etc. The only tags the developer has to worry about now are standard
> XSLT tags, as opposed to custom built (either by you or a framework's)
tags.
>
