Return-Path: 
 <cocoon-users-return-51027-apmail-xml-cocoon-users-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org
Received: (qmail 38495 invoked by uid 500); 23 May 2003 15:55:51 -0000
Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-users-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-users-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-users@xml.apache.org>
Reply-To: cocoon-users@xml.apache.org
Delivered-To: mailing list cocoon-users@xml.apache.org
Received: (qmail 38481 invoked from network); 23 May 2003 15:55:51 -0000
Received: from securemail3.diginsite.com (HELO securemail.diginsite.com)
 (206.107.78.16)
  by daedalus.apache.org with SMTP; 23 May 2003 15:55:51 -0000
Received: from warden.diginsite.com (warden-p.diginsite.com [208.29.163.248]
 (may be forged))
	by securemail.diginsite.com (8.12.9/8.12.4) with SMTP id h4NFtsBB006147
	for <cocoon-users@xml.apache.org>; Fri, 23 May 2003 08:55:54 -0700
Received: from no.name.available by warden.diginsite.com
          via smtpd (for securemail.diginsite.com [206.107.78.4]) with SMTP;
 Fri, 23 May 2003 08:55:54 -0700
Message-ID: <001a01c32143$ad7a1350$4efcc80a@RGOERS>
From: "Ralph Goers" <rg1915@dslextreme.com>
To: <cocoon-users@xml.apache.org>
References: <F4FDFA2571F2464EBCBCC8B12AED3E57011E1973@CHBEMAIL1>
        <001201c3213a$27f7d900$4efcc80a@RGOERS>
        <063e01c32140$5f96fca0$0500a8c0@hypernexinc.local>
 <33763.10.0.0.5.1053704825.squirrel@ags01.agsoftware.dnsalias.com>
Subject: Re: How to work with cocoon?
Date: Fri, 23 May 2003 08:55:04 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

While I agree that the documentation could be better, I have to comment that
Cocoon, as it is now, is documented far better than a lot of other open
source projects.  The main problem in this area is that Cocoon is powerful
and complicated.  To learn to use it from a programmer's perspective you
have to also understand Avalon - where IMHO the documentation is nowhere
near the level of Cocoon.

However, I think you missed the point of Dr. Martin's post.  Cocoon's
recommended method of building and deploying an application doesn't work for
at least some of us.  The fact that the default sitemap contains the cocoon
sample site means I can never use it.  I'd just like a sitemap that has all
the definitions with no pipeline.  I'd like all the definitions in
cocoon.xconf but then disable those I'm not going to use in my product.

Ralph

----- Original Message -----
From: "Antonio Gallardo" <agallardo@agsoftware.dnsalias.com>
To: <cocoon-users@xml.apache.org>
Sent: Friday, May 23, 2003 8:47 AM
Subject: Re: How to work with cocoon?


> Roger I Martin PhD dijo:
> >A tool that investigates a webapp and generates the
> > sitemap.xmap, cocoon.xconf and cocoon.roles a webapp developer needs
> > would be...<sigh>
>
> hi:
>
> It is not as easy as you wrote fro the sitemap. Remeber that the physical
> path of the resource into the machine and the request URI does not always
> are the same. A tool for generating the sitemap getting this into account
> is not easy.
>
> Cocoon is a great product and instead of a tool I think it weakness is the
> docs. To solve this many people is helping into this effort. Please check
> wiki as Derek suggested before.
>
> Another good source of docs are the mail list archieves.
>
> Best Regards,
>
> Antonio Gallardo.


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