David Duhme wrote:
Are you using CachingURICoplet or URICoplet ?
I'm using the CachingURICoplet
David.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Hi David,
Just a hint: i keep cl:links for URI coplets, with cachingURI coplets i usually use cl:links and bookmarks to transfer some data to another coplet or pass something about its layout. If the targeted pipeline is still the same- say temporaryAttributes/application-uri is the same-, i think it is much easier to use a usual <a hred"uri?req-param1&req-param2">Next</a>, the portal-eventlink-transformer coming wth CachingURI will let your coplet pipeline know about the new req-params by events way . Then you can style it too. I guess the cachingURI coplets have been designed to do this. You develop your app and then put it in the portal as it is.
If you still want the cl:link, no idea, but just try replace $copletid by its actual value and add the temporaryAttributes/application-uri value.
Hope it helps, Phil
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
