Version 1.0

Version 1.1

Version: 1.0

Version: 1.1

Section 3.10, item 1, replace:

The service provider implements the Web service business logic by implementing a stateless session EJB. The EJB�s remote interface method signatures must match the method signatures of the Service Endpoint Interface and must include all methods of the Service Endpoint Interface.

With:

The service provider implements the Web service business logic by creating a stateless session Bean that implements the methods of the Service Endpoint Interface as described in the Enterprise JavaBeans 2.1 specification.

Section 8.1 paragraph 6, replace:

In general, the deployment tool generates a servlet to handle parsing the incoming SOAP request, create a remote stateless session EJBObject and dispatch the request to the stateless session EJB. The methods of the SEI are described by the remote interface, the deployment tool can generate a servlet that dispatches to the remote interface of the EJB.

With:

In general, the deployment tool generates a servlet to handle parsing the incoming SOAP request, the servlet obtains a reference to an instance of an appropriate EJBObject and dispatches the request to the stateless session EJB.

Section 3.10 item 1, remove:

The EJB�s remote interface method signatures must match the method signatures of the Service Endpoint Interface and must include all methods of the Service Endpoint Interface.

Section 5.3.2.1.3, remove entire section:

5.3.2.1.3 Exposing an existing EJB
An existing Enterprise JavaBean may be used as a Service Implementation Bean if it meets the following requirements:
� The business methods of the EJB bean class that are exposed on the SEI must meet the Service Implementation Bean requirements defined in section 5.3.1.
� The Service Endpoint Interface methods must be a subset of the remote interface methods of the EJB and the SEI must meet the requirements described in the JAX-RPC specification for Java->WSDL mapping.
� The transaction attributes of the SEI methods must not include Mandatory.
The developer must package the Web service as described in section 5.4 and must specify an ejb-link from the port in the Web services deployment descriptor to the existing EJB.

Section 8.1, 3rd bullet, remove:

If the Service Implementation Bean is an EJB, the SEI methods are fully contained by the remote interface.

If the Service Implementation Bean is an EJB, the SEI methods are not fully contained by the remote interface.

Optional support for J2EE 1.3 platforms

Web Services for J2EE Version 1.1 does not require support for applications built according to the Web Services for J2EE Version 1.0 specification. A vendor may optionally support Web Services for J2EE 1.0 by implementing that version of the specification. See the Web Services Version 1.0 Change Log for more details on the differences between the two specifications.

Section 7.1.5, replace DTD with XML Schema

Section 7.2.2, 4th bullet, remove:

Scope. If the service reference is being defined within an EJB-JAR, the service-ref elements must be defined within a component-scoped-refs element so that the service-ref can be associated with a particular EJB. The association with the EJB is defined by the component-name element.

Section 7.2.2?, add note regarding service-endpoint declaration in EJB 2.1 deployment descriptor.

Section 7.2.5, replace DTD with XML Schema.

Section 7.3.5, replace DTD with XML Schema.

Section 5.3, first definition list item, move the following to the appendix:

Support for OUT and IN/OUT parameters is optional for the EJB container.

Section 5.3, second definition list item, move the following to the appendix:

Support for Holder parameters is optional for the EJB container.

Section 5.3.1, move the last paragraph to the appendix:

JAX-RPC defines Holders as non-serializable classes which cannot be implemented by the remote interface of an Enterprise JavaBean. Therefore, support for an SEI which uses Holders for parameters is not required for Port components deployed in the EJB container

Section 6.1, last paragraph, remove:

This specification makes Handler support in the EJB container optional due to the required EJB container changes that would be necessary to implement Handler support. It is expected that EJB Handler support will be made required in a future J2EE specification.

Section 6.2.4, last paragraph, remove:

A container provider is not required to support Handlers for Port component�s that run in the EJB container. It is expected this will be required when this specification is included in J2EE 1.4.

The relation of this specification to J2EE 1.4 is defined in Appendix A.

The Web service deployment is supported on top of existing J2EE 1.3 environments.

The Web service deployment is supported on J2EE 1.4 environments.

Appendix A, J2EE APIs, replace:

Enterprise JavaBeans 2.0 defines the programming model for implementing Web services which run in the EJB container.

Servlet 2.3 defines the packaging and container service model for implementing Web services which run in the servlet container.

J2EE 1.4, EJB 2.1, and Servlet 2.4 will include the Web services specification defined within this specification. An effort will be made to maintain compatibility and ease migration to J2EE 1.4, but there is no guarantee that compatibility will be ensured. A JSR 109 1.1 maintenance release will address XML Schema based deployment descriptors, the EJB 2.1 Web services view, as well as Holder and Handler class usage in the EJB container for use by J2EE 1.4

With:

Enterprise JavaBeans 2.1 defines the programming model for implementing Web services which run in the EJB container.

Servlet 2.4 defines the packaging and container service model for implementing Web services which run in the servlet container.

The port address attribute may be absent from the WSDL or may be a dummy value.

The port address location attribute may be absent from the WSDL or may be a dummy value.