few comments 1) Pls make sure InOnlyMEPClient ect have a constructer that accept the client repository, other wise user should be creating a service context ect
2) Option have setTransportInfo method that accet sender and receiving transport, but it do not make sense for the InOnly case. We need a way to handle this Srinath On 11/30/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote: > +1 > > On 11/30/05, Eran Chinthaka <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I would like to propose following changes to the client api. > > > > > > > > Rename InOnlyMEPClient to RobustInOnlyMEPClient and clean up as needed > > Add InOnlyMEPClient to support true fire-and-forget behavior > > move the convenience methods in MessageSender to InOnlyMEPClient > > (RobustInOnlyMEPClient) and remove MessageSender > > Well, let me explain a bit more about the third item. Current MessageSender > > class only provides two convenience methods for InOnly invocation. If we > > can pull those two members up, we can remove that class without a problem. > > I'd like to do the same for the Call class as well, but since "Call" is sort > > of a legacy thing, I do not want to change it. > > > > -- Chinthaka > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ >
