This chapter describes basic Axis use within JOnAS. It assumes that you do not require any explanation about Axis-specific tasks (for example, Axis deployment with WSDD). Before deployment in Axis, you must verify that the deploy.wsdd file matches the site machine configuration (the jndiURL parameter in particular):
<parameter name="jndiURL" value="rmi://localhost:1099"/> |
This chapter describes two ways to make an EJB (stateless Session Bean (SB)) available as a Web Service with JOnAS:
Axis runs in a unique Webapp, the SB is packaged in a separate EJB-JAR (or even EAR). The intent of this approach is to make EJBs from different packages that are already deployed accessible as Web Services via a single Axis Webapp deployment. The drawback is that Web Services are centralized in one Webapp only and the only way to distinguish between them for access is by the <service-name>, not by the <context-root>/<service-name>. In addition, the EJB-JAR files that contain the Web Services must be included in the Webapp.
The accessed EJB(s) are packaged with the Axis Webapp in an EAR archive. With this approach, the EJB-JAR files do not have to be included in the Webapp WEB-INF/lib directory; different Applications that contain Web Services can be hosted, providing the capability of distinguishing between Web Services of different applications.