JSR-109 facilitates the building of interoperable Web services in the Java 2 Platform, Enterprise Edition (J2EE) environment. It standardizes the deployment of Web services in a J2EE container.

Prior to JSR-109, the procedure for deploying a Web service was highly coupled to the destination runtime. Deploying a Web service to Apache Axis is quite different from deploying to Apache SOAP. The motivation for JSR-109 is to promote the building of interoperable and portable Web services in the J2EE environment. JSR-109 leverages existing J2EE technology and provides industrial standards for Web services deployment. It clearly defines requirements that a Web service for J2EE product provider must support. It allows a J2EE Web service to be configurable via XML-based deployment descriptors and hides the complexity of the system from Web service developers, assemblers and deployers. Knowing how JSR-109 works allows you to configure a J2EE Web service without having to explore and learn the implementation details of the underlying system. Finally, as JSR-109 is adopted by Web server providers, the process of migration and deployment should become a routine procedure.

In general, a developer is responsible for providing the following:

In sum, JSR-109 provides a universal and simple way to enable stateless EJB and SERVLET to Web Service. UDTT component complies with JSR-109 standard and can be easily wrapped upon your request.

In Application Developer or WebSphere Integration Developer, the IDE generates the Web Service based on EJB or Servlet, and provides the invoke proxy in a strong-type manner.

If you want to invoke JSR109 style Web Service inside UDTT invoker, do the following: