Thanks for you help Jacques, In seca, i used event="return" instead of event="commit", it worked i got both custRequestId, workEffortId, and also created a row in the CustRequestWorkEffort.
Regards, Naveen. On Tue, Sep 14, 2010 at 5:27 PM, Jacques Le Roux < [email protected]> wrote: > You may mix both. Group services allow you to pass data just created. There > are other ways of course... > > > Jacques > > From: "Naveen Kumar" <[email protected]> > >> Hi Jacques, >> >> I am creating workeffort based on some condition from request, for example >> if request is support then only it should call services createWorkEffort, >> createWorkEffortRequest in backend, so using service group it is possible >> specify condition. >> >> Regards, >> >> Naveen. >> >> On Tue, Sep 14, 2010 at 4:49 PM, Jacques Le Roux < >> [email protected]> wrote: >> >> With a SECA you can use only what is already in the context. >>> You may try a service group using result-to-context="true" >>> Jacques >>> >>> From: "Naveen Kumar" <[email protected]> >>> >>> Hi All, >>> >>>> >>>> After creation of Workeffort, i want to call one more service >>>> createWorkEffortRequest, I want to know how to get workEffortId and >>>> custRequestId after createCustRequest and createWorkEffort services are >>>> invoked. >>>> >>>> Regards, >>>> >>>> Naveen. >>>> >>>> >>>> On Thu, Aug 26, 2010 at 4:12 PM, Naveen Kumar <[email protected] >>>> >wrote: >>>> >>>> OK, I tried with seca and setting the required field using <set >>>> >>>>> field-name= >>>>> ...... /> , it worked for me, and created entry in both WorkEffort and >>>>> CustRequest. >>>>> >>>>> Regards, >>>>> >>>>> Naveen. >>>>> >>>>> >>>>> >>>>> On Thu, Aug 26, 2010 at 4:05 PM, Scott Gray < >>>>> [email protected] >>>>> >wrote: >>>>> >>>>> That's because the Entity ECA handler only has the entity fields of >>>>> >>>>>> CustRequest to work with. Any input parameters that aren't used by >>>>>> the >>>>>> createCustRequest service never make it past the service event handler >>>>>> into >>>>>> the call chain. >>>>>> >>>>>> Regards >>>>>> Scott >>>>>> >>>>>> On 26/08/2010, at 9:46 PM, Naveen Kumar wrote: >>>>>> >>>>>> > Hi Scott, >>>>>> > >>>>>> > Thanks for the reply, >>>>>> > >>>>>> > But i am sending required parameter in the form as a hidden field, >>>>>> but >>>>>> after >>>>>> > creation of request those parameters are not available for >>>>>> workeffort >>>>>> > creation. >>>>>> > >>>>>> > Regards, >>>>>> > >>>>>> > Naveen. >>>>>> > >>>>>> > On Thu, Aug 26, 2010 at 1:53 PM, Scott Gray < >>>>>> [email protected] >>>>>> >wrote: >>>>>> > >>>>>> >> The call to createWorkEffort is missing required parameters, you >>>>>> are >>>>>> >> probably better off either using a service group to combine the two >>>>>> services >>>>>> >> into one or create a wrapping service to do the same. Service ECAs >>>>>> are >>>>>> >> really only useful when the additional services don't require >>>>>> anything >>>>>> >> additional in the context other than what is going in to or coming >>>>>> out >>>>>> of >>>>>> >> the triggering service. >>>>>> >> >>>>>> >> Regards >>>>>> >> Scott >>>>>> >> >>>>>> >> HotWax Media >>>>>> >> http://www.hotwaxmedia.com >>>>>> >> >>>>>> >> On 26/08/2010, at 8:14 PM, Naveen Kumar wrote: >>>>>> >> >>>>>> >>> Hi BJ, >>>>>> >>> >>>>>> >>> I am using EECA, >>>>>> >>> >>>>>> >>> Here is my code >>>>>> >>> >>>>>> >>> <eca entity="CustRequest" operation="create" event="return"> >>>>>> >>> <condition field-name="custRequestTypeId" operator="equals" >>>>>> >>> value="RF_SUPPORT"/> >>>>>> >>> <action service="createWorkEffort" mode="sync"/> >>>>>> >>> </eca> >>>>>> >>> >>>>>> >>> Regards, >>>>>> >>> >>>>>> >>> Naveen. >>>>>> >>> >>>>>> >>> On Thu, Aug 26, 2010 at 1:37 PM, BJ Freeman <[email protected]> >>>>>> wrote: >>>>>> >>> >>>>>> >>>> there are two types of ECA's, EECA and SECA >>>>>> >>>> could you provide more info. >>>>>> >>>> >>>>>> >>>> ========================= >>>>>> >>>> BJ Freeman <http://bjfreeman.elance.com> >>>>>> >>>> Strategic Power Office with Supplier Automation < >>>>>> >>>> http://www.businessesnetwork.com/automation/viewforum.php?f=52> >>>>>> >>>> Specialtymarket.com <http://www.specialtymarket.com/> >>>>>> >>>> Systems Integrator-- Glad to Assist >>>>>> >>>> >>>>>> >>>> Chat Y! messenger: bjfr33man >>>>>> >>>> >>>>>> >>>> >>>>>> >>>> Naveen Kumar sent the following on 8/26/2010 12:50 AM: >>>>>> >>>> >>>>>> >>>> Hi All, >>>>>> >>>>> >>>>>> >>>>> I was working on ECA, i have struck with this error, can any one >>>>>> help >>>>>> >> me, >>>>>> >>>>> to >>>>>> >>>>> solve this issue. >>>>>> >>>>> >>>>>> >>>>> 1. I want to create WorkEffort in backend, when request is >>>>>> created, >>>>>> so >>>>>> >> i >>>>>> >>>>> have written ECA to do this job. >>>>>> >>>>> 2. When i tried to create request, i am getting this error >>>>>> >>>>> >>>>>> >>>>> The Following Errors Occurred: >>>>>> >>>>> >>>>>> >>>>> Error: Error trying to begin transaction, could not process >>>>>> method: >>>>>> The >>>>>> >>>>> current transaction is marked for rollback, not beginning a new >>>>>> >>>>> transaction >>>>>> >>>>> and aborting current operation; the rollbackOnly was caused by: >>>>>> Service >>>>>> >>>>> [createWorkEffort] threw an unexpected >>>>>> >>>>> exception/errororg.ofbiz.service.ServiceValidationException: The >>>>>> >> following >>>>>> >>>>> required parameter is missing: [IN] >>>>>> >> [createWorkEffort.currentStatusId]The >>>>>> >>>>> following required parameter is missing: [IN] >>>>>> >>>>> [createWorkEffort.workEffortName]The following required >>>>>> parameter >>>>>> is >>>>>> >>>>> missing: [IN] [createWorkEffort.workEffortTypeId] (The following >>>>>> >> required >>>>>> >>>>> parameter is missing: [IN] [createWorkEffort.currentStatusId]The >>>>>> >> following >>>>>> >>>>> required parameter is missing: [IN] >>>>>> >> [createWorkEffort.workEffortName]The >>>>>> >>>>> following required parameter is missing: [IN] >>>>>> >>>>> [createWorkEffort.workEffortTypeId]) calling service >>>>>> >>>>> setCustRequestStatus >>>>>> >>>>> in createCustRequest >>>>>> >>>>> >>>>>> >>>>> >>>>>> >>>>> 3. I am sending this three fields (workEffortName, >>>>>> >>>>> WorkEffort.currentStatusId, workEffortTypeId) as hidden fields >>>>>> in >>>>>> >> request >>>>>> >>>>> form. >>>>>> >>>>> >>>>>> >>>>> >>>>>> >>>> >>>>>> >> >>>>>> >> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >> >
