Stefano Mazzocchi wrote: > Michael Hartle wrote: > > 1.) Whenever I used a pipeline like (any generator parsing XML with DTD) > > => (no transformer) => (HTML serializer), the first character returned > > and visible astonishingly was always a ">". I assume this is Xerces > > related, as changing the serializer type to "xml" produces an > > ArrayOutOfBoundsException in the Xerces parser. To see this live, take > > the entity catalog demo in the sitemap, remove the stylesheet > > transformation to see the first bug and then change the serializer type > > to "xml" to see the second. Adding an XSLT transformer to the pipeline, > > even if it does not change anything, seems to be a workaround for now. > > I have encountered this before. The problem with SAX is that doesn't > guarantee well-formness as DOM does, being an event-driven approach, of > course.
Hang on. The parser guarantees well-formedness. Try removing closing </title> tag on index.xml then do "build docs". I suppose that you mean that once Cocoon starts building a pipeline, and potentially aggregating other SAX streams into it, then the overall stream is not guaranteed to be well-formed. The strange thing wilth Michael's demonstration, is that a bare ">" has jumped into the pipeline ahead of the XML content stream. The same happens if you similarly tweak the "hello" sitemap entry. > The Xalan internal tree builder/indexer (DTM), seems to be kinda > 'tollerant' in small SAX failures. Try enabling intra-pipe logging and > see what that gives you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
