Gang Yang wrote:
--- Cut ---
How about plugging your code into an Axis2 handler instead of a Tuscany
handler? Is there is a way to get control after Axis2 has built the
SOAPFault and before the fault is sent on the wire?
Simon
Our security software has been integrated with Axis2 and other WS
frameworks such as JAX-WS and JAX-RPC. The problem here is that we are
supposed to integrate with Tuscany. Axis2 is just a ws binding provider
and it's hidden behind Tuscany:-). In an earlier quick effort, I have
modified tuscany-sca-all-1.6.jar to add Axis2 handlers in a hard-coded
way. But that's not a good solution and it's not flexiable.
Why do the Axis2 handlers need to be part of the Tuscany jar? Is this
a classloader issue? Perhaps there is a way to customize Tuscany's use
of classloaders to allow Axis2 handlers to be loaded from outside the
Tuscany jar. For example, it's possible to set up Tuscany 1.x to run with
a different version of Axis2 from that included with the tuscany-sca-all
jar, as described in [1] (please read the whole thread).
Simon
[1] http://www.mail-archive.com/user@tuscany.apache.org/msg02597.html
