I'm guessing here that you want service2 to be triggered before service1 and ultimately have it alter the value of attribute1 before it gets passed to service1?
If so, then just define attribute1 as INOUT and then modify it inside service2 and get rid of attribute2 altogether. Regards Scott HotWax Media http://www.hotwaxmedia.com On 20/07/2010, at 4:26 PM, varun bhansaly wrote: > Thanks Jacques, Scott, is there any other way to achieve the same w/o > customizing the framework code ? > > This is the actual problem > http://ofbiz.135035.n4.nabble.com/query-regarding-SECAs-tt2294160.html > > Thanks, > > On Tue, Jul 20, 2010 at 9:34 AM, Scott Gray <[email protected]>wrote: > >> Won't work, I'm pretty sure nothing will after looking at the code. >> >> Regards >> Scott >> >> HotWax Media >> http://www.hotwaxmedia.com >> >> On 20/07/2010, at 3:57 PM, Jacques Le Roux wrote: >> >>> Try nullField, ie >>> <set field-name="attribute1" value="nullField"/> >>> >>> Jacques >>> >>> From: "varun bhansaly" <[email protected]> >>>> Hi, >>>> I am implementing a scenario using SECAs, where in it would be required >> to >>>> set a field to NULL or empty string. >>>> Is it possible to set a field to NULL using the set tags of eca xmls. >>>> I've tried with <set field-name="attribute1" value=""/> but this does >>>> not set attribute1 to empty string >>>> -- >>>> Regards, >>>> Varun Bhansaly >>>> >>> >> >> > > > -- > Regards, > Varun Bhansaly
smime.p7s
Description: S/MIME cryptographic signature
