SanjivaI also agree on your comments regarding the operation client.Now about the whole session/clustering thing. You mention that outside of Axis2 the concept of Service Group does not exist !!!So a client would expect to interact with Services from two Service Groups in a single session.
Thats th
On Tue, 2006-10-10 at 17:54 -0500, Deepal Jayasinghe wrote:
> Why do we need operation client ?
??? You gotta be kidding.
We have it because that's the client API for a generic MEP.
> As Dennis suggested , having annon name as public static seems not that
> good , so we need to remove th
Hi,
public MessageContext sendReceive(MessageContext req){}
public void sendReceiveNonBlocking(MessageContext req){}
public fireAndForget(MessageContext req){}
public sendRobust(MessageContext req){}
Huge +1.
Currently we provide SwA support only in the OperationClient level,
cause we need
Deepal,
Please create JIRA issue(s) and let's work on them.
thanks,
dims
On 10/10/06, Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
Hi All;
Few note from todays Hackathon we had at ApacheCon US.
We are having very ugly name called finalizeInvoke() in service client
with restriction, so we (Gl
Hi All;
Few note from todays Hackathon we had at ApacheCon US.
We are having very ugly name called finalizeInvoke() in service client
with restriction, so we (Glen and I agreed) to remove that method and
move the code into cleanup (well I am doing the changes in current
codebase).
Why do we need
