Thanks Jean-Christophe,

Actually my problem was resolved using URI coplets instead of CachingURI
coplets. Don't know why, except that CachingURI uses
portal-html-eventlink transformer.

Regards,

Phil

On Wed, 2004-04-21 at 17:06, Jean-Christophe Kermagoret wrote:
> Hi,
> 
> You can just use the 
> {coplet:attributes/name_of_attribute_defined_for_your_coplet} in a 
> parameter in your sitemap like usual :
>     <map:parameter name="category" value="{coplet:attributes/category}"/>
> This way, you can get it in your stylesheet or xsp (I think because I 
> don't use xsp)
> 
> Jean-Christophe
> 
> Philippe Guillard wrote:
> 
> >Mario,
> >
> >Really? I don't think this is with my advice :-) Can you tell me how you
> >did this? Specially the sitemap of the 2 coplets. Did you use util in
> >the XSP ? I'm still blocked.
> >
> >Regards,
> >
> >Phil
> >
> >
> >On Mon, 2004-04-19 at 16:58, Mariusz WÃjcik wrote:
> >  
> >
> >>Thanks it works :))))
> >>
> >>
> >>
> >>
> >>----- Original Message ----- 
> >>From: "Philippe Guillard" <[EMAIL PROTECTED]>
> >>To: "users cocoon" <[EMAIL PROTECTED]>
> >>Sent: Monday, April 19, 2004 6:00 AM
> >>Subject: Re: Coplets, cl:link - problems with sending and
> >>receivingparameters
> >>
> >>
> >>    
> >>
> >>>Hi Mario,
> >>>
> >>>I'm on the same thing without success, looking for a solution two...
> >>>
> >>>I think you need more configuration to pass the data from cl:link to the
> >>>other coplet, suggest to have a look here :
> >>>http://www.mail-archive.com/[EMAIL PROTECTED]/msg08500.html
> >>>
> >>>To get the request param in your XSP page i suggest declare
> >>>xmlns:util="http://apache.org/xsp/util/2.0 namespace then use a
> >>><util:get-sitemap-parameter name="MyParameter"/>
> >>>
> >>>Hope it helps !
> >>>
> >>>Phil
> >>>
> >>>
> >>>On Mon, 2004-04-19 at 04:31, Mariusz Wojcik wrote:
> >>>      
> >>>
> >>>>Hi I'm using new Cocoon Portal Engine (C. 2.1.4), and I have to send
> >>>>parameters between coplets (their context is generated by xsp pages).
> >>>>
> >>>>I have set coplet attribute in my copletdata portal.xml file:
> >>>>************************************
> >>>>(coplet data) portal.xml
> >>>>************************************
> >>>><coplet-data id="Pracownicy" name="standard">
> >>>>.................
> >>>><attribute>
> >>>><name>id</name><!-- My attribute name-->
> >>>><value xsi:type="java:java.lang.String"
> >>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>Hello</value>
> >>>><!-- My attribute default value-->
> >>>></attribute>
> >>>></coplet-data>
> >>>>
> >>>>************************************
> >>>>
> >>>>In the first xsp file I'm using cl:links commands to reload content,
> >>>>and setting "id" attribute value:
> >>>>************************************
> >>>>first xsp file
> >>>>************************************
> >>>>.............................................
> >>>><cl:links>
> >>>> <cl:link coplet="Pracownicy-1 path="copletData/attributes/id
> >>>>value="New_Value"/> <!-- setting up id value-->
> >>>> <p>
> >>>>  <cl:link coplet="Pracownicy-1"
> >>>>             path="copletData/attributes/uri"
> >>>>value="cocoon:/coplets/xsp/the_other_file.xsp"/> <!-- content
> >>>>reloading-->
> >>>>                      <cl:content>My Link Content</cl:content>
> >>>>        </p>
> >>>></cl:links>
> >>>>............................................
> >>>>************************************
> >>>>
> >>>>What I should write in the  the_other_file.xsp file to get the id
> >>>>parameter value?????
> >>>>
> >>>>************************************
> >>>>The other xsp file
> >>>>************************************
> >>>>????????????????????????
> >>>>???????????????????????
> >>>>************************************
> >>>>
> >>>>Thanks for help
> >>>>Mario
> >>>>
> >>>>
> >>>>        
> >>>>
> >>>---------------------------------------------------------------------
> >>>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]
> >>
> >>
> >>    
> >>
> >
> >
> >---------------------------------------------------------------------
> >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]

Reply via email to