I haven't used the XSL service, but you should be able to drop in your stylesheets as they exist already. Here is the configuration: http://jakarta.apache.org/turbine/fulcrum/howto/xslt-service.html
and here is where I found the class referenced at the bottom of the above doc: http://cvs.apache.org/viewcvs.cgi/jakarta-turbine-3/misc/ -warner ----- Original Message ----- From: "daniel robinson" <[EMAIL PROTECTED]> To: "Turbine Users List" <[EMAIL PROTECTED]> Sent: Saturday, June 29, 2002 10:35 AM Subject: Re: XML and XSLT with Turbine > Thanks for the input. As I've said, I already have the site running > under XML/XSL. I spent a lot of time with cocoon and I'm not sure that > Turbine will work for me either. I want to introduce as few changes as > possible, re-doing the display logic in Velocity will take some time and > it is already done in XSL. Eventually what will probably happen is > that the pages will be cached as HTML and the generation will only occur > when the data changes - a fairly infrequent event. At any rate what I'm > looking for is a more concrete how-to for this. > > Dan > > Warner Onstine wrote: > > >----- Original Message ----- > >From: "daniel robinson" <[EMAIL PROTECTED]> > >To: "Turbine Users List" <[EMAIL PROTECTED]> > >Sent: Friday, June 28, 2002 11:17 PM > >Subject: XML and XSLT with Turbing > > > > > >>I currently have a web site in cocoon that queries a db to produce XML > >>data and then uses XSLT to produce HTML. I am trying to figure out how > >>to convert this to a Turbine app. I have got the TDK running with a > >>sample app and have read through all the documentation I could find and > >>searched through the mail archives. Of course I've come across the XSL > >>classes. I'm still unsure of how to use them. > >> > >>I'm sure I could struggle through this but I'm hoping that someone could > >>quickly explain the steps I need to take to: > >> > >>1) Fetch data from the database - (This seems pretty straight forward) > >> > > > >Depending on how you do it, you could use Torque Object Model, to model the > >data > >you want to pull out what you want and place it into nice container objects. > > > >>2) Wrap the data in XML tags > >> > > > >XML is nice, but what's the business need. Do you need to send xml data to > >someone else? > >If not then I would recommend using Torque to pull your data into objects, > >and a request-tool to allow you to 'pull' your data into a velocity > >template. > > > >>3) Transform the XML using XSLT > >> > > > >Unless there's a business need for XML, I would stay away from the > >performance hit. > > > >>4) Output the HTML > >> > >>Help appreciated, > >> > >>Dan > >> > >> > >>-- > >>To unsubscribe, e-mail: > >> > ><mailto:[EMAIL PROTECTED]> > > > >>For additional commands, e-mail: > >> > ><mailto:[EMAIL PROTECTED]> > > > >> > > > > > >-- > >To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > >For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > > > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
