As I explained in my last blog entry
, we moved the policy core code with support for WS-Policy
into a separate workspace on java.net several weeks ago: https://policy.dev.java.net/
. Since late January that code has been successfully reintegrated into Metro
. It was a very smooth process indeed. I set up a build job to create a policy.jar with Maven 2
. Then I removed the policy core code from the Project Tango
code base and added the policy.jar to the compile class path. The builds have been working flawlessly ever since. You do not actually notice any difference from the outside because the policy.jar like all other run-time libraries for Metro
is repackaged in Metro's webservices-rt.jar.
One final step that is still outstanding and that we will realize with JAX-WS 2.2 remains. Right now Project Tango still contains all policy code that has a dependency on JAX-WS. That code will be moved into JAX-WS 2.2 and out of Project Tango entirely. This will allow us to support e.g. WS-Addressing policy assertions directly from JAX-WS without the addition of Project Tango.
Tags: GlassFish, WS-Policy, Web Services, Metro, JAX-WS, Project Tango, WSIT