Change Log: JSR-109 : Web Services for Java EE, Version 1.3

Description

Additional changes for JSR-109 1.3 MR

Maintenance Lead

Jitendra Kotamraju, Sun Microsystems, Inc.

Changes

  1. Port components packaged in a WAR file must use a JAX-RPC/JAX-WS Service Endpoint or a JAX-WS(not JAX-RPC) service using Stateless/Singleton session bean for the Service Implementation Bean.

  2. Adding @WebServiceRef(lookup) example

  3. Adding that @WebServiceRef(lookup) and @WebServiceRef(mappedName) can be overriden respectively using <service-ref>/<lookup-name> and <service-ref>/<mapped-name> deployment descriptor elements.

  4. In a product that also supports JSR-299, an implementation must support use of 299-style managed beans as JAX-WS web service classes in an application. JAX-WS annotations may be directly applied to these beans. JSR-299 specifies the requirements for these container-managed bean instances w.r.t instantiation, injection and other services. JSR-299 defines @Dependent pseudo-scope, web service classes must be in that scope. Additionally, a JAX-WS service using singleton EJB can also be in @ApplicationScoped scope. It is an error if the service class has a scope other than the required one.

  5. In a product that also supports Managed Beans, an implementation must support use of managed beans as JAX-WS web service classes in an application. JAX-WS annotations may be directly applied to managed beans. Managed Beans specification specifies the requirements for these container-managed bean instances w.r.t instantiation, injection and other services.

  6. In a product that also supports JSR-299, an implementation must support use of 299-style managed beans as JAX-WS handler classes in an application. JSR-299 specifies the requirements for these container-managed bean instances w.r.t instantiation, injection and other services. JSR-299 defines @Dependent pseudo-scope, handler classes must be in that scope. It is an error if the handler class has a scope other than the required one.

  7. In a product that also supports Managed Beans, an implementation must support use of managed beans as JAX-WS handler classes in an application. Managed Beans specification specifies the requirements for these container-managed bean instances w.r.t instantiation, injection and other services.

  8. JAX-RPC mapping schema is specified as a link(rather than inlining)

Accepted Changes

None

Deferred Changes

None