Hi, Sebastien and Raymond, thanks for your responses on the other thread... I will follow up the issues there one by one. Here I want to discuss about PolicyHandlers.
Every policyset encapsulate policies that could follow a standard model such as ws-policy or could follow a custom model as in the case of our axis2-config-param policy and jdkLogging policy. Each implementation and binding type could have its own way of interpretting these policy models and affecting them accordingly in the binding or implementation. For example the axis2 binding simply injects the ws-policy into the axis configuration. Some other binding that works with ws-policy might handle this differently. This sort of 'policy handling' is what I had initially thought of as something that can be dealt by PolicyHandler classes. Now I find that how these classes look and what they do inside it entirely upto the binding and implementation types including when they are called i.e. during start or stop of the binding/implementatoin or during invocation of service methods etc. Given that the PolicyHandler is getting to be something internal to the binding or implementation do we ever have to define an SPI for it ? I am basically questioning the current implementation of defining PolicyHandler classes in a services sort of file in META-INF directory, loading and instantiating them, invoking them and so on. Is there a view-point I am missing here? Thanks -Venkat
