cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò <ilgro...@apache.org>
Subject Re: [C3] Passing parameters from sitemap to generator
Date Wed, 03 Aug 2011 16:31:58 GMT
On 01/07/2011 11:40, Francesco Chicchiriccò wrote:
> On 01/07/2011 11:29, Reinhard Pötz wrote:
>> On 07/01/2011 10:25 AM, Francesco Chicchiriccò wrote:
>>> Hi all,
>>> recently I have been in the situation for which I need to 
>>> parametrize an XML file of my application; I thought there was a 
>>> simpler way but I ended up by using an additional XSLT 
>>> transformation step (since the XSLTTransformer can accep parameters 
>>> from the pipeline).
>>>
>>> With C2.1 I used to put in place the JXGenerator [1] (or 
>>> JXTransformer [2] depending on the case): this saved me, in many 
>>> cases, from an additional transformation step in the pipeline.
>>>
>>> Even though it is true that everything you could do with JXGenerator 
>>> can always be done with XMLGenerator + XSLTTransformer, do you think 
>>> that such component can be a "nice to have" in C3?
>>
>> So far there is only the StringTemplateGenerator component, that 
>> dynamically generates XML based on a template.
>
> How long should it be to add sitemap parameter handling there?
>
>> There are also no 'build-in' objects like request, session, etc. 
>> which were supported by the JXGenerator or the VelocityGenerator in 
>> Cocoon 2.x
>>
>> I have no strong opinion on what should be migrated to C3 as long as 
>> it goes into a new module or the cocoon-optional module ;-)
>
> Eh eh, I knew that :-)
>
>> I suggest that you choose that technology that fits your requirements 
>> and your time constraints (VelocityGenerator should be rather 
>> straight forward, migrating JX* is definitly more-timeconsuming) best.
>
> As far as the "sitemap parameter handling" part is viable, the 
> VelocityGenerator could be fine.

After taking a closer look to cocoon-stringtemplate, I ended up by doing 
some adjustments to the previous implementation, updating to latest 
StringTemplate available to maven and adding, besides the 
StringTemplateGenerator, a StringTemplateTransformer.

I have also updated cocoon-sample so that it should be straightforward 
to check these two components running.

In this way, we (well, at least I) have something that should cover the 
principal use cases of JX* or VelocityGenerator.

Cheers.

-- 
Francesco Chicchiriccò

Apache Cocoon Committer and PMC Member
http://people.apache.org/~ilgrosso/


Mime
View raw message