Hi Scott, I had already seen the implementations in ServiceEcaSetField.java. I would not want to introduce yet another SECA to remove partyId. Guess introducing a value such (as setToNull) for the format attribute would not break any thing else.
Thanksm On Tue, Jul 20, 2010 at 11:57 AM, Scott Gray <[email protected]>wrote: > So you want some of the results from CC to go into CA but not all of them? > I think the code only allows for an all or nothing approach, the only real > workaround is to add another service that manually calls CC but does not > return the unwanted fields. You're welcome to look at the implementations > yourself, they're in ServiceEcaAction.java and ServiceEcaSetField.java. > > Perhaps ideally a SECA action would provide a bit more flexibility similar > to what we have in the minilang call-service attribute whereby you can use > child elements to specify exactly what should be done with each result > field. > > Regards > Scott > > On 20/07/2010, at 5:06 PM, varun bhansaly wrote: > > > The issue is with attribute name = "partyId" both CC & CA are custom > > services working fine independently. > > > > partyId comes in the output of CC, the idea is to either > > > > 1. reset partyId to null OR > > 2. not to send it in input to CA. > > > > for 2. I have tried with result-map-name attribute, but it remains the > same > > (as observed while context is printing in CA). > > > > I would not want to change any of the input output params since they work > > fine independently. > > > > Thanks > > > > > > > > On Tue, Jul 20, 2010 at 10:14 AM, Scott Gray <[email protected] > >wrote: > > > >> 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 > >> > >> > > > > > > -- > > Regards, > > Varun Bhansaly > > -- Regards, Varun Bhansaly
