> -----Ursprüngliche Nachricht-----
> Von: Michael Jouravlev [mailto:[EMAIL PROTECTED] 
> Gesendet: Donnerstag, 18. August 2005 21:33
> An: Struts Users Mailing List
> Betreff: Re: Struts with XSLT
> 
> On 8/18/05, Graham Smith <[EMAIL PROTECTED]> wrote:
> > * Should I just stop fighting city hall and abandon XSLT in 
> favour of JSP?

Yes :-) Really. We did it a year ago, and gained A LOT of performance. Not
to mention that XSLT 
is much less powerful then jsp (custom tags, etc). At least as long, as you
are using an existing renderer.

> 
> No. XML/XSLT is more flexible than JSP and has been supported 
> bunch of other markup tecnhologies like XML, XHTML and XPath 
> for a long time.

And are very much slower to. 

> Keep it if it works. Don't forget that modern browsers can 
> accept XML and have built-in XSLT processor. So, you can send 
> your serialized bean data as XML with linked XSLT stylesheet 
> with linked CSS stylesheet.


Now this is an urban legend :-) Each browser support it it's own way. Not to
mention each version of the redmond browser supports ist
own extensions. None of them are compatible. 

> 
> > * Perhaps it's still a little early to say exactly how 
> Struts 2.x will 
> > turn out but will the idea of view technology independence 
> be maintained?
> > * If Struts 2.x doesn't (essentiall) force us to use 
> something akin to 
> > JSF will XSLT still be a viable option?
> 
> You can do it in Struts 1.x too. Instead of forwarding to JSP 
> page just stick XML (or XML/XSLT already processed into HTML) 
> into response object and return null from an Action class. 
> Apparently, you would use ActionForm for input only with 
> request scope, and store your app data somewhere in the 
> session or in database.

Actually it's better to write out the dom object (if you have one, but you
should, if you seriously want xslt/xml). 
I would also look into rendering with SAX, it could probably give you 40-50%
more performance then dom rendering.

Regards
Leon



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to