Please dont put the same question with different names ;-)
Ravi
On Mon, Jul 19, 2010 at 2:39 PM, Pradipta Ghosh <
[hidden email]
> wrote:
> Hi.
> I am facing issues with atrribute result-map-name in my SECA definition
>
> Listed below is the scenario i am trying to implement
>
> Service definitions -
>
> <service name="CA" engine="java" location="locationName1"
> invoke="functionName1">
> <attribute name="attribute1" type="String" mode="IN" optional="true"/>
> <attribute name="partyId" type="String" mode="INOUT" optional="true"/>
> </service>
>
> <service name="CC" engine="java" location="locationName2"
> invoke="functionName2">
> <attribute name="attribute1" type="String" mode="IN" optional="true"/>
> <!-- This is an auto generated id generated by the framework -->
> <attribute name="attribute2" type="String" mode="OUT" optional="true"/>
> <!-- This is an auto generated id generated by the framework -->
> <attribute name="partyId" type="String" mode="INOUT" optional="true"/>
> </service>
>
> SECA definition -
>
> <eca service="CA" event="invoke">
> <action service="CC" mode="sync" result-to-context="false"
> result-map-name="result"/>
> <set field-name="attribute1" env-name="${result.attribute2}"/>
> </eca>
>
> The problem -
> For each invocation of service "CA", same result map "result" remains the
> same until & unless server is restarted. Is there any thing wrong with the
> SECA definition ?
>
> Also, Is there any way to set a field name as null in SECA set tags -
> I've tried with <set field-name="attribute1" value=""/> but this does not
> set attribute1 to empty string
>
> Thanks..
>