cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Upayavira ...@upaya.co.uk>
Subject Re: Finding DTD when aggregating content using XSL (resolved
Date Mon, 01 Sep 2003 14:21:20 GMT
The following is my understanding:

The use of document() in Cocoon is not recommended because it is 
difficult for Cocoon to 'intercept' these functions. Elsewhere, Cocoon 
can use its own source mechanisms to handle things like caching, entity 
resolving, referencing the cocoon protocol, etc. However, XSLT 
transformers will bypass Cocoon's mechanisms and go direct to the system 
to resolve resources when using document(). Thus, a broken Cocoon 
caching system, no entity resolving, no cocoon: protocol, etc, etc.

That is why you are better recommended to use <map:aggregate> or the 
cinclude/xinclude transformers to pull multiple documents into one 
before doing an XSLT on them.

Regards, Upayavira

Albert Bruffaerts wrote:

> Hello.
>
>
> I just wanted to know whether the behaviour described in the email 
> thread started on Fri, 09 Aug 2002 12:55:24 -0700 by Ross Gardler has 
> generated some follow-up, or even better some correcting patch.
>
>
> Indeed, today in Sep 2003, I am still observing exactly the same 
> behaviour:
>
> a. XML parsers used by XSLT transformers activated directly from a 
> sitemap pipelines are using the Cocoon entity catalogs to get access 
> to DTD files
>
> b. XML parsers used to perform execution of calls to XSLT function 
> "document()" embedded in XSLT scripts used by XSLT transformers 
> activated directly from a sitemap pipelines are not using the Cocoon 
> entity catalogs to get access to DTD files
>
> I am using:
>  Cocoon 2.1
>  Tomcat 4.1.24
>  JDK 1.4
>  Xerces 2.4.0
>  Xalan 2.5.1
>
>
> Even if from the Cocoon XSLT FAQs, I read that the use of document() 
> is not recommended within the Cocoon context (What's "wrong" with the 
> use of the document() function in Cocoon), I consider it rather 
> surprising that the Cocoon entity catalogs seem not to be used by all 
> XML parsers instantiated within the Cocoon context.
>
>
> Please, could you tell me whether I miss a step somewhere
> or whether this behaviour is the symptom of a bug in the wiring of 
> Cocoon components (specifically some XML parser instances)?
>
>
> Thank you very much for your cooperation.
>
>
> Best regards,
> Albert Bruffaerts
>
>
> -----------------------------------------------------------------
> Sema Belgium SA    http://be.sema.com
> rue de Stalle 96   mailto:albert.bruffaerts@brussels.sema.slb.com
> B-1180 Brussels    fax: +32 2 333 55 22
> Belgium            tel: +32 2 333 52 34 / 58 (secr.)
> -----------------------------------------------------------------
> Member of SchlumbergerSema, a segment of Schlumberger Ltd.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>
>



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


Mime
View raw message