atom feed19 messages in org.apache.struts.userRe: Struts with XSLT
FromSent OnAttachments
Graham SmithAug 18, 2005 7:12 am 
Don BrownAug 18, 2005 8:01 am 
Graham SmithAug 18, 2005 8:31 am 
Craig McClanahanAug 18, 2005 9:31 am 
Mark BenussiAug 18, 2005 9:36 am 
John MartyniakAug 18, 2005 12:07 pm 
Michael JouravlevAug 18, 2005 12:32 pm 
Graham SmithAug 18, 2005 12:42 pm 
Leon RosenbergAug 18, 2005 12:44 pm 
Leon RosenbergAug 18, 2005 12:52 pm 
Graham SmithAug 18, 2005 1:05 pm 
Michael JouravlevAug 18, 2005 1:10 pm 
Luiz GodoyAug 18, 2005 1:21 pm 
Leon RosenbergAug 18, 2005 1:27 pm 
Eduardo Ribeiro da SilvaAug 18, 2005 1:32 pm 
Dhar...@ubs.comAug 18, 2005 2:10 pm 
Peter MaasAug 18, 2005 10:41 pm 
Mitchell, Steven CAug 19, 2005 5:29 am 
Craig McClanahanAug 19, 2005 2:52 pm 
Subject:Re: Struts with XSLT
From:Michael Jouravlev (jmi@gmail.com)
Date:Aug 18, 2005 12:32:20 pm
List:org.apache.struts.user

On 8/18/05, Graham Smith <gra@crazysquirrel.com> wrote:

* Should I just stop fighting city hall and abandon XSLT in favour of JSP?

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. 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.

* 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.

Michael.