cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [BUG] DTD validation shows bugs
Date Fri, 14 Dec 2001 13:02:40 GMT
Michael Hartle wrote:
> 
> Hello all,
> 
> after working and starting to slowly get pretty impressive, nearly
> presentable results on coupling Documentum, Cocoon, Slide and OpenOffice
> together

Uh, cool. Hope you're going to share your experience with us :) [maybe
an howto, hint, hint :)]

> I found out that DTD validation is still a bit buggy in the
> Cocoon 2.0 release:
> 
> 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.

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.

> 2.) After adding the OpenOffice DTD to the catalog and trying to
> validate a content.xml with corresponds to the office.dtd, I encountered
> the bug that whenever entities are to be resolved, the ISO*.pen files
> are being searched in the same directory where the XML file to be
> validated is located. After reverting a recent change to
> org.apache.cocoon.components.resolver.ResolverImpl.java submitted by
> Christian Schmitt (see
> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=100691270713121&w=2),
> this issue was solved and any XML content produced by OpenOffice has
> successfully been validated so far.

Cool. Has this patch being applied?
 
> Has anyone seen such behavior too, or is it just me ? I am using a clean
> Cocoon 2.0 release build with extensions like new generators, source
> factories and the like which are closely modelled after existing
> components. BTW, the Docbase source factory for interfacing Documentum
> docbases yet has to be made configurable, but then it is close to donation.

Cool.

A while ago, I rejected a donation about non-freely available software,
but I've changed my mind: as long as a donation is useful for somebody
and doesn't lag behind (I mean, it's not a code dump) I'm happy to
introduce it in the disto, even if it touches commercial software.

Of course, priorities still go to open-source solutions, but if you are
willing to pay for a service, that's your concern, not ours, and Cocoon
should be as interoperable as possible with existing (and future)
systems.

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<stefano@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------



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


Mime
View raw message