cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philippe Guillard <>
Subject Re: [Portal] coplet transformer links
Date Tue, 01 Feb 2005 18:01:26 GMT
David Duhme wrote:

>>>>Are you using CachingURICoplet or URICoplet ?
>>>I'm using the CachingURICoplet
>>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&amp;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,
>Thanks Phil.
>I think I will try it again with request parameters because it didn't
>work with <cl:links>, wether with the cachingURI coplet nor with the URI 
>coplet. With
>the URIcoplet the pipeline is called again when I hit a link but the 
>doesn't change and the old one from copletinstancedata/portal.xml is used.
>But I need to execute a diiferent query in my generator, so somehow I have
>to pass the changed parameters to the generator. Maybe me pipeline is 
>wrong and I'm fetching the old parameters all the time.
>        <map:match pattern="domino/view">
>                <map:generate type="domino-proxy">
>                        <map:parameter name="server" 
>value="{coplet:attributes/server}" />
>                        <map:parameter name="database" 
>value="{coplet:attributes/database}" />
>                        <map:parameter name="designelement" value="view" 
>                        <map:parameter name="designelementname" 
>value="{coplet:attributes/designelementname}" />
>                        <map:parameter name="query" value="
>                </map:generate>
>                <map:transform src="styles/behaelterkonten-view2html.xsl">
>                        <map:parameter name="copletid" value="{coplet:#}" 
>                        <map:parameter name="Count" value="10" />
>                </map:transform>
>                <map:serialize type="html" />
>        </map:match>
>Here again the part of my stylesheet:
>        <cl:links>
>                <cl:link coplet="$copletid" 
>                         path="attributes/query" 
> value="'&amp;RestrictToCategory=[username]&amp;Count=10&amp;Expand=1'" />
>                <cl:content>
>                        <img src="images/plus.gif" alt="Plus-Icon" 
>border="0" />
>                </cl:content>
>        </cl:links>
>Perhaps you could tell me the difference between 'temporaryAttributes' and 
>and what's the difference in definig attributes in 'copletdata/portal.xml' 

CL:links are working anyway, maybe you should try with an 
easier/simplier exemple with just 1 parameter and simple string value, i 
suggest to use XSP and log the values you get.
Looking at your samples i feel you can also use {request-param:query} in 
your sitemap for request parameters if it's the only thing missing!!

 From my notes :
- {copletData/attributes/query} to change an attribute initialized in 
file copletData/portal.xml
- {copletinstanceData/attributes/query} to change an attribute you 
initialized in file copletinstancedata/portal.xml
- {attributes/query} to set/change attribute never initialized
- {temporaryAttributes/application-uri} is the key point of cachingURI,  
best way to study it is looking at portal/coplets/html/sitemap.xmap


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message