"Robert" <[EMAIL PROTECTED]> writes: > The question of 'if you should' is always up for grabs :-), but it comes > closer to a 'yes' if you need to have multiple client types/outputs, > such as HTML, PDF, WML, etc. If not, then it _may_ not be worth it to > use.
We've found that XSLT works very well when your primary objective is to deliver static content (flat files, or cache-able catalog-like non-changing stuff) to different clients requiring different formats. When the content is dynamic (read from a database in response to a request and bean-ified for presentation), then using XSLT to further transform that data degrades performance too much. You're better off using straight Java to do the transformations at the point of "beanification". -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
