Great info. in these posts, Donald...don't let my (or anyone else's) repeated preferences for JSP-based views disuade you, XSLT has great promise (still wishing I had my crystal ball) and the comparisons to the JSP approach are quite useful no matter which side of the fence you fall on.
peace, Joe > -----Original Message----- > From: Donald Ball [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, September 11, 2002 3:04 PM > To: [EMAIL PROTECTED] > Subject: RE: Additional <logic:iterate> helper tags wanted > > > On 9/11/2002 at 10:14 AM [EMAIL PROTECTED] wrote: > > >Wow, good rhubarb here hiding under a misleading subject title ;-). > > rhubarb? do you mean rhetoric? :) > > >To me, the big strength of the XSLT approach would be the ability to > >transform the model into a variety of views (not just one > html view). I > >know that I can create a JSP application that is layered > well, keeping > only > >things like variable output and iteration in the JSPs and > all other data > >preparation work back in other Java layers. Believe me, > programmers can > >hash up any architecture. I can make a mess with XSLT just > as readily as > I > >can with JSP. > > While that's true to a certain extent, you can't make as much > of a mess > with XSLT as you can with JSP. For one thing, without relying on XSLT > extensions, you _can't_ write an XSLT stylesheet which > affects the Java > Model or Controller objects in any way. For another, you > _can't_ generate > invalid output with XSLT (syntactically, anyway. you can > check grammar if > you run the output through a validating SAX filter, but you > _could_ do that > with your JSP pages if you wanted to.) > > >The strength of the JSP approach is it is faster to get going, > particularly > >if I'm starting with HTML prototypes of an application. If > I only have > one > >transform (model data to one html), why do a lot of extra work? > > I find I can turn an HTML page into an XSLT stylesheet in a > matter of a few > minutes (tidy -asxml, add xslt wrapper elements), but for the sake of > argument, I'll accept that you can get JSP's up and running > faster. Even if > you only have one target output device (modern html), in > addition to the > aforementioned pedantic benefits of XSLT, it also makes it > easy to factor > common design elements into a central stylesheet. (I'm a huge > fan of the > Don't Repeat Yourself principle.) > > Sorry, I didn't mean to turn this into a defence of XSLT - I'm really > curious what JSP/JSTL developers think is superior about it. > Thanks for > helping illuminate me. > > - donald > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
