On Thursday 18 August 2005 20:32, Michael Jouravlev wrote: > On 8/18/05, Graham Smith <[EMAIL PROTECTED]> 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.
I'm glad to see there is some support for XSLT. Makes me feel like I haven't been barking up the wrong tree for the last few years. Sending the XML to the client is a nice idea in principal but has so many problems that IMHO it's not worth it. Transformation server side is cheap enough now that I don't worry about doing it. > > > * 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. That's an interesting idea. I have a look into that. Thanks Graham > > Michael. > > --------------------------------------------------------------------- > 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]
