Title: Tapestry and XML/XSLT
Well, there are lots of options.  You could write a XSLT Component that could be fed XML and XSLT and convert it to raw HTML.
 
You could use Tapestry (with the new OGNL support) to walk your XML Dom and do XSLT-style transformations that way.
 
You could used Tapestry components and your own implemenation of IMarkupWriter to walk business objects and produce XML, and use a servlet filter and XSLT to generate HTML.
 
The default Tapestry implementation wants to be on the front line (the thing that generates the HTML), but there are always extension points and options.  And if you hit a good pattern, feel free to contribute some code back!
----- Original Message -----
Sent: Tuesday, September 03, 2002 12:43 PM
Subject: Tapestry and XML/XSLT

Hi,

I am currently evaluating web-app UI toolkits for a data-driven form based web-application. Tapestry is one of the toolkits I am looking at, I was wondering if you could possibly answer a question for me:

Our backend will probably use XML as it's data format. So far something like XSLT looks like the best way to generate our data-driven HTML pages. If we were to use Tapestry as the toolkit to build the UI, what are the options for integrating with XSLT to produce embedded lists of data etc.?

Thanks for your time,

Kevin
--
+44 (0)1628 589125
[EMAIL PROTECTED]

Reply via email to