New Web Services Features in Netbean 6.5
Netbeans 6.5 is recently released. Along with tons of new features, it has some enhancements for Web Services development.
The foremost is that with Netbeans 6.5, you can easily develop Web Services applications and deploy on to Glassfish V3. There are are other features like configuring WS-Addressing, and exposing a SOAP based Web service as REST service through GUI caught my attention.
Coming to configuring WS-Addressing, You can easily configure by editing the Web Service attributes and checking the box for Addressing as shown in the following picture.
Previously, it was enabled if it required by other option like Reliable Message Delivery. This feature lets you configure your Web Service to use WS-Addressing without other technologies.
Doing this automatically generates WSIT configuration file with the right policies to enable WS-Addressing as shown below.
<wsp:Policy wsu:Id="NewWebServicePortBindingPolicy">
<wsp:ExactlyOne>
<wsp:All>
<wsaw:UsingAddressing xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" wsp:Optional="true"/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
Its currently generating <wsaw:UsingAddressing> assertion, in future this would generate <wsam:Addressing> when Metro supports WS-Addressing 1.0 Metadata specification.
Of course, you can still configure in other ways by using the annotation @javax.xml.ws.Addressing on the endpoint implementation or programmatic configuration using AddressingFeature()
Among other things in Netbeans 6.5, you can expose a SOAP based Web Service as a Restful Service.
Right click on the Web Service, select Generate SOAP-over-HTTP wrapper option. It generates a Rest resource.
Wow,thats easy!!!.
Download Netbeans 6.5 and give it a try.
- Login or register to post comments
- Printer-friendly version
- ramapulavarthi's blog
- 2432 reads









Comments
by ashishgodani - 2009-01-29 00:40
There is this really strange issue i am struggling with using JCAPS 6.0 with Netbeans 6.1: http://www.netbeans.org/issues/show_bug.cgi?id=157587 Issue: Content type for any webservice invocation is sent as "multipart/related" by bpel engine..