cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Noels" <stev...@outerthought.org>
Subject RE: entity resolver woes
Date Tue, 22 Jan 2002 15:54:02 GMT
Getting back to cocoon-dev land:

I did some further testing with some input from Michael...

As I feared, putting an identity transformation stylesheet in between my
pipeline, my problem was solved.

I've been browsing some code to find the difference in handling SAX
events between the AbstractTextSerializer and AbstractXMLPipe - but I
could use a couple of extra eyes :-)

My wild assumptions are that:

1) or this is a Resolver bug, i.e. it incorrectly handles comments
inside external entities and inserts them incorrectly in the output
stream
2) it throws some (weird?) SAX events (cfr 1) that the Serializer is
unable to handle, but the XMLPipe is handling correctly (based on my
understanding that XMLPipe is indeed the event-forwarder)
3) I'm touching grounds way to difficult for my weary brain to handle
:-)

Regards,

</Steven>

> -----Original Message-----
> From: David Crossley [mailto:crossley@indexgeo.com.au]
> Sent: dinsdag 22 januari 2002 15:39
> To: cocoon-dev@xml.apache.org
> Subject: Re: entity resolver woes
>
>
> Michael Hartle wrote:
> > Steven Noels wrote:
> > >Has anyone experienced problems with the Resolver when
> simply generating
> > >& immediately (re-)serializing an XML document, when this document
> > >refers to a PUBLIC DTD which includes a number of external
> parameter
> > >entities.
> > >
> > >From what i can see now, the comments inside the external
> entities are
> > >inserted as-is in the stream, unfortunately not inside a local
> > >declaration subset but immediately after the SYSTEM id:
> >
> > <snip/>
> >
> > I recently had the same problem when I made a pipeline
> which returns the
> > DTD-conforming main content.xml file from OpenOffice zip archives;
> > trying to aggregate several content.xml from another Cocoon
> server via
> > HTTP, the parser told me that the content.xml files are not
> well-formed
> > anymore, thus showing exactly the same resolution behaviour as you
> > described. IIRC, there has been a thread not long ago where someone
> > (maybe David Crossley) posted that this is resolver and/or
> > parser-related, but I am not sure.
>
> No i do not know anything about this and do not recall such a
> thread (but hey, there are so many :-)
>
> I will be doing some paid work with Cocoon tomorrow on files
> that match Steven's description. So i will try to reproduce the
> behaviour. I do recall once seeing XML comments from a DTD
> being passed into the stream. But it did not cause the issue
> that you reported.
> --David
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message