Friday Sep 07, 2007

WS-Policy 1.5 published as a W3C recommendation

A few days ago, WS-Policy 1.5 was published as a standard by the W3C. Check out the press release for the relevant links. Monica Martin and me have been active members of the working group and I have been impressed by Monica's capacity and dedication to creating standards of high quality.

We are actively working on support for WS-Policy 1.5 in Project Tango. You can already see our work in action on our interop test site.

Technorati:

Friday May 04, 2007

WSIT and WS-Policy at JavaOne 2007

We have quite a number of sessions, BOFs and labs that talk about Web Services, JAX-WS, WSIT and .NET interoperability. WS-Policy plays a role everywhere that WSIT is covered. It is the base technology to configure all the required functionality. You may find me at POD #966 or our hands-on lab. Here is a list of events (shamelessly stolen and adapted from Arun Gupta's blog):
 

Time Session ID/Title Speaker(s)
Monday, 05/08/07
10:30 AM - 7:30 AM GlassFish Day @ Community One  
Tuesday , 05/08/2007
11:15 AM - 1:15 PM Java EE SDK & Web Services Interoperability Technology booth duty (pod #966) Martin Grebac
1:00 PM - 3:00 PM Java EE SDK & Web Services Interoperability Technology booth duty (pod #966) Bhakti Mehta
2:45 AM - 4:45 PM Java EE SDK & Web Services Interoperability Technology booth duty (pod #966) Fabian Ritzmann
Wednesday, 05/09/2007
3:50 PM - 5:20 PM LAB-3350
Make Java Technology and .NET 3.0 Interoperability Work With WSIT
Martin Grebac; Sreejith A K
4:10 PM - 5:10 PM TS-4865
Takes two to Tango: Java Web Services and .NET Interoperability
Arun Gupta; Harold Carr
7:55 PM - 8:45 PM BOF-6412
Describing RESTful Applications: WADLing with Java
Marc Hadley
Thursday , 05/10/2007
11:15 AM - 1:15 PM Java EE SDK & Web Services Interoperability Technology booth duty (pod #966) Ashutosh Shahi, Shyam Rao
1:00 PM - 3:00 PM Java EE SDK & Web Services Interoperability Technology booth duty (pod #966) Sreejith A K
2:45 PM - 4:45 PM Java EE SDK & Web Services Interoperability Technology booth duty (pod #966) Sreejith A K; Arun Gupta
2:50 PM - 3:50 PM TS-4948
Unleashing the Power of JAX-WS RI: Spring, Stateful Web Services, SMTP, and More
Kohsuke Kawaguchi; Jitendra Kotamraju
5:30 PM - 6:30 PM TS-8840
Services Interoperability with Java Technology and .NET: Technologies and Tools for Web 2.0
Marina Fisher; Gerald Beuchelt
7:55 PM - 8:45 PM BOF-4108
Interoperable Web Services Security between Java Technology and .NET 3.0 with WSIT: Ease of Developement and Performance
Jiandong Guo; Ashutosh Shahi; Shyam Rao
Friday , 05/11/2007
10:50 AM - 11:50 AM TS-8029
Bridging the Gap: Using Java Technology and .NET Together in Harmony
Ted Neward
1:30 PM - 2:30 PM TS-4865
Takes two to Tango: Java Web Services and .NET Interoperability
Arun Gupta; Harold Carr

 

Thursday Feb 22, 2007

WS-Policy in WSIT milestone 3

With WSIT milestone 3, we are now shipping a complete WS-Policy implementation. WSIT provides an open-source and fully compliant implementation of WS-Policy 1.2 and WS-PolicyAttachment 1.2. We have lately been able to solely focus on fixing bugs and polishing the code and documentation and we currently have only very few open bugs . This seems like a good time to examine how WSIT supports WS-Policy more closely. And if you are wondering now what WS-Policy is in the first place, take a look at Marek Potociar's blog .

WSIT is an extension of JAX-WS and part of the GlassFish community. JAX-WS supports quite a number of approaches to develop and configure a web service. You can start with plain Java code and use annotations. If you need maximum flexibility, you would implement the Provider interface. If you have a WSDL document, you may want to start by having JAX-WS generate a service endpoint interface. There may be some deployment descriptors that allow you to configure your web service, see e.g. JSR 109. And on the client, you can use WebServiceFeatures.

Generally, the WS-Policy support in WSIT distinguishes between whether you develop your service starting from Java or WSDL. If you provide a WSDL document with your service, WSIT uses it and the contained policies to configure the system. The WSDL document is published almost unaltered. I am saying almost because this WSDL may contain policy assertions that are considered private. You can e.g. specify the password of a certificate store with a policy assertion. This and similar elements are automatically removed from the WSDL document before it is published.

When a service is developed from Java without any WSDL, WSIT relies on a separate configuration file. The file format is almost valid WSDL 1.1 and the actual configuration settings are contained as policies. That makes it very easy when JAX-WS generates a WSDL document for the service to attach the given policies to the generated WSDL document. As is the case when you develop your service from WSDL, private policy assertions are removed before the final WSDL is published.

Web service clients retrieve the WSDL of the service that they want to talk to. If that WSDL document contains policies, the client configures itself automatically to comply with the requirements of the service. Note that a client usually retrieves the service WSDL at run-time, i.e. the client configures itself at run-time as well. That makes it very easy to e.g. tighten the configuration of a web service in production without having to change or redeploy any client. (There is one exception to that rule, namely if you are using WS-AtomicTransaction, but then you have to adapt your code to deal with transactions anyway.)

The WSIT client can additionally read a separate configuration file. That configuration file serves two purposes. It allows to configure client-only settings, e.g. the certificate store of the client. And in case the service WSDL does not have any policies or the service has no retrievable WSDL at all, the service policies can be added to the client configuration instead. The client configuration file has the same format as the service configuration file, i.e. it is almost valid WSDL 1.1.

Technorati:

Tuesday Feb 06, 2007

How to configure logging in GlassFish for the WS-Policy implementation in WSIT II

How to configure logging in GlassFish for the WS-Policy implementation in WSIT by editing domain.xml.[Read More]
About

ritzmann

Search

Categories
Archives
« April 2014
MonTueWedThuFriSatSun
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today