> -----Original Message----- > From: Don Brown [mailto:[EMAIL PROTECTED] ==////== > > > Now, now, Peter, you can't quite say that since you met me at the > Struts user group at JavaOne. :) I've used stxx, an XML > transformation Struts extension, for a production app and have been > pretty happy with it. Performance is good, as long as one has memory > resources available. The stylesheets can be cached when compiled, and > using a decorator tool like sitemesh, the pages your XSL generates are > quite small. The big disadvantage, as I see it, is it requires XSLT > knowledge, which most web developers don't have. I probably wouldn't > recommend it for apps that don't have their data in XML and don't need > multiple views. > > Don
Don, it's bean so long that I cant remember all the discussions from July this year, so there you go. My apologises, because I dont remember Stxx coming up in the conversation. Yeah! I agree XSLT is a bit harder to fathom for web page designers too. The use case is multiple views, data already stored and prepared in XML i.e. XML database / report or web services. > > > On Tue, 16 Nov 2004 17:59:48 -0000, Pilgrim, Peter > <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > -----Original Message----- > > > From: Dakota Jack [mailto:[EMAIL PROTECTED] > > > Sent: 16 November 2004 17:46 > > > To: Struts Users Mailing List > > > Subject: Re: talking about paradigms > > > > > > > > > Bill, > > > > > > Sounds like you don't need what XSLT provides. The > important thing, I > > > think, is to make sure that the framework leaves that > option open for > > > those that want it and does not require that option to > those who do > > > not want it. I am not privy to the details of your > application, of > > > course, but adding code to the controller to assist in the > > > presentation seems to me to indicate a serious design flaw. That > > > simply is not the business of the control layer, if you > are using the > > > control layer in an MVC pattern. Part of your bad experience with > > > XSLT sounds like it is not related to the view issues but to some > > > confusion in the architecture of the application? Not > knowing much > > > about the details, this is probably a harsh assessment, > but it is what > > > I would intuitively expect to find. My head keeps saying > "What the > > > heck is the controller doing generating XML?". The > controller should > > > be deciding what to do about user input given whatever > strategy the > > > application has adopted. > > > > > > Jack > > > > > > > > > On Tue, 16 Nov 2004 10:55:52 -0500, Bill Siggelkow > > > <[EMAIL PROTECTED]> wrote: > > > > Jack, > > > > > > > > What I found was that alot of Java code to generate XML > > > (using DOM API) > > > > had to be added in the controller layer to facilitate > the view; for > > > > example, an odd/even indicator was added just to facilitate > > > striping on > > > > the generated HTML table; to me, this seems downright > > > overkill for some > > > > feature that is purely presentation (granted, the > > > developers could have > > > > avoided this through better use of XSLT). > > > > > > > > Personally, I've never warmed to the idea of using the > > > XML/XSLT approach > > > > when the data is already in the form of a Java object; > it just seems > > > > like an extra step that doesn't buy me a whole lot. > > > > > > > > -Bill Siggelkow > > > > > > > > I have never come across anyone in a face-to-face who uses > > the XML/XSLT approach at least with Struts. I met a straight-up > > Cocoon fantastic a few years ago, but by then he was moving > > away from XSLT to proprietary web application framework on > > some app server. > > > > This biggest problem of the XML is the transformation phase, > > and it sounds like that the original tabular XML was not > > augmented with attributes to say this is hint "render > > this row in green" and now "render that next row with > > white background". Then an XSLT can be written to easily > > transform things around (or not as the case may be). > > > > I think XML/XSLT pipeline is useful for static stuff that > > mostly does not change frequently. How did you find the > > XSLT transformation performance on your project? > > Did you cache the XSLT results somewhere? > > ==////== -- Peter Pilgrim Operations/IT - Credit Suisse First Boston, 10 South Colonnade, London E14 4QJ, United Kingdom Tel: +44-(0)207-883-4497 ============================================================================== This message is for the sole use of the intended recipient. If you received this message in error please delete it and notify us. If this message was misdirected, CSFB does not waive any confidentiality or privilege. CSFB retains and monitors electronic communications sent through its network. Instructions transmitted over this system are not binding on CSFB until they are confirmed by us. Message transmission is not guaranteed to be secure. ============================================================================== --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
