You have three options (that come to mind): 1. You can chain request-maps together to call multiple events by using "request" typed response element. 2. You can call a single service which in turn calls two services, basically a wrapper. 3. You can use a service group which is essentially a shortcut for #2
You can find examples for 1 and 3 in the source code so I'm not going to explain them here unless you have specific questions. (#2 doesn't really need explaining) Regards Scott HotWax Media http://www.hotwaxmedia.com On 14/10/2010, at 3:02 AM, Deepa Priolkar wrote: > > Can we call multiple services one after another as part of controller > request-map entry > > <request-map uri="createPracticePersonJavaEvent"> > > <security https="false" auth="true"/> > > <event type="java" path="org.hotwax.mypractice.PracticeEvents" > invoke="createPracticePersonJavaEvent"/> > > <event type="java" path="org.hotwax.mypractice.PracticeEvents" > invoke="createPracticePersonJavaEvent1"/> > > <response name="success" type="view" > value="CreatePracticePersonEventJ"/> > > <response name="error" type="view" value="CreatePracticePersonEventJ"/> > > </request-map> > > The xsd allows this, but what should the first service return for the second > event to be called. And how will this work if the first event is of type > “simple” > > ============================================================================================================================Disclaimer: > This message and the information contained herein is proprietary and > confidential and subject to the Tech Mahindra policy statement, you may > review the policy at <a > href="http://www.techmahindra.com/Disclaimer.html">http://www.techmahindra.com/Disclaimer.html</a> > externally and <a > href="http://tim.techmahindra.com/Disclaimer.html">http://tim.techmahindra.com/Disclaimer.html</a> > internally within Tech > Mahindra.============================================================================================================================
smime.p7s
Description: S/MIME cryptographic signature
