confused by jx generators and transformers in 2.1.11 & 2.2.0

["Steven D. Majewski" <sd...@virginia.edu>]

I'm still having troubles trying to port from cocoon 2.1.11 to 2.2.0.
( I'm trying to keep as much common between the versions as possible. )


I couldn't get jx generator to work in 2.2.0 as it did in 2.1.11 with  
newjx.

I changed it to use a file generator and then jx transformer.

That works in 2.2.0.

However, it breaks if I try it in 2.1.11

There are several places where I'm passing:

         <map:generate src="scripts/eadframe.jx" type="file" />
         <map:transform type="jx" >
           <map:parameter name="docpath" value="published/{1}/{2}" />
           <map:parameter name="instdir" value="{1}" />
           <map:parameter name="document" value="{2}" />
         </map:transform>

and the jx file is using:  src="${cocoon.parameters.document}.tp" .

( and a couple of other instances with different file extensions. )


In 2.1.11 that seems to be a null value,
however, when I change that to "${cocoon.paramaters}" ,
I see a map of all of the parameter values in the generated error  
message:

org.apache.cocoon.ResourceNotFoundException: No pipeline matched  
request: vivaead/published/uva-sc/Parameters[r/w]:{instdir=uva-sc,  
docpath=published/uva-sc/viu01958, document=viu01958}.tp

( Otherwise, with cocoon.parameters.document, the error message  
displays  .../uva-sc/.tp )

What are the differences in the implementations ?
Any idea what is going wrong?

Why would cocoon.parameters display all of the values,
but $cocoon.paramaters.document  not work?

-- Steve Majewski



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