Thanks for your reply Leon.
First let me say that I am a novice at XSLT and am really looking at my
technical options..., so I'm not quite 'in-the-know' as to why I've
qualified for the double frown. Any explanation [or pointers to a good
article] would help me very much.
I wanted to take a step back and enlist your help...
My primary requirement is to provide multi-language versions of articles. I
am trying to find the best way to serve this out, I intend [although still
evaluating but is good as sold] to use Turbine.
My idea with XSLT was to store the different language versions of the
articles in XML. This seems attractive since I can change format very easily
using XSL style sheets. Creating the XML document would also be easy to do.
I'm am concerned that I'm having to put in a transformation step and am very
unsure how this will impact the performance [I see from the original message
below that there is caching but I don't currently have a feel for the
speed].
My second option was to store the articles in a database and implement my
own caching [or use Turbine, at least I think there is a caching service].
But I'm still left with the step of having to mark up the document! Maybe my
thinking was to store XML in my database [MySQL] and then still transform
using XSLT. I really do not want to dissect my article up and map it somehow
to a database table[s]!
My last option was to provide my different articles in their final marked up
versions [since the content is static], e.g. JSPs. I would then use the
correct JSP version at runtime. This is obviously the most rigid option
[since I am tying myself to JSPs] and would not help my second requirement!
My (very) secondary requirement is to maybe use XSLT for marking up content
for different client types [e.g. PDAs, WAP, etc.] - this is very much low
priority and would be very limited, so this is a nice to have but can be
dropped.
Thanks for any comments, Hong.
>From: Leon Messerschmidt <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: [EMAIL PROTECTED], [EMAIL PROTECTED]
>Subject: Re: XSLTService with JSPs
>Date: Wed, 13 Jun 2001 12:13:28 +0200
>
>Hi Hong,
>
>XSLT is also somewhat frowned upon, so I don't think anyone has tried the
>double-frown :-)
>
>As long as you can feed the XSLTService with XML input it will happile
>transform anything you give it, regardless where it came from. If you can
>divise a way to give it XML that came from JSP it will work.
>
>~ Leon
>
> > Hi
> >
> > I know the use of JSPs is frowned upon but...
> >
> > Has anyone tried using the XSLTService with JSPs with success? Any
>pointers
> > [examples would be ideal] would be very much appreciated.
> >
> > Thanks in advance, Hong.
> >
> > >From: Leon Messerschmidt <[EMAIL PROTECTED]>
> > >Reply-To: [EMAIL PROTECTED]
> > >To: [EMAIL PROTECTED], Gary Lawrence Murphy
> > ><[EMAIL PROTECTED]>
> > >Subject: Re: Conceptual leap needed: How do I jump into Xslt services?
> > >Date: Wed, 13 Jun 2001 08:54:37 +0200
> > >
> > >Hi Gary,
> > >
> > >The XSLTService takes XML input and transforms it with an XSL
>stylesheet
> > >placed in the directory that you specify in the TR.properties. It only
> > >exposes a transform() method, which you use to do the transformation.
> > >
> > >The VelocityXslLayout assumes that your Velocity
>Layout/Screen/Navigations
> > >are XML templates instead of HTML templates. So the
> > >Layout/Screen/Navigations work exactly the same as in HTML, but before
>the
> > >result is sent of to the user an XSL transformation is done on the
>content.
> > >VelocityXslLayout also assumes that you have correctly set up
>XSLTService.
> > >
> > >If you need to sometimes do a transformation and not on others, you
>need
>to
> > >tell a screen which layout to use. You can use setLayout to make it
>use
> > >the
> > >VelocityXslLayout when you need transform. You can also implement your
>own
> > >layout class and let this class decide when to do a transform and when
>not.
> > >
> > >~ Leon
> > >
> > >p.s. Remember to turn on XSLT caching in your TR.properties for
>production,
> > >otherwise you're site is going to be SLLOOOOWWWWWW.
> > >
> > > >
> > > > The xdocs say to look at VelocityXslLayout.java for usage examples,
> > > > but the source file only tells how to enable the service in the
> > >tr.props;
> > > > where can I learn how to actually invoke the service?
> > > >
> > > > What I'd want is to have my new DefaultLayout detect that the
>request
> > > > really wants an XML doc, and have it setLayout (or
>setLayoutTemplate?)
> > > > to the XML case, but what happens next?
> > > >
> > > > --
> > > > Gary Lawrence Murphy <[EMAIL PROTECTED]> TeleDynamics Communications
>Inc
> > > > Business Innovations Through Open Source Systems:
>http://www.teledyn.com
> > > > "Computers are useless. They can only give you answers."(Pablo
>Picasso)
> > > >
> > > >
> > > >
>---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail:
>[EMAIL PROTECTED]
> > > >
> > >
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
>_________________________________________________________________________
> > Get Your Private, Free E-mail from MSN Hotmail at
>http://www.hotmail.com.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
