Hi,Phil:
How to add copletID in cl:link?If you mean coplet="test-coplet" I already added it
in the beginning.So the error is not appear but the data like "attributes/param" still
not passed.
I try this in samples of current cvs version,steps below:
1.edit portal.xml in profiles\copletdata ,change GalleryViewer from URICoplet to
CachingURICoplet
2.add attributes:
<attribute>
<name>buffer</name>
<value xsi:type="java:java.lang.Boolean"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">true</value>
</attribute>
<attribute>
<name>handleParameters</name>
<value xsi:type="java:java.lang.Boolean"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">true</value>
</attribute>
<attribute>
<name>uri</name>
<value xsi:type="java:java.lang.String"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">cocoon:/coplets/html/application</value>
</attribute>
<attribute>
<name>temporary:application-uri</name>
<value xsi:type="java:java.lang.String"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">cocoon://samples/blocks/portal/coplets/gallery/viewer</value>
</attribute>
3.start jetty and then the Gallary Viewer did't work.
What can I do to make this work again? Or is it a bug?
If you were me ,how to solve this problem by using CachingURICoplet with bookmark?
WDYT?
Roy Huang
----- Original Message -----
From: "Philippe Guillard" <[EMAIL PROTECTED]>
To: "users cocoon" <[EMAIL PROTECTED]>
Sent: Wednesday, June 30, 2004 3:46 PM
Subject: Re: cl:links in cachingURI coplet ?
> Hi Roy,
>
> Outside the portal maybe means calling a pipeline from a sitemap that is
> not mounted by the portal sitemap, or child of portal sitemap, but not
> sure.
>
> I personnally passed to bookmarks!
> However, i made a quick try for you, Chris was right, you need to add
> the copletId in the cl:link like this :
>
> <cl:link coplet="test-coplet" path="attributes/param"
> value="tets"></cl:link>
>
> I didn't check the link but i don't have the exception below (using head
> cvs, that could be another reason since event-link-transformer has
> changed too).
>
>
> Phil
>
>
> On Wed, 2004-06-30 at 10:40, roy huang wrote:
> > 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]
> > >
> > >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>