Eduardo Pelegri-Llopart's Blog

JWSDP 1.4 is out!

• FCS implementation of JAX-RPC 1.1 with substantial performance improvements and implementing WS-I BP 1.1 and WS-I's Attachment Profile 1.0.
• FCS implementation of JAXB with substantial performance improvements.
• FCS JAXP 1.2, with new renamed packages, and with XSLTC as default transformation engine.
• EA support for OASIS's WS Security.
• EA support of JSR 105, implementing XML Digital Signature.
• Tested with several containers: Sun's App Server 8.0 PE (this the same as the free J2EE 1.4 SDK), Sun's Web Server 6.1, and Tomcat 5.0

A longer list is at Sun's web site, but below are some comments on this one.

In Sun's parlance, FCS stands for "first customer shipment", and means the component is production ready. In the case of the JWSDP, the license for FCS components allows deployment, but they are not supported - the supported versions will show up when bundled in later releases of Sun's products. EA stands for "early access" and indicates the component is useful for development but there may still be changes in the component, including the API!, before it becomes FCS quality.

JWSDP 1.4 has a number of substantial performance improvements. On the JAXB front, the biggest improvements were on marshalling and unmarshalling: when measured using an internal microbenchmarks we saw about 2x improvement; much of this thanks to direct feedback from the weekly builds at the JAXB project at java.net. I don't have specifics handy on the JAX-RPC improvements but they are key contributors to the recently published results on a macrobenchmark analysis comparing J2EE and .NET on WS and XML. XSLTC is, of course, the XSLT compiler that started as Sun experimental work, was then donated to Apache and is now in full product-ready mode (it is bundled in Tiger!); we see between 2.5x to 11x improvements in performance when compared with Xalan classic- although this depends on whether you apply the stylesheet only once, or several times. The usual disclaimer applies: although the numbers we quote are our best understanding of the real situation, your performance may vary... (there are lies, dammed lies, and benchmarks :-)).

The WS-I's Attachment Profile 1.0 is the MIME-based spec from WS-I that describes how to send attachments in WS messages. Attachments are critical to practical applications of WS and I believe that JWSDP is the first FCS-quality implementation of this standard.

The other major change on JAXP, besides the change of the default transformer (Xalan classic is still there, just not the default), is that the packages got renamed. This is so that you don't have to do classpath magic (which too often leads you into trouble) if you want to use at the same time the new JAXP classes and some other version of Xerces or Xalan.

I could also talk more about the JDBC RowSet Implementations 1.0 JWSDP 1.4 Co-Bundle, which provides a set of tools, documentation, samples and tutorial for developers who want to use JDBC RowSets with Web Services, but I'll talk more about that in another blog.

Finally, I just noticed that Marc also posted a blog on the JWSDP; Marc is a key participant at WS-I, among many other things, so he is your man in that area of the JWSDP!

Comments

• More details on XSLTC performance
  Santiago gave me more details on the XSLTC performance. He says:

  Single-threaded latency is 2.5-3X on aggregate
  In multi-threaded tests people have seen up to 10X improvement,
  especially when compared to some older versions of Xalan.

  - santiago
  

  Posted by: pelegri on June 25, 2004 at 07:15 AM

• WS-I Sample Application...
  The JWSDP 1.4 also includes the WS-I Attachments Sample Application 1.0 EA, and Arun posted the instructions on how to configure it with WS-I testing tools at
  http://jwsdp.dev.java.net/wsinterop/wsi/testingtools.html.
  

  Posted by: pelegri on June 25, 2004 at 07:35 AM

• UDDI Registry Server is EA, not FCS..
  Somebody pointed out that the pages in the Web say that the UDDI Registry Server is FCS. That is incorrect, it is an EA component.

  - eduard/o

  Posted by: pelegri on June 25, 2004 at 09:54 AM

• XWS Security and Sample App in JWSDP 1.4
  The Early Access version of XML and Web Services Security technology included with JWSDP 1.4 is based on OASIS Web Services Security specification. This implementation has been tested for interoperability with other vendor's implementations via participation in OASIS virtual interop events. One can use this technology in conjuction with JAX-RPC for passing secure SOAP messages.

  Also included with JWSDP 1.4 is Early Access version of WS-I Sample Application with Attachments. Developers can use this to learn design and development of WS-I conformant web services using JAX-RPC technology.

  Posted by: jindala on June 25, 2004 at 11:10 AM

This work is licensed under a Creative Commons License.