cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: Catalogs don't work on XSLT stylesheets
Date Thu, 04 Oct 2001 09:21:58 GMT
OK Stefano, i have reproduced the issue with the following
steps. In the quoted email below, i build upon your potential

1) referenced an entity in stylesheet test.xsl - i used J&ouml;rg
2) received processing expection ... as expected because
i have not yet declared the ISOlat1 entity set
ERROR   (2001-10-04) 01:12.23:056   [cocoon  ] (/cocoon/catalog-demo) 
Thread-16/TraxTransformer: Problem in getTransformer:
org.apache.cocoon.ProcessingException: Error in creating Transform Handler: 
org.xml.sax.SAXParseException: The entity "ouml" was referenced, but not 
... that was an extract from the cocoon.log whereas the error page
was very cryptic.
3) declared the entity set in my test.xsl ... similar to Stefano's
example below, but for ISOlat1
4) now we get a different exception ... file not found ISOlat1.pen
... this indicates that the entity resolver is not working.
There were also no resolver messages going to stdout.
5) as a workaround, i copied the ISOlat1.pen file to the same
directory as the stylesheet
... now the parser finds ISOlat1 via the default system identifier
6) it works, i see my output with the proper entity well presented
7) summary - entity catalogs are not working at stylesheet level

see more comments below ...

Stefano Mazzocchi wrote:
> David Crossley wrote:
> > Hi Stephano, 
> ehmm, Stefano, please :)
> > thanks for your Bugzilla entry. 
> You are welcome :)
> > Would you please
> > add a test case stylesheet to demonstrate how you declare an
> > external entity. I wonder if this is actually a bug or a usage issue.
> Good point. What I did was placing the following
> <!DOCTYPE xsl:stylesheet [
>    "ISO 8879:1986//ENTITIES Numeric and Special Graphic//EN//XML"
>    "ISOnum.pen"
>  %ISOnum;
> ]>
> above the <xsl:stylesheet> element and it didn't work.
> > The entity resolver is attached to the parser, so resolution
> > happens at that level rather than at the XSLT level.
> Ah, ok. I thought that maybe the Trax handlers required another instance
> of the entity resolver.

I think that you are right. Every time that a parser is used, it needs
to have an entity resolver set for it. Cocoon does this already for 
That parser is used for processing the original XML stream. At that
level the entity catalog resolver works beautifully.

However, it now appears that other parsers are called from
elsewhere in Cocoon (e.g. TraxTransformer). So yes, the entity
resolver needs to be set for whatever parser is used.

If our analysis is correct would someone please follow the
example code in to set entity resolvers for any
other parsers.

> > By the time
> > that the XML stream gets to the stylesheet, then all entities
> > have already been resolved. I would expect that you would need
> > to declare all necessary entities from the document type
> > declaration of your XML instance document.

I tried doing this to no avail. I imagine that is because there were
two separate parser instances. The XML stream has already had
all of its entities resolved and now the stylesheet is adding more. 

> Am I doing something wrong in the above declaration?

I am not really sure Stefano - my XSLT book does not
discuss entity declarations very much, or even using character
entities at all. Anyway the declaration that you have provided
does work, as evidenced by 6) above.
regards, David Crossley

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

To unsubscribe, e-mail:
For additional commands, email:

View raw message