Hi Daniel,
I agree that the lack of taglibs does make the ready-to-go XSL tags much
more appealing.
On the subject of the data-type formatting though, I really think you are
going to have to address this in more detail at some point.
First, variations in format (should they occur) require you to produce
different XML files rather than different XSL files. This seems contrary to
an "XML=model, XSL=view" perspective since the model shouldn't change just
to facilitate an alternative view.
Furthermore, you are diminishing the opportunity to use the XML as a data
interchange with other systems (both external or even other internal
components in a service-based architecture). This is because you are
imposing your current display format as the actual "value" and then forcing
other systems to interpret as same. So, if your data includes say a list of
invoice dates and you want to show them on screen to one user as dd/mm/yyyy
you have lost the time component of the date that may be important in
another system responsible for scheduling or collections.
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
