Classification: UNCLASSIFIED Caveats: NONE > 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
Hi, Simon, The issue is not the classloader. The reason I had to modify the Tuscany-sca-all-1.6.jar was that I needed to modify the axis2.xml configuration file to add our Axis2 module declaration. Our Axis2 module package and handler code were packaged separately. Even with this approach, it's still not flexible enough because the module declaration I added in axis2.xml could only be a global one that applies to all services deployed in Axis2/Tuscany. We needed to the flexibility to declare different modules for difference services and references, which needs to be done in the service/reference creation stage, but Tuscany hid the service/reference creation from us, which is the right thing to do, so I could not do so. I like the Tuscany policy interceptor/handler approach much better. It just needs some refinement and enhancement to fully support the security. Thanks, Gang Classification: UNCLASSIFIED Caveats: NONE
