ofbiz-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From varun bhansaly <vbhans...@gmail.com>
Subject query regarding SECAs
Date Mon, 19 Jul 2010 15:10:05 GMT
Hi,
I am facing issues with attribute "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

-- 
Regards,
Varun Bhansaly

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message