Without getting into detailed interpretations of the spec, I am happy
that a number of vendors are exploring this direction, but I want to
make it clear that the mapping can change as we debug it. Caveat Emptor
and all of that... Remember that one of the reasons why we didn't mark
this is final is that we were not sure we had debugged all the details
of the mapping.
There are other vendors that are supporting the jsp: version of the
scripting elements & directives. At the least RESIN is; although he is
also extending JSP in several other directions.
There are several places where XML and JSP intersect/synergize,
including:
* Accepting XML data and processing it.
* Generating an XML docuemnt.
* Sending the output of a JSP through an XSL transformation
* Using an XML authoring tool to generate a JSP page
* Using DOM to view/manipulate a JSP page
* Using XSLT to transform a specification into a JSP page.
You do not need the JSP page->XML doc mapping to do the first 2. The
third one is actually mostly a Servelt/filter issue, although I think
something can be done using the JSP 1.1 tag lib mechanism. The last 3
are dependent on the JSP page to XML doc mapping, plus the availablity
of DOM support.
We welcome exploration around these topics as they will help us define a
better standard solution to the problem in JSP 1.1+. We just want
people to be sure of what is portable and what is not.
I should write a longer white paper on this and send it around. I'll
get tothat after PR2 goes out; which should be early October.
Hope this helps,
- eduard/o
Karl Avedal wrote:
>
> Hey Eduardo,
>
> > Note that the JSP 1.1 spec still does not require any JSP engine to
> > accept XML mappings of the scripting elements. We have not seen a big
> > need for this, we have not yet had the time to debug the mapping, and we
> > are awaiting the basic "plumbing XML APIs". Bottom line: JSP1.1+.
>
> Yes, but nothing in the JSP 1.1 spec stops engines from implementing it. XML is too
> important to ignore and its match with JSP is great, providing additional seperation
> between content and presentation.
>
> Luckily, I'm using Orion (http://www.orionserver.com) which supports both XML JSP:s
>and
> integrates nicely with LotusXSL to get XML->HTML transformation for non-XML-able
>clients,
> or XML->WML to provide support for WAP phones browsing the site.
>
> >
>
> >
> > Hope this helps,
>
> I'm sorry, but the fact that the spec doesn't mandate XML support won't help me use
>SJSP
> with XML JSP:s ;)
>
> Cheers,
> Karl Avedal
===========================================================================
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
