Completing the EJB implementation for JAX-RPC applications
After you have developed the Java™ artifacts necessary to develop a Java API for XML-based RPC (JAX-RPC) web service, you must complete the Enterprise JavaBeans (EJB) implementation to assemble a Java archive (JAR) file or a web application archive (WAR) file based on your programming model. The resulting JAR file or WAR file contains the Enterprise JavaBeans (EJB) implementation and the supported classes created from the tooling.
Before you begin
Develop EJB implementation templates and bindings from a WSDL file for JAX-RPC web services using the wsdl2java command-line tool. The deployment descriptor templates that are generated from a Web Services Description Language (WSDL) file are required to complete the EJB implementation in the web services development process.
About this task
For JAX-RPC applications, complete the enterprise beans implementation by writing your business application.
Procedure
- Inspect the EJB remote interface template, portType_RI.java. If necessary, modify the template. The value portType is the name of the <wsdl:portType> element in the WSDL file.
- Edit the bindingImpl.java EJB implementation template. Where binding is the name of the <wsdl:binding> element in the WSDL file.
- Complete the implementation of the methods in the template.
- (Optional) Make changes if necessary.
- (Optional) Change the class name if the binding name is not acceptable.
- Compile all the Java classes.
- Assemble an EJB Java archive (JAR) file. Assemble all the Java classes into an enterprise bean JAR file using assembly tools. Include all of the classes generated from running the WSDL2Java command tool when developing implementation templates and bindings from a WSDL file.
Results
What to do next
Now that you have gathered the required artifacts for developing a JAX-RPC web service with an enterprise bean, you need to, configure the webservices.xml deployment descriptor.