I thought it was useful to point out that was specifically a problem w/ a callback over binding.sca, as the proxy set up for a binding.ws (axis2) callback should be able to call back to the right client today, right?
Scott On Fri, Feb 6, 2009 at 12:55 PM, Raymond Feng <[email protected]> wrote: > Yes, the injected proxy for callback decides its target based on the > incoming invocation on the thread. For the concurrent access to the > composite-scoped component, synchronizations may be required for the > business logic but the callback proxy should be able to handle different > clients. >
