Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 62922 invoked from network); 20 May 2008 13:42:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 May 2008 13:42:52 -0000 Received: (qmail 58690 invoked by uid 500); 20 May 2008 13:42:45 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 58665 invoked by uid 500); 20 May 2008 13:42:45 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 58643 invoked by uid 99); 20 May 2008 13:42:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 May 2008 06:42:45 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [146.64.10.166] (HELO wabe.csir.co.za) (146.64.10.166) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 May 2008 13:41:54 +0000 X-CSIR-MailScanner-Watermark: 1211895647.52687@Mib/sxoiycfGcfElGXwWKw Received: from cs-emo.csir.co.za (cs-emo.csir.co.za [146.64.10.40]) by wabe.csir.co.za (8.14.2/8.14.2) with ESMTP id m4KDelhH016317 for ; Tue, 20 May 2008 15:40:47 +0200 Received: from GW-EMO-MTA by cs-emo.csir.co.za with Novell_GroupWise; Tue, 20 May 2008 15:40:47 +0200 Message-Id: <4832F0F2.5CE9.00D4.0@csir.co.za> X-Mailer: Novell GroupWise Internet Agent 7.0.3 Date: Tue, 20 May 2008 15:40:39 +0200 From: "Derek Hohls" To: Subject: Re: [ANN] Apache Cocoon 2.2.0 Released References: <482D48B5.8040504@apache.org> <483142EB.3030501@interactive-net.de> <4831FDDB.8030106@tt.com.au> In-Reply-To: <4831FDDB.8030106@tt.com.au> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=__Part012876C7.0__=" X-CSIR-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: m4KDelhH016317 X-CSIR-MailScanner: Found to be clean X-CSIR-MailScanner-From: dhohls@csir.co.za X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No --=__Part012876C7.0__= Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit 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 wrote: Reinhard Haller wrote: > Reinhard P�tz schrieb: >> >> The Apache Cocoon Community is proud to announce the release of >> Cocoon 2.2.0. > Thanks a lot! >> >> Cocoon 2.2 introduces the idea of blocks. A block is the unit of >> modularization in Cocoon, allowing the framework to be built upon. (in >> comparison: Eclipse uses the term plugins, OSGi uses bundles). > I'm using many different generators/transformers im the 2.1.10 based > webapp. Where do > I find the detailed documentation about the needed blocks for > xpathdirectory-generator, > sourcewriting-transformer, parser-transformer, calendar-generator etc.? > Is there a 1:1 mapping of core sitemap components between 2.1.x and 2.2? > > I had a rant about this about a month back. Basically, Cocoon documentation is now a mess. Basically, go here: http://cocoon.apache.org/2.2/core-modules/core/2.2/1006_1_1.html You MAY find what you are looking for under "Sitemap Components". I say may because most of the documetentation is actually in the Javadoc. http://cocoon.apache.org/2.2/core-modules/core/2.2/apidocs/index.html Basically, work out the class for the transformer you are interested in, (from the first URL) then go to the Javadoc. The "daisy" documentation is better: http://cocoon.zones.apache.org/daisy/cdocs/g1/g1/g2/853.html?branch=1&language=1 If only because it is annotated and has direct links to the javadoc. Unfortunately, it has the same insane structure. I put the blame on Maven. I know it is more convenient to have documentation generated by Maven, but it makes for an appalling website. Hopefully, in future releases there may be some effort put into reorganise the information so humans can navigate it. 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. -- This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html. This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks Transtec Computers for their support. --=__Part012876C7.0__= Content-Type: text/html; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable
I am obviously not reading carefully enough...
cinclude is deprecated?   what is meant to be its replacemen= t??
 
Thanks
Derek

>>> On 2008/05/20 at 12:23, in message <4831F= DDB.8030106@tt.com.au>, Kamal Bhatt <kbhatt@tt.com.au> wrote:
<= /DIV>
Reinhard Haller wrote:
> R= einhard P=F6tz schrieb:
>>
>>   The Apache Coco= on Community is proud to announce the release of
>>   Co= coon 2.2.0.
> Thanks a lot!
>>
>>   Cocoo= n 2.2 introduces the idea of blocks. A block is the unit of
>>&nbs= p;  modularization in Cocoon, allowing the framework to be built upon.= (in
>>   comparison: Eclipse uses the term plugins, OSG= i uses bundles).
> I'm using many different generators/transformers i= m the 2.1.10 based
> webapp. Where do
> I find the detailed do= cumentation about the needed blocks for
> xpathdirectory-generator,<= BR>> sourcewriting-transformer, parser-transformer, calendar-generator e= tc.?
> Is there a 1:1 mapping of core sitemap components between 2.1.= x and 2.2?
>
>
I had a rant about this about a month back. B= asically, Cocoon
documentation is now a mess.

Basically, go here= :

http://cocoon.apache= .org/2.2/core-modules/core/2.2/1006_1_1.html

You MAY find what y= ou are looking for under "Sitemap Components".  I say
may because = most of the documetentation is actually in the Javadoc.

http://cocoon.apache.org/2.2/core-mod= ules/core/2.2/apidocs/index.html

Basically, work out the class for t= he transformer you are interested in,
(from the first URL) then go to t= he Javadoc.

The "daisy" documentation is better:

http://cocoon.zones.apache.org/daisy/cdocs/g1/g1/g2/853.html?= branch=3D1&language=3D1

If only because it is annotated and = has direct links to the javadoc.
Unfortunately, it has the same insane = structure.

I put the blame on Maven. I know it is more convenient to= have
documentation generated by Maven, but it makes for an appalling w= ebsite.
Hopefully, in future releases there may be some effort put into=
reorganise the information so humans can navigate it.

Last I lo= oked, most of the functionality was ported across. A lot of
things have= been deprecated (cinclude, XSP, etc...), so be aware of
this. If you w= ant information about migration options, I recommend
looking at my vari= ous posts last month on Cocoon 2.2 migration. Grzegorz
and others discu= ssed all the various migration options.

FYI, we have held off on mig= rating to Cocoon 2.2, but that is not
because of Cocoon 2.2s functional= ity. As frustrating as certain aspects
of Cocoon 2.2 can be (confusing = documentation being top of the list), I
would recommend upgrading to Co= coon 2.2 if only for a saner development
environment.


=
--=20
This message is subject to the CSIR's copyright terms and conditions,= e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.


This message has been scanned for viruses and dangerous content by MailScanner,=20
and is believed to be clean. MailScanner thanks Transtec Computers for their support. --=__Part012876C7.0__=--