cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jasha Joachimsthal" <>
Subject RE: (newbie) Access parameter passed to an XSL transformation from stylesheet
Date Sat, 12 May 2007 07:36:29 GMT
Thinking further on your problem, if you need the input from other pipelines, why don't you
use an aggregate?


  <map:match pattern="patternA">
    <map:aggregate element="root>
      <map:part element="patternB" src="cocoon:/patternB"/>
      <map:part element="patternC" src="cocoon:/patternC"/>
    <map:transform src="style.xsl"/>
    <map:serialize type="xml"/>

Now you have all information from both patternB and patternC at the moment of the XSLT transformation.


-----Original Message-----
From:	Jasha Joachimsthal
Sent:	Sat 5/12/2007 9:28 AM
Subject:	RE: (newbie) Access parameter passed to an XSL transformation from stylesheet

Have a look at the XMLFileModule [1] 
Then you can use <map:parameter name="someParam" value="{myModule:/someParam/nodeA}"/>
in your pipeline.




-----Original Message-----
From:	ypomonh []
Sent:	Fri 5/11/2007 5:52 PM
Subject:	Re: (newbie) Access parameter passed to an XSL transformation from stylesheet

Joerg Heinicke wrote:
> On 11.05.2007 16:54, ypomonh wrote:
>> I have a simple pipelineQ
>>        <map:pipeline>
>>            <map:match pattern="patternA">
>>                <map:generate src="cocoon:/patternB"/>
>>                <map:transform src="style.xsl">
>>                    <map:parameter name="someParam" 
>> value="cocoon:/patternC"/>
>>                </map:transform>
>>                <map:serialize type="xml"/>
>>            </map:match>
>>        </map:pipeline>
>> and I want to handle the parameter "someParam" in my style.xsl:
>>    <xsl:variable name="myVariable">
>>        <xsl:value-of select="someParam/nodeA"/>
>>    </xsl:variable>
>> but it returns empty.
>> What is the correct way to access a parameter passed to an XSL 
>> transformation from within the XSL stylesheet..?
> You are only injecting a string, not the content of the pipeline 
> cocoon:/patternC. Have a look on IncludeTransformer.

Joerg I supposed you meant "CInclude Transformer", so I just read and I 
understood that I could first do my XSL transformation leaving a:

    <cinclude:include src="cocoon:/patternC"/>

somewhere in the output and continue the pipeline with a CInclude 
transformation that would fetch the date from cocoon:/patternC.

Besides the fact that it seems a bit complicated, I cannot use the 
element cinclude:include since need the fetched data inside an attribute:

    <elem someAttr="$myVariable"/>

and <elem someAttr="<cinclude:include src="cocoon:/patternC"/>"/> is 
obviously wrong.

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

View raw message