Policy Relationship with JAX-WS

Despite the fact that many developers keep saying (especially when looking for a new job ;-) they do not mind
learning new technologies and APIs, when it comes to reality a lot of them mind. Last time I wrote about
WSIT. The implementation brings new quality features to web services technology
and the key to this is having policies attached to particular services. You can read about the details
in Marek's blog. The good news is, that adoption of WSIT does not mean switching to a totally different world.

How is it possible? WSIT is actually based on JAX-WS
implementation, which provides a convenient interface (SPI) for plugging WSDL extensions into processing code.
This mechanism is then used naturally for our policy implementation. The current version plugs into JAX-WS code for runtime WSDL processing. It means
parsing (on both client and server sides) and generation (just server side) of WSDL files.
Tooltime extensions will be implemented soon. Additional implementation information can be found at Fabian's blog.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.