The XML syntax for JSPs exposes the page as XML. If one disallows
access to "out", then one can compile XML fragments and content into
pushing SAX events. The big hole is what to do with custom tags, since
they operate on character streams. But, if the custom tags used in the
page deal with SAX events, then that seems manageable.
To be honest I am not yet clear that there are substantial performance
benefits with staying within SAX events instead of characters. I know
that this seems appealing in theory, but there are factors in practice
that may not be that simple; just as one example, the fastest
implementation of XSLT that I know, Sun's XSTLC, uses its own API, not
SAX, for performance, so a conversion would be needed anyhow. Etc. But
I would love for somebody to explore this out. Last time I checked
cocoon2 was exploring some of these ideas, there, of course, in the
context of XSP, which has a very different extensibility mechanism.
In any case, in the meantime there are benefits to standard
consumer/producer APIs for XML-aware tags to use.
- eduard/o
James Strachan wrote:
> > The SAX/JDOM type of tags could even interact
> > automatically with JSP in XML syntax so XML elements are passed as
> > events.
>
> I'm not totally sure how yet though ;-)
>
> <James/>
>
> James Strachan
> =============
> email: [EMAIL PROTECTED]
> web: http://www.metastuff.com
