Topic
  • 3 replies
  • Latest Post - ‏2011-05-16T17:56:00Z by barrettj
barrettj
barrettj
2 Posts

Pinned topic Feature Focus Week: JAX-WS and Web Services for Java EE Updates

‏2011-05-09T17:14:12Z |
IBM WebSphere Application Server has been updated based on the Web Services for Java EE (JSR 109) version 1.3 and Java API for XML-Based Web Services (JAX-WS) (JSR 224) version 2.2 specifications.

Some of the updates related to JAX-WS 2.2 include:
  • Client Service factory method support for web services features for MTOM, Respect Binding, and Addressing [1]
  • Not returning a response to the requester when a WSDL-less WebServiceProvider implementation returns null
  • Allowing a service to be packaged without the JAX-B wrapper bean classes
  • Only exposing public, non-static, and non-final methods in services with an implicit SEI, based on the WebMethod and/or WebService annotations
  • Supporting web service feature annotations for MTOM, RespectBinding, and Addressing on injected WebServiceRef port references [1]
  • Configuring WS-Addressing via WS-Policy assertions in WSDL

Some of the updates related to JSR 109 1.3 include:
  • Support for Singleton Session beans as JAX-WS endpoints
  • Support for declaration of web service features MTOM, Addressing, and RespectBinding for service-references and endpoints via the deployment descriptor [1]
  • Support for Web Beans as JAX-WS endpoints and JAX-WS application handlers
  • Web services support for java:global, app, and module naming contexts
  • Support for web services in EJBs within a WAR

Other updates include:
  • Support for a Custom Properties policy type and binding which can be used to set generic properties not supported in other policy types
  • Updates to JMS support based on SOAP Over JMS 1.0

We will discuss several of these item in more detail in subsequent posts during this Feature Focus Week.

References:
[1] - This was discussed in a previous forum post "Feature Focus Week: Java EE 6 Web Services Specification Updates" from September 13, 2010: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=346279&tstart=195

Jeff Barrett
WebSphere Web Services Development
Updated on 2011-05-16T17:56:00Z at 2011-05-16T17:56:00Z by barrettj
  • SystemAdmin
    SystemAdmin
    462 Posts

    Re: Feature Focus Week: JAX-WS and Web Services for Java EE Updates

    ‏2011-05-11T13:57:29Z  
    The IBM WebSphere Application Server V8 release supports a new Custom Properties policy for use in JAX-WS Web services. You can use the Custom Properties policy and binding to set some generic properties that are not supported in other policy types. The additional properties are set in the binding. The Custom Properties binding is only supported for service clients and is not allowed for service providers. The Custom Properties policy type provides an alternate way to set some binding properties that would otherwise have been set on the javax.xml.ws.BindingProvider object using the JAX-WS programming model.

    For example, you could configure the BindingProvider.ENDPOINT_ADDRESS_PROPERTY in a Custom Properties binding. By assigning a different binding with a different endpoint address to each service reference of a service client, you could target a request to a particular server based on the specified service reference.

    You can use the WebSphere administrative console or a wsadmin scripting command to set a property in a Custom Properties binding. The following example of the setBinding command demonstrates how you can use the Custom Properties binding to set a value for the BindingProvider.ENDPOINT_ADDRESS_PROPERTY in a general, cell-level binding:
    
    AdminTask.setBinding(
    '[-bindingLocation "" -bindingName generalCellWideBind1 -attachmentType client  -policyType CustomProperties -attributes "[[javax.xml.ws.service.endpoint.address addressURLValue]]"]')
    
  • kumar_varadan
    kumar_varadan
    1 Post

    Re: Feature Focus Week: JAX-WS and Web Services for Java EE Updates

    ‏2011-05-12T16:52:06Z  
    One of the updates related to JSR 109 1.3 that was mentioned in the initial post is
    Support for web services in EJBs within a WAR. Thoe following bullets gives more information on that feature along with the rules of packaging.

    • JAX-WS EJB-based WebServices can now be deployed in a war module as per the EJB 3.1 spec (JSR318 Section 20.5.2),
    • The EJB function that is supported for beans packaged inside EJB Java archive (JAR) modules is also supported for beans packaged inside WAR modules.
    • A bean that is packaged inside a WAR module can have the same behavior as a bean that is packaged inside an EJB JAR module.
    • All types of EJB 3.x beans are supported in WAR modules.

    The rules for packaging EJB content in a WAR module are different from the rules for packaging EJB content in a JAR module.

    • The bean class files must be placed in one of two locations within the WAR module:
    1. Loosely (One can place the individual *.class files instead of the jar itself) in the
    WEB-INF/classes directory structure
    2. Within a JAR file that is placed in the WEB-INF/lib directory
    For example, the bean class com.foo.MyBean loosely placed in the WAR module at this location: WEB-INF/classes/com/foo/MyBean.class.
    The bean class can also be placed in the myJar.jar file, which is then placed in WEB-INF/lib/myJar.jar.

    •A WAR module can have some bean code loosely placed in the WEB-INF/classes directory structure, and have other bean code inside
    JAR files in the WEB-INF/lib directory.

    • It is also valid for a WAR module to have all the bean code in the WEB-INF/classes directory structure and nothing in the
    WEB-INF/lib directory, or all the bean code in JAR files in the WEB-INF/lib directory and nothing in WEB-INF/classes.

    • It is valid to have multiple JAR files in the WEB-INF/lib directory, all of which might contain bean code.

    • The EJB deployment descriptor files must be placed in the WEB-INF directory. This directory contains the ejb-jar.xml deployment descriptor,
    and any ibm-ejb-jar-ext and ibm-ejb-jar-bnd XML or XMI bindings and extensions files.

    • A WAR module must be version 2.5 or higher to contain EJB content.

    • If a WAR module is version 2.5 or higher, the web metadata files containing bindings and extensions information must use the XML version of the files, not the XMI version.
  • barrettj
    barrettj
    2 Posts

    Re: Feature Focus Week: JAX-WS and Web Services for Java EE Updates

    ‏2011-05-16T17:56:00Z  
    To Learn More
    Join us for our Feature Focus Week Reflections teleconference scheduled for Thursday, May 19th, 2011. To receive invitations to our CEP sessions, simply email cepatusdotibmdotcom requesting to join. By return, you will receive a confirmation with a few questions about you and your interests. After that, you will start to receive regular invitations to the presentation.