Jeff, The simple answer to your question (asumming the transform is to html) is that transformations are part of the view. I use only xml and xslt for the client side out put in my struts app. What happens is that you replace all the jsps with xslt stylesheets and an xslt processor (servlet), and the majority of your model is replaced with DTDs or Schema. I use the ActionForms still with the controller to gain any information from user input, but all of my business logic will return xml documents or text to the Action classes, that are then forwarded to the xslt processor servlet.
If you treat the legacy app as part of the view (assuming this is the equivilent of the xslt servlet) the it makes it easier to see this. I would advise against manipulating a xml doc into beans. It's very complicated with complex DTDs or Schemas, and just addes in more complexity to your system (not to mention a boat load more places where things can go wrong). If you need any more info, I can help you out with most xml, xsl xslt problems. Cheers Simon ----- Original Message ----- From: "Jeff Kyser" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 03, 2003 4:09 PM Subject: [OT] What layer does an XSL transform belong to > Hey all, > > A bit philisophical I suppose, but we've integrated some > legacy apps into a Struts application, and they return their > data as an XML document. > > In a previous version of the app, the JSP made the legacy > call (gakk!), and then performed an XSL transform to display > the info to the user. (I didn't write it :) > > I'm trying to migrate things towards their proper places, and > my question is where (if anywhere) the XSL transform belongs. > > Ideally, I would either call the legacy app from within a > Action, or pushed down yet another layer behind some > model call. > > But if I did a model layer, then I'd probably transfer the data > from the XML document to a Java model object and then > transfer data from the model to a form via the Action and let > the tag libraries take it from there. > > I don't have the luxury of a rewrite, so trying to incrementally > migrate and just not sure where the XSL transform should > land (or at least roost). > > your insights would be appreciated > > regards, > > -jeff > > > --------------------------------------------------------------------- > 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]
