axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaliya Ekanayake" <>
Subject Re: [Axis2] Implications of WSRM interfaces on Axis2 ClientAPI
Date Sat, 29 Oct 2005 14:01:47 GMT
This is what we have in Sandesha 1.0. It introduce this new RMContext that 
requires the jar to be in the classpath.


----- Original Message ----- 
From: "Srinath Perera" <>
To: <>
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();
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


View raw message