Read this article if you would like to learn how to use SOAP, WSDL, and the Web services stack with J2EE. The second of three parts, this section focuses on EJBs and Axis. It is excerpted from chapter 7 of the book Building Web Services with Java: Making sense of XML, SOAP, WSDL, and UDDI, written by Steve Graham et al. (Sams; ISBN: 0672326418).
Usually you'd use a tool from the application server to do this and package the resulting EAR file. The EAR file now contains the following:
At this point we move away from pure interoperable J2EE and into the realm of a specific application server. The deployment tooling will augment skates.ear with server- specific files. For example, WebSphere Application Server will generate a number of additional classes and XML files that bind the EJBs we've written into the container. For the examples in this book, we used the latest available WebSphere Application Server—version 5.1, which is available for trial download on the Web (http://www-106.ibm.com/developerworks/websphere/ downloads/WASsupport.html).
WebSphere allows you to do this outside the runtime using the application assembly tool, and also from the administration console. Other application servers have appropriate methods (for example, BEA WebLogic server has an ejbdeploy tool).
Please come back next week for the conclusion of this article.
DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware.