>One of the issues is technical in nature. Because of the SAX stream
approach
>that Cocoon 2 uses, the XSP page is being serialized AS it is being parsed.
>What is happening is that each SAX event (startDocument, startElement,
etc),
>is being propogated through the entire SAX chain and being transformed as
they
>are called. Once the root element has been propogated, there is no turning
>back.
Ok.. Could you clarify a bit how and in what order things are done in
Cocoon. What
exactly does Cocoon do with a xsp page (that has been compiled into a java
class)? The
compiled java class constructs a SAX document, which in turn is XSLT
processed if needed. Right?
Isn't this the basic flow of things?
- Anders
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
