cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <vadim.gritse...@verizon.net>
Subject Re: Dynamic XSL generation with "cocoon:" : excalibur Source or cocoon Source bug ?
Date Thu, 31 Jul 2003 12:36:29 GMT
Olivier Billard wrote:

> Hi all,
>
> I have some troubles with a dynamic generated xsl. Here is the sitemap 
> snippet :
>
>            <map:match select="requests">
>               <map:generate src="..."/>
>               <map:transform src="cocoon:/picto-filter.xsl">
>                   <map:parameter name="profile" 
> value="{session-attr:profile}"/>
>               </map:transform>
>               <map:serialize type="xml"/>
>            </map:match>
>
>            <map:match pattern="picto-filter.xsl">
>               <map:generate src="resources/workflow.xconf"/>
>               <map:transform 
> src="stylesheets/picto-filter-generator.xsl"/>
>               <map:serialize type="xml"/>
>           </map:match>
>
> And I've got the following stack trace (long... but maybe usefull for 
> info) :

....

> but when I replace
> <map:transform src="cocoon:/picto-filter.xsl">
> by
> <map:transform src="http://localhost:8888/picto-filter.xsl">
> all works well...
> But I don't want to externalize the xsl pipeline to the users !...
>
> Any idea ?
> Is this a problem in the pool of sources ? 


Start with working sample, and slowly grow from there:
  http://localhost:8888/samples/sources/xsl-dynamic

When it stops working, then there is a bug in the last change you made. 
May be you have a problem in a way you generate SAX events of your xsl.

Vadim



Mime
View raw message