Hi Sanjiva, I find this statement odd -- the JAXWS code has been in place for several months and is clearly another API (yes, I know that it hasn't been packaged in a release, but neither have Matt's changes.) Nobody is advocating that end-users go through the OperationClient, however any other programming models that are layered on top of the base Axis2 runtime (e.g. JAXWS) probably will.
Matt's modifications made no reference in any of the comments about this being a new or the preferred API, so I don't see how users are going to be aware of these modifications. It shouldn't make a difference at all where the logic lives -- they should be using what we tell them to use. -Bill On Fri, 2007-01-26 at 04:51 +0530, Sanjiva Weerawarana wrote: > On Wed, 2007-01-24 at 22:38 -0600, Nicholas L Gallardo wrote: > > > > Matt's patch is intended to push some logic that exists in the > > ServiceClient down to the OperationClient. I don't see this as a > > change in the API, just an addition to the behavior based on certain > > criteria. Would there be a reason for not including this in the > > OperationClient rather than the ServiceClient? > > It changes the API because we've so far had exactly one way to invoke a > service: using the ServiceClient API. Now we have two. I view that as a > major API change because the user experience has changed dramatically. > > Matt, is this change meant to be something for say JAX-WS to use and not > for end users? If so can we document it as such? If not I don't > understand how Sandesha has been able to handle every RM scenario we've > seen so far without the need for this API change. > > Sanjiva. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
