Interesting discussion.
The underlying problem I see here is "where do you put the layer for
converting *data* to XML ".
The problem I see with using JSP as this layer is that it constrains this
mapping layer to web-only applications by virtue of the dependence on the
servlet objects etc. What happens if I want to render the same objects (as
represented by Beans) to XML in another custom non-web application e.g. a
B2B channel based on JMS or whatever.
My perspective would be that any basic enterprise object (modelled as a
Bean) should be inherently capable of representing itself as XML, maybe as
some basic override of the serialization. That way it can used in any
application.
Now, in a particular web app you still might construct an *aggregate* XML
file in the JSP layer by including the XML-renderings of several Beans as
necessary and perhaps this can be XSLT-d into whatever output format is
required.
As ever, feedback is most welcome...
Regards
@
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
