|
|
||
Doug Kohlert's BlogJune 2005 ArchivesJAX-WS 2.0 Generates up to 85% less code than JAX-RPC 1.1Posted by kohlert on June 28, 2005 at 04:07 PM | Permalink | Comments (0)To highlight the savings in generated code with JAX-WS 2.0 compared to JAX-RPC 1.1, I ran the WS-I Sample application WSDL files through JAX-RPC's wscompile and JAX-WS's wsimport. The results are very good. JAX-RPC 1.1 generated 128 files that were 365KB in size. JAX-WS 2.0 generated only 61 files for a total size of 83KB. That is a 52% reduction in the number of files generated and a 77% reduction in the size of the generated files. You can download the early access 2 of JAX-WS 2.0 here. You can read the online documentation here. JAXB 2.0 and JAX-RPC 2.0 forum renamed to JAXB 2.0 and JAX-WS 2.0Posted by kohlert on June 23, 2005 at 10:14 AM | Permalink | Comments (0)The JAXB 2.0 and JAX-RPC 2.0 java.net forum has been renamed to JAXB 2.0 and JAX-WS 2.0 to be consistent with the rename of JAX-RPC 2.0 to JAX-WS 2.0. To read about the JAX-RPC 2.0 rename to JAX-WS 2.0 read my blog entry here. The JAXB and JAX-WS developement teams had worked very hard to release early access 2 of these technologies yesterday. Please download JAXB 2.0 EA2 and JAX-WS 2.0 EA2 and tell us what you think using the JAXB 2.0 and JAX-WS 2.0 forum. JAX-WS 2.0 Public Review has startedPosted by kohlert on June 22, 2005 at 04:42 PM | Permalink | Comments (0)The JAX-WS 2.0 Public Review version of the specifcation has been posted to the JCP and is open for review until 18 July 2005. Please download it and let us know what you think. You can send an email to: jsr224-spec-comments@sun.com, or post a message to the JAXB 2.0 and JAX-RPC 2.0 forum on java.net. JAX-WS 2.0 Early Access 2 is now availablePosted by kohlert on June 22, 2005 at 04:27 PM | Permalink | Comments (0)JAX-WS 2.0 Early Access 2 is now available. This version of JAX-WS provides support for SOAP 1.2, MTOM and Swaref. This is also the first implementation of a dynamic runtime that does not rely on non portable artifacts. We have removed the wsdeploy tool since we no longer generated non portable artifacts. We have redefined the RI's deployment descriptor used on stand alone servlet containers (not a J2EE). With this deployment descriptor, a developer can create their own deployable WAR file that can be run on any JAX-WS enabled servlet container. The EA2 can be downloaded here. | ||
|
|