WS-Policy Future Topics
By ritzmann on May 18, 2006
I already mentioned that there is still more we want to do in our WS-Policy implementation. Most of that relates to improving and completing integration into JAX-WS and Glassfish because the support for the generic WS-Policy framework is almost complete already. Here are a couple of topics we want to be looking into in the coming months:
- Support for external policy attachments
- This is not exactly straight-forward, because WS-PolicyAttachment leaves the concrete attachment mechanisms entirely in the open. We would very much like to get feedback on the needs and desires in that area.
- Call-back interface for the JAX-WS client to select policy alternatives
- Right now, if a service publishes policies with more than one policy alternative, we just randomly select the first alternative that suits us. We want to change that and provide an API that allows developers to actively select one of the policy alternatives.
- User-defined policy assertions
- Currently, all the supported policy assertions are hard-coded into WSIT and there is no facility where you could query the policies that the service or client is applying. We would like to define an API that makes it possible to query policies and support user-defined policy assertions.
- Flexible client configuration
- Clients are now looking up their configuration file from the classpath, which means that clients that share the same classpath also need to share the client configuration file. That means a lot of manual work to merge all client configurations into one file. This is aggravated by the fact that we can process only one target namespace per client configuration file. Obviously, this needs to improve and we might have to rethink the current format of the client configuration file.
These are just a few items from a long list. If you have any feedback on our WS-Policy implementation, we would love to hear from you.