Classification: UNCLASSIFIED Caveats: NONE > > Yep, the policy providers get the opportunity to see binding specific > configuration. You have to know what binding you're dealing with of > course and in the ws/axis case it's an Axis2BaseBindingProvider object > that the policy provider sees. Once you have that you can get at the > Axis ConfigurationContext and you're off to the races. See > > http://svn.apache.org/repos/asf/tuscany/sca-java- > 2.x/trunk/unreleased/testing/itest/interceptors/src/main/java/sample/In > teractionBindingWSServicePolicyProvider.java > > We may need to work on that interface a bit but you get the idea, > > Other policies need to do other things with the configuration such as > turning on MTOM but without access to the whole context it's difficult > to predict what a policy might need to do. >
Hi, Simon, I followed your pointer to access Axis2's configuration context. I was able to get the configuration context on the service side, but the configuration context on the client side is null. I'm not sure if it's the service vs reference that made the difference or the launch mechanism that made the difference. My testing configuration is a WAR deployed into Jboss with policy extension applied to service and a command line client (jar) with policy extension applied to reference. Gang Classification: UNCLASSIFIED Caveats: NONE
