On Wed, 2011-09-14 at 10:58 +0200, Alec Bickerton wrote:
> Hi,
> 
> I'm seeing some unusual behaviour in Cocoon 2.1.9. It appears that it 
> possible for the xalan transformer parameters to
> not be set in a pipeline. Is this a known issue?
> 
> Relevant part of the sitemap.xmap
> 
> <map:match pattern="general">
>       <map:generate src="cocoon://projects/pe/templatetrafo/generic-common" />
>       <!-- No failure of the generator ever detected -->
> 
>       <map:transform src="transformer_one.xsl">
>               <map:parameter name="hostname" value="myhost.example.com"/>
>               <map:parameter name="jsessionid" 
> value="{request-param:jsessionid}"/>
>               <map:parameter name="bi_show" value="{request-param:bi_show}"/>
>               <map:parameter name="basehosttest" 
> value="{request-param:basehosttest}"/>
>               <map:parameter name="portalnumber" 
> value="{request-param:portalnumber}"/>
>       </map:transform>
> 
>       <map:transform src="transformer_two.xsl">
>               <map:parameter name="jsessionid" 
> value="{request-param:jsessionid}"/>
>       </map:transform>
>       <map:serialize type="xml"/>
> </map:match>
> 
> Using the above sitemap 1 in 5 requests fails to set the parameters 
> triggering the pipeline to fail. I see this by
> setting a breakpoint in the extension method called from transformer_one.
> 
> The transformer is configure as shown.
>     <map:transformer logger="sitemap.transformer.xslt" name="xslt" 
> pool-max="2048" pool-min="32" pool-grow="8"
> src="org.apache.cocoon.transformation.TraxTransformer" >
>       <use-request-parameters>false</use-request-parameters>
>       <use-session-parameters>false</use-session-parameters>
>       <use-cookie-parameters>false</use-cookie-parameters>
>       <xslt-processor-role>xalan</xslt-processor-role>
>       <check-includes>true</check-includes>
>       <use-deli>false</use-deli>
>     <encoding>UTF-8</encoding>
>     </map:transformer>
> 
> Has anyone seen this behaviour in the past, or suggest a place to look for a 
> misconfiguration?

Hmm, try with <use-request-parameters>true</use-request-parameters>
however calling localhost:8888/general?bi_show=true should work

salu2

-- 
Thorsten Scherler <thorsten.at.apache.org>
codeBusters S.L. - web based systems
<consulting, training and solutions>
http://www.codebusters.es/


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

Reply via email to