First a note that XSLT & XML can be used not just as on the output
part of a JSP but also when processing data in.
We are seing a number of peple use tag libraries to get better reuse of
abstractions, with multiple JSP pages per substantially different user
itnerations. Experience seems to point that it is hard to do a good job
designing a JSP page that works equally well for, say, a voice
interaction and a desktop browser interaction. But we have heard of
people being sucessful using XSLT to, say, cover the differences between
multiple WAP clients, or compact HTML or basic XHTML, or the like - all
similar interaction models. In general going with plain JSP seems to be
faster, and people doing XSLT tend to do caching - although XSLTC does
deliver good performance-; but really what is important (usually) is
whether it is fast "enough".
Also check out http://java.sun.com/products/jsp/html/JSPXML.html,
although that paper & presentation is due for an update.
Hope this helps,
- eduard/o
> Hi,
>
> I have a scenario where I need to write
> web-server-side component that generates UI in an
> efficient way. I am considering many different
> combinations of technologies to achieve this:
> (1) Servlets + XML/XSL
> (2) JSP + XML/XSL
> (3) Just JSP
> (4) Just Servlets
> Among these four both (2) and (3) are the chosen.
> Among these two, which one is the best for:
> (A) Best Performance
> (B) Scalable
> (C) Customizable
> (D) Easily maintainable, etc
>
> Any help would be really appreciatable.
>
> Thank you.
>
> -Srini
>
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST".
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
