Originally posted by Gregg Bolinger:
Personally, I think allowing java code in a jsp page was a bad idea. (I know it all goes to java code anyway) but from a design perspective, using XSLT seems a bit cleaner of an approach?
I agree that the scriptlet stuff is often awful to look at, let alone touch it.
But. I don't think XSLT is necessarily a better solution. XSLT is meant for transformations -- how many transformations your typical web interface really needs? Is your data coming in XML from the business logic layer?
I am currently doing a mobile application where the J2ME code and
J2EE code (webapp) talk to each other using XML messages. I looked for a web framework with XML support for some time but decided that there was no rationale for using such a product as I wasn't doing transformations, only generating the XML from Java objects on the web layer. XML data binding, perhaps, but no XSLT for me, thanks.
Personally, I put my hopes on JSPs with XML syntax and taglibs (Struts,
JSF, or something else).