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?

Regards,

Phil

------------------------------

Here details :


Coplet_data
___________
<coplet-data id="topics" name="standard">
      <title>topics</title>
      <coplet-base-data>CachingURICoplet</coplet-base-data>
      <attribute>
        ......
      </attribute>
      <attribute>
        <name>parameter1</name>
        <value xsi:type="java:java.lang.String"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>0</value>
      </attribute>      
</coplet-data>

The appication pipeline
______________________________
<map:match pattern="application">
        <map:generate
        src="{coplet:temporaryAttributes/application-uri}?copletid={coplet:#}"/>
        <map:transform type="portal-html-eventlink">
        <map:parameter name="attribute-name" value="application-uri"/>
        <!-- <map:parameter name="copletId" value="topics-1"/> -->
        </map:transform>
        <map:serialize type="xml"/>
</map:match>

The "temporary-application" pipeline
____________________________________

<map:generate src="topics.xsp" type="serverpages"/>
<map:call resource="mainxsl"/>
<!-- transform xsl with file below -->
<map:serialize/>

my cl:link in xsl
______________
<cl:links>
<cl:link path="copletData/attribute/parameter1" value="test1"></cl:link>
<cl:link path="attribute/parameter2" value="test2"></cl:link>   
<cl:content>link</cl:content>
</cl:links>





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to