Hi,

When I update the Axis2 binding with IDL-independent ServiceContract/Operation 
model, I find the dispatching from Axis2 service to the wired component is 
based on the proxy of the component and the invocation is then constrained by 
the java interfaces implemented by the proxy. After the discussion with Jeremy 
on IRC, we agree that we should directly use the interceptor chain to do the 
dispatching.

In fact, the logic exists in Abstract*InvocationHandler and 
JDK*InvocationHandler which are in the core package. I think it should be 
refactored into the SPI so that extensions can leverage it. What's the right 
place to host this SPI? WireService or?

I worked around the issue by copying the code in Axis2Service and it works in 
my testing. But I want to make sure it's owned by the right code.

Thanks,
Raymond

Reply via email to