Easier syntax and parameters/attributes (no need to handle them in service_2, though see also result-to-context ) for group version
Also more possibilities with send-mode and async attributes
https://cwiki.apache.org/confluence/display/OFBTECH/Service+Engine+Guide#ServiceEngineGuide-ServiceGroups
Maybe in some cases Sample2 could be easier, but I don't see any OTTOMH
Jacques
From: "Wai" <[email protected]>
Is there any advantage/difference between Sample1 and Sample2 when it comes
to calling multiple services?
Sample1:
========
<service name="someService_1" engine="group" ...>
<group>
<invoke name="someService_A"/>
<invoke name="someService_B"/>
</group>
</service>
Sample2:
========
<service name="someService_2" engine="simple"
location=".../SomeServices.xml" invoke="someService_2" ...>
...
</service>
File SomeServices.xml
---------------------
<simple-method method-name="someService_2"...>
<call-service service-name="someService_A" ...>...</call-service>
<call-service service-name="someService_B" ...>...</call-service>
</simple-method>
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Calling-multiple-services-tp4226530p4226530.html
Sent from the OFBiz - User mailing list archive at Nabble.com.
