Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4832DC82.9000309@onehippo.com>
Date: Tue, 20 May 2008 16:13:22 +0200
From: Jeroen Reijn <j.reijn@onehippo.com>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: [ANN] Apache Cocoon 2.2.0 Released
References: <482D48B5.8040504@apache.org>
 <483142EB.3030501@interactive-net.de> <4831FDDB.8030106@tt.com.au>
 <4832F0F2.5CE9.00D4.0@csir.co.za> <4832DA0D.6040306@onehippo.com>
 <4832F786.5CE9.00D4.0@csir.co.za>
In-Reply-To: <4832F786.5CE9.00D4.0@csir.co.za>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Derek,

as far as I know (I have not used the cinclude transformer in more then 
a year) you will only have to change the way you feed parameters to the 
transformer from your xsl or xml. As i can remember the include 
transformer does not have a containing parameters element. Everything 
else should be the same as far as I can remember.

Regards,

Jeroen


Derek Hohls wrote:
> Is the functionality equivalent?  ie I can just change all my "cinclude" tags
> to "include" and things will work as before?
> 
>>>> On 2008/05/20 at 04:02, in message <4832DA0D.6040306@onehippo.com>, Jeroen Reijn <j.reijn@onehippo.com> wrote:
> Hi Derek,
> 
> the IncludeTransformer has been favored over the CincludeTransformer for 
> a long time as far as I know.
> 
> Regards,
> 
> Jeroen
> 
> 
> Derek Hohls wrote:
>> I am obviously not reading carefully enough...
>> cinclude is deprecated?   what is meant to be its replacement??
>>  
>> Thanks
>> Derek
>>
>>  >>> On 2008/05/20 at 12:23, in message <4831FDDB.8030106@tt.com.au>, 
>> Kamal Bhatt <kbhatt@tt.com.au> wrote:
>> Reinhard Haller wrote:
>> I had a rant about this about a month back. Basically, Cocoon
>> documentation is now a mess.
>> ...
>> Last I looked, most of the functionality was ported across. A lot of
>> things have been deprecated (cinclude, XSP, etc...), so be aware of
>> this. If you want information about migration options, I recommend
>> looking at my various posts last month on Cocoon 2.2 migration. Grzegorz
>> and others discussed all the various migration options.
>>
>> FYI, we have held off on migrating to Cocoon 2.2, but that is not
>> because of Cocoon 2.2s functionality. As frustrating as certain aspects
>> of Cocoon 2.2 can be (confusing documentation being top of the list), I
>> would recommend upgrading to Cocoon 2.2 if only for a saner development
>> environment.
> 
> 
> 

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