Hi Chris,
I meet the similar situation.I don't understand "calling your pipeline from
outside the portal".How to define a pipeline called in a portal ? And what need to do
if I call a pipeline outside a portal? Can you describe it more in detail?
Thanks
Roy Huang
----- Original Message -----
From: "Christian Mayrhuber" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, June 22, 2004 5:07 PM
Subject: Re: cl:links in cachingURI coplet ?
> On Monday 21 June 2004 19:01, Philippe Guillard wrote:
> > Hi,
> >
> > I'm using cl:links OK with URI coplet but can't make cl:links work with
> > cachingURI coplet in rls 2.1.5. Should i change something ?
> >
> > I think the point is that cachingURI Coplet uses portal-html-eventlink
> > transformer.
> >
> > Error:
> > org.apache.cocoon.ProcessingException: Failed to execute pipeline.:
> > java.lang.RuntimeException: org.xml.sax.SAXException: copletId must be
> > passed as parameter or in the object model within the parent context.
> >
> > It seems that portal-html-eventlink needs copletId, i tried to give
> > <map:parameter name="copletId" value="{request-param:copletid}"/>
> > or <map:parameter name="copletId" value="id of my coplet"/>, no success
> >
> > Any idea?
>
> I guess you are calling your pipeline from outside the portal, if you do this
> the {coplet:#} and any other coplet data is unknown, so you have to
> specifiy the "copletId" as string. The coplet transformer is in no
> way different in this regard.
>
> --
> lg, Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
