Skip navigation

Thomas Diesler's Blog

3 posts
I am happy to anounce that jbossws-1.0.1.GA is released. It is a drop in replacement for jbossws-1.0.0.GA in JBossAS-4.0.4.GA and also works in standalone Tomcat. This allows you to develop standard portable J2EE-1.4 web service endpoints in Tomcat that can be deployed to JBoss whenever full app server support is required.

 

 

 

 

http://labs.jboss.com/portal/jbossws/user-guide/en/html/installation.html

 

 

What's new
  • [JBWS-852] Integration with Microcontainer
  • [JBWS-865] Support security annotations for EJB3 endpoints
  • [JBWS-871] Arrays with JSR181 endpoints
  • [JBWS-923] Complete MTOM for rpc/literal
  • [JBWS-776] WSDLToJava Support wildcards
  • Bug fixes
For details see the change log.

 

 

Enjoy
-thomas
I am happy to announce that the web service team has released JBossWS-1.0.0 ready to be used in the upcomming JBoss-4.0.4 release.

 

 

 

 

JBossWS currently supports these standard J2EE-1.4 features:
  • RPC style endpoints
  • Document style endpoints (wrapped and bare)
  • SOAP header values bound/unbound to endpoint parameters
  • J2EE endpoint development model for EJB and Java
  • J2EE client development model
  • Dynamic Invocation Interface (DII)
  • JAXRPC client/server side handlers
  • Holders for INOUT/OUT parameters
JBossWS also supports:
  • Message style endpoints
  • Attachments Profile Version 1.0
  • Dynamic client/server side handler injection
  • Web Service Metadata (JSR-181)
  • EJB3 Stateless Session endpoints
  • WS-Security for XML Encryption/Signature of the SOAP message
  • WS-Addressing and JSR-261
  • WS-Transaction
  • WS-Eventing
  • WS-Policy
  • MTOM/XOP
There is still some integration work to be done with respect to WS-Transaction and WS-Policy. (clarified on 05-May-2006)

 

 

 

 

Support for the WS-Coordination, WS-AtomicTransaction and WS-BusinessActivity specifications will be provided by technology recently acquired from Arjuna Technologies Ltd. This technology will be present within the JBoss Transactions 4.2.1 release. Further information can be obtained from the JBoss Transactions Project. Both integration tasks are scheduled for jbossws-1.0.2.

 

 

The JBossWS-1.0.0 final release passes our internal testsuite, the testsuite for the jboss-4.0.x web service stack and the >2200 web service tests that come with Sun's Compatibility Test Suite (CTS). It comes with its own tool set (wstools) that generates portable J2EE-1.4 web service artifacts both from WSDL and from Java.

 

 

 

 

Please checkout the JBossWS project page, especially our extensive user guide. Most chapters in the user guide are backed up by standalone samples that are available from the JBossWS download page.

 

 

Over the next couple of months you will see us moving forward towards a J2EE-5.0 compliant implemenatation. This includes JAX-WS, JAXB, SOAP-1.3, etc.
If you can, come to JBoss World in Vegas and meet the team. I'll be happy to tell you more and receive your feed back.

 

 

----------------
Thomas Diesler
Web Service Lead
JBoss Inc.

The JBossWS project has released an early access version of its JAXRPC stack. After JBoss J2EE-1.4 certification in Jun/2004 we have decided to develop our own SOAP stack that is independent of the Apache Axis project, fits better in the overall JBoss architecture and is geared towards the specific J2EE needs for web services.

In J2EE-5.0, web services will have support for JAXRPC-2.0, JAXB-2.0, SOAP-1.2, BasicProfile-1.1, etc. For a full list see the JBossWS Wiki.

JBossWS currently support these standard J2EE-1.4 features:

  • RPC style endpoints
  • Document style endpoints (wrapped and unwrapped)
  • SOAP header values bound/unbound to endpoint parameters
  • J2EE endpoint deployment model for EJB and Java
  • J2EE client deployment model
  • Dynamic Invocation Interface (DII)
  • JAXRPC client/server side handlers
  • Holders for INOUT/OUT parameters


In its early access, JBossWS also supports:

  • Message style endpoints
  • Attachments Profile Version 1.0
  • Dynamic client/server side handler injection
  • XML Encryption on the SOAP message
  • XML Signature on the SOAP message
  • Standard Web Service Metadata as annotations (JSR-181)


Security is of high importance in mission crital web service applications. JBossWS adds support for this in its early access.

The last bullet point may also deserve special attention. Prior to JSR-181 annotations, you would develop a service endpoint interface (SEI), its associated implementation and the plethora of required XML descriptors.

With JBossWS you simply code: 

   /** Test the JSR-181 annotation: javax.jws.WebService
    */
   @WebService(
      name = "EndpointInterface", 
      targetNamespace = "http://www.openuri.org/2004/04/HelloWorld", 
      serviceName = "TestService")
   @PortComponent(contextRoot="/jsr181", urlPattern="/*")
   @Stateless
   public class EJB3Bean01 
   {
      @WebMethod
      public String echo(String input)
      {
         return input;
     }
  }


End of story. JBossWS deployes a web service endpoint that is targeted to this EJB3 stateless session bean and generates the associated abstract contract (WSDL) dynamically. JSR-181 annotated endpoints work for EJB-2.1, EJB-3.0, Pojo endpoints.

Here you find instructions on howto get started with JBossWS.

By the end of Q3/2005 we hope to deliver JBossWS-1.0 final release that passes our internal testsuite for the JBoss-4.0 stack and the >2200 web service tests that come with Sun's Compatibility Test Suite (CTS).

On the JBossWS Roadmap we have partly accomplished or scheduled support for:



That's all from me, enjoy the summer.

----------------
Thomas Diesler
Web Service Lead
JBoss Inc.