Miles to go …

Other than performance improvements and minor bugfixes, the biggest change in WS-Addressing from WSIT M1 to M2 is enabling interoperability with a publicly available release of .NET 3.0 runtime (a.k.a. WCF or Indigo). The problem was identified few weeks ago and fixed right away but this is the first milestone build to incorporate the fix.

As mentioned earlier, WS-Addressing functionality is getting subsumed in JAX-WS 2.1. If everything goes well, a subsequent release of WSIT will use WS-Addressing functionality from JAX-WS 2.1 instead of JAX-WSA. As a developer, this change will not be visible to you except that it will be a faster and better performing implementation. Read Vivek‘s blog for more details on JAX-WS 2.1 roadmap. I’ll provide more details on WS-Addressing implementation in a later entry.

Other than that, there is not much activity on JAX-WSA. Hope you are enjoying WSITing.

Technorati: WSIT Web Services Web-services WSAddressing JAX-WSA WCF

Bleeding edge WSIT nightly builds are now available at your service.

Starting today, WSIT nightly builds will be posted here. A fresh copy of the workspace is checked out at 2:30am PT, built, installation bundles created and uploaded right after. All the latest and greatest bug fixes can be obtained using this nightly build. These builds will be overridden every day.

You can follow these instructions (Step 1) to install WSIT on your choice of Web container. If you like to develop, deploy and invoke a JAX-WS Web service that does not use any WSIT-specific technologies, then follow these instructions (Step 2). If you like to do the same and enable WSIT-specific functionalities then follow these instructions (Step 3). If you would rather NetBeans develop JAX-WS Web services using WSIT features then use these instructions (Step 4). And you can always try the full WSIT tutorial here.

More stable releases can be downloaded from here.

We would like to hear your feedback at . 

Technorati: WSIT Web Services Web-services GlassFish

Microsoft is hosting a Windows Communication Foundation (a.k.a. Indigo) interop plug-fest in Seattle from Sep 26-28. Sun Microsystems will participate in this plug-fest as we did during the previous two (Mar 2006, Nov 2005). We will be taking WSIT and GlassFish for all the interop testing.

I’ll post another blog entry, with our interop report, after the plug-fest.

Technorati: Web Services Interoperability WSIT Tango WCF Indigo GlassFish

As mentioned in The Aquarium few weeks ago, Fast Infoset support is now available in wsmonitor. Thanks to Joe Wang for all the work.

Given below is the CVS diff of JAX-WS fromjava sample that shows how to run the sample using wsmonitor and also how Fast Infoset support can be enabled.

cvs server: Diffing .
Index: build.xml
===================================================================
RCS file: /cvs/jax-ws-sources/jaxws-ri/samples/annotations/build.xml,v
retrieving revision 1.5.2.2.2.1
diff -r1.5.2.2.2.1 build.xml
125a126,127
> <sysproperty key="wsmonitor" value="${wsmonitor}"/>
> <sysproperty key="com.sun.xml.ws.client.ContentNegotiation" value="${fi}"/>
cvs server: Diffing etc
Index: etc/build.properties
===================================================================
RCS file: /cvs/jax-ws-sources/jaxws-ri/samples/annotations/etc/build.properties,v
retrieving revision 1.5
diff -r1.5 build.properties
9a10,11
> wsmonitor=false
> fi=none
cvs server: Diffing src
cvs server: Diffing src/annotations
cvs server: Diffing src/annotations/client
Index: src/annotations/client/AddNumbersClient.java
===================================================================
RCS file: /cvs/jax-ws-sources/jaxws-ri/samples/annotations/src/annotations/client/AddNumbersClient.java,v
retrieving revision 1.5.12.1
diff -r1.5.12.1 AddNumbersClient.java
23a24,25
> import javax.xml.ws.BindingProvider;
>
27a30
> log(port);
42a46,53
> }
> }
>
> private static final void log(AddNumbers port) {
> if (Boolean.getBoolean("wsmonitor")) {
> String address = (String)((BindingProvider)port).getRequestContext().get(BindingProvider.ENDPOINT_ADDRESS_PROPERTY);
> address = address.replaceFirst("8080", "4040");
> ((BindingProvider)port).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, address);
cvs server: Diffing src/annotations/server

This sample is available in JAX-WS 2.0.1 binary or can be checked out along with the JAX-WS sources project.

After making the above mentioned changes in the files, download, install and run wsmonitor v1.1. Re-build the sample client (ant client) and run it with the following additional properties: 

ant run -Dwsmonitor=true

This command will run the client and wsmonitor console will show the HTTP headers and SOAP request and response messages.

ant run -Dfi=[optimistic | pessimistic | none ]

This command will run the client based upon the Fast Infoset content negotiation defined by the property values. The wsmonitor console will show the HTTP headers and SOAP request and response messages. Fast Infoset messages are identified by the request and response encoding shown in the table at the top and also by the application/fastinfoset value of Accept-Type HTTP header for the request message and Content-Type HTTP header for the response message. The SOAP message, in this case, is displayed as a binary dump using hexadecimal representation.

The various console dumps showing HTTP headers and request/response messages using SOAP and Fast Infoset is available here.

Technorati: Web Services Web-services JAX-WS SOAP HTTP Fast Infoset