The composite reference target invoker variants are for forward vs callback invocation. Their only real difference is that they instantiate a different invocation handler to pass through to. It may be worth keeping them separate. As far as I can tell, they are not further extended so there is no issue with that.
On 10/26/06, Jim Marino <[EMAIL PROTECTED]> wrote:
Following up on the move of non-blocking thread dispatches to NonBlockingBridgingInterceptor, I merged the asynchronous variant of TargetInvoker with its synchronous counterpart in Component implementations. This has the effect of simplifying extensions since they only need to extend TargetInvokerExtension; the handling of message and correlation ids will be handled automatically by the wiring fabric. This will hopefully provide Ant's scripting extension with built-in async support. As part of this refactor, I also simplified the TargetInvoker hierarchy for Java component types by eliminating PojoInvoker and combining AsyncJavaTargetInvoker and JavaTargetInvoker. I did not make the analogous change for References (they still have the two variants of TargetInvoker), but I believe we can perform a similar merge. Raymond or Ignacio, do you want to take a look at this? Jim
