Classification: UNCLASSIFIED Caveats: NONE
--- cut --- > > 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. Thanks. On the high level, I kind of understand path you are pointing to. But I need to take a closer look or get my hands dirty to really understand how Axis2 handles its configuration. One comment: I guess the strategy Tuscany uses is that I, as Tuscany core, will do least abstractions but will make everything available and you, as extension developers, will need to figure out how to work with what you need:-). It's smart and maybe necessary to implement SCA type of framework. It just seems to be a lot of (potentially repeated) work for the policy extension developers to figure out how a specific provider does things w/o abstraction. There could be multiple different providers for an extension point. --- cut--- > > OK, interesting, this would be a generic alternative to getting in and > manipulating the Axis configuration directly (in the Axis case). I > still come back to thinking isn't this what JAXWS is supposed to do > but maybe I need to give it some more thought. > I think it all boils down to who does what. I was hoping that with the help of Tuscany core, Axis2 WS binding provider would abstracts some common concepts, such as handlers, and implement them once and used by many. Compare this to the approach that each policy extension that needs to use Axis2 WS binding provider's handler needs to understand how Axis2 does it and repeatedly implements it in their code repeatedly. I agree that conforming to standards, such as JAX-WS, is a good strategy. Then Axis2 WS binding provider code needs to change? Note that this only matters to the extension developers, not component developers, because only extension developers need to access the internals. Gang Classification: UNCLASSIFIED Caveats: NONE
