> I've heard a lot of great things about using XML in combination with JSP to
> make it easier to change the presentation for other languages(Spanish,
> German, etc.) and protocols (e.g. WAP/WML). I know very little about XML
You don't need XML to write a web app that easily supports other lanuages.
Java has very easy to use/powerful internationalization classes. My webapp
is currently written for 5 languages without a touch of XML. I researched
XML for my project and I found out that I'm one of the people that think XML
is a lot of hype for many of it's proposed uses (i may be totally wrong I
admit but "to XML or not XML" is like talking politics - very boring). To
me it is completely unecessary for developing web applications. I think
it's great for many other things but to convert everything you want to
output into XML and then convert that to HTML or some other display format
is a waste of time and doesn't get you very much in return. The other thing
is that servlets do not demand that output be in HTML. If you separate your
business logic into beans and servlets and then only use the JSP for
display, it will be very trivial to convert to some other form of output
(XML if need be).
>
> I'm in the early stages of developing a very large, (hopefully) highly
> scalable web site and I'm trying to decide if it's worth it to go down the
> XML path or if it's just going to be another heavyweight API that'll take
> time to learn and lots of cpu time to run (as if servlets, JSP, EJB, HTML,
> JavaScript, OODB, etc weren't enough).
I know there is some overhead but I really don't know what the resource cost
is. With hardware being so cheap and powerful these days it's probably not
that bad.
Mike
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
