why u need RM methods when u do not have RM jar in the classpath?
On 10/29/05, Jaliya Ekanayake <[EMAIL PROTECTED]> wrote: > This is what we have in Sandesha 1.0. It introduce this new RMContext that > requires the jar to be in the classpath. > > Thanks, > > Jaliya > ----- Original Message ----- > From: "Srinath Perera" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Saturday, October 29, 2005 7:37 AM > Subject: Re: [Axis2] Implications of WSRM interfaces on Axis2 ClientAPI > > > I am 0- on moving the constants to the core > > how about following > > Call call = new Call(); > call.engageModule("RM"); > RMContext rcontext = (RMContext)call.getExtentionContext(RM_MODULE); > //return the RMContext from extension registry > > RMContext will have RM specific methods and provide way to monitor the RM > > IMHO once the user enable RM, user is not allowed to set sequence id > ect .. at the first message RM will automatically call create sequence > ..ect and provide sequenceIDs/UUID for the messages. Once the RM is > started Axis and RM control what happen .. User can quary status via > RMContext .. He may have a terminateSequence method() .. for premature > termination > > Thanks > Srinath > > >
