Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 82731 invoked from network); 30 Aug 2007 14:16:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Aug 2007 14:16:04 -0000 Received: (qmail 4637 invoked by uid 500); 30 Aug 2007 14:15:52 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 4579 invoked by uid 500); 30 Aug 2007 14:15:52 -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 4561 invoked by uid 99); 30 Aug 2007 14:15:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2007 07:15:52 -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: domain of suminub@gmail.com designates 66.249.92.168 as permitted sender) Received: from [66.249.92.168] (HELO ug-out-1314.google.com) (66.249.92.168) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 30 Aug 2007 14:15:44 +0000 Received: by ug-out-1314.google.com with SMTP id m3so180933ugc for ; Thu, 30 Aug 2007 07:15:23 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=VRin8Oconqj2bt8285AWETcbGoX9/wQZd9O9IyxULbdFlmLDmher8hj1n22eP31YfAQnDrQi1A7fMhYUnKYjqNFohp4s8OwjQbhycv83O1/MHPmeaGETiW13CCglPFKQY5f6zhengLi29N6f4YLygRjNruocwU5UCCV0WUg3ZUc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=ikLeD61dqQs45S6QcKSGnXvJJneabixo3Fic2lOC69aoDV0ZGDlZ6KwzasW9WsVFWJnM+gMluqdWfRqasCBPg9uBlfOKX8NtHG8H73BWORI7eblQ8QaYJYWHBpkWpc+A+WfDtINwYii60YEtHKHeEFCI/Cors+lsmT/6Ay68WAw= Received: by 10.142.103.6 with SMTP id a6mr25122wfc.1188483321864; Thu, 30 Aug 2007 07:15:21 -0700 (PDT) Received: by 10.142.83.20 with HTTP; Thu, 30 Aug 2007 07:15:21 -0700 (PDT) Message-ID: Date: Thu, 30 Aug 2007 10:15:21 -0400 From: "Edward S" To: users@cocoon.apache.org Subject: Re: cocoon: protocol In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5983_29812472.1188483321829" References: X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_5983_29812472.1188483321829 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline never mind. i figured out that cocoon: wasnt the protocol I should be using there thanks -Ed. On 8/30/07, Jasha Joachimsthal wrote: > > Could you please send the pipeline snippet in which you are using the > cocoon protocol? > > > Jasha Joachimsthal > > Hippo > Oosteinde 11 > 1017 WT Amsterdam > The Netherlands > +31 (0)20 5224466 > > www.hippo.nl > > ------------------------------ > *From:* Edward S [mailto:suminub@gmail.com] > *Sent:* donderdag 30 augustus 2007 15:55 > *To:* users@cocoon.apache.org > *Subject:* Re: cocoon: protocol > > > thanks Jasha. > I am trying to use it in a sitemap and am getting a 'unknown protocol: > cocoon' error. > > Any idea why this is happening? > > thanks > > Ed. > > > > On 8/30/07, Jasha Joachimsthal wrote: > > > > Hi Ed, > > > > The difference between cocoon:/ [1] and cocoon:// [2] is that [1] stays > > within the current sitemap to find a matching pipeline and [2] returns to > > the root sitemap of your project to find a match. They may end up to the > > same pipeline but [1] is more efficient if you know for sure the match is in > > the current sitemap. > > > > Regards, > > > > > > Jasha Joachimsthal > > > > Hippo > > Oosteinde 11 > > 1017 WT Amsterdam > > The Netherlands > > +31 (0)20 5224466 > > > > www.hippo.nl > > > > ------------------------------ > > *From:* Edward S [mailto:suminub@gmail.com] > > *Sent:* donderdag 30 augustus 2007 15:37 > > *To:* users@cocoon.apache.org > > *Subject:* cocoon: protocol > > > > > > hey guys, > > > > How does the cocoon:/ and cocoon:// protocol work? > > > > thanks > > > > Ed > > > > > > > ------=_Part_5983_29812472.1188483321829 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
never mind. i figured out that cocoon: wasnt the protocol I should be using there
 
thanks
 
-Ed.


 
On 8/30/07, Jasha Joachimsthal <j.joachimsthal@hippo.nl> wrote:
Could you please send the pipeline snippet in which you are using the cocoon protocol?
 

Jasha Joachimsthal

Hippo
Oosteinde 11
1017 WT Amsterdam
The Netherlands
+31 (0)20 5224466

www.hippo.nl


From: Edward S [mailto:suminub@gmail.com]
Sent: donderdag 30 augustus 2007 15:55
To: users@cocoon.apache.org
 Subject: Re: cocoon: protocol

 
thanks Jasha.
I am trying to use it in a sitemap and am getting a 'unknown protocol: cocoon' error.
 
Any idea why this is happening?
 
thanks
 
Ed.


 
On 8/30/07, Jasha Joachimsthal <j.joachimsthal@hippo.nl > wrote:
Hi Ed,
 
The difference between cocoon:/ [1] and cocoon:// [2] is that [1] stays within the current sitemap to find a matching pipeline and [2] returns to the root sitemap of your project to find a match. They may end up to the same pipeline but [1] is more efficient if you know for sure the match is in the current sitemap.
 
Regards,
 

Jasha Joachimsthal

Hippo
Oosteinde 11
1017 WT Amsterdam
The Netherlands
+31 (0)20 5224466

www.hippo.nl


From: Edward S [mailto:suminub@gmail.com]
Sent: donderdag 30 augustus 2007 15:37
To: users@cocoon.apache.org
Subject: cocoon: protocol

 
hey guys,
 
How does the cocoon:/ and cocoon:// protocol work?
 
thanks
 
Ed
 


------=_Part_5983_29812472.1188483321829--