How do I best organize my classes and/or jars so that all clients of EJBs are serviced?

How do I best organize my classes and/or jars so that all clients of EJBs are serviced?

Clients of EJBs that run under the Inprise Application Server environment are as follows: JSPs Servlets other EJBs EJB Container: The following information assumes a single container. Out-of-process container: The container's classpath is automatically configured with the EJB Jars hosted by that container. It thus has all the "client" classes it needs to reference other EJBs in that container. In-process container: The automatic configuration does not occur here.The EJB Jars hosted by the container must be placed on the server's classpath. Once this is done the container has all the "client" classes it needs to reference other EJBs in that container. Non-EJB clients: JSPs and Servlets are run in the server's VM; therefore, you need to make sure that the client classes/jars are organized well for that VM. There are "obvious" cheap/easy/standard places to put classes and jar files--such as the server's classes directory. Our recommendation for the "real world" is to define your own place to put client classes/jars and then configure the server's classpath (in ./properties/server/server name/java.options) to reference these. You can then maintain/share/backup/see these client classes/jars. Note: You can also easily re-configure the container's repository location and thus in a similar manner configure the above in-process container scenario.

Article originally contributed by Borland Developer Support

Tags: Files EJB Container Deployment CORBA AppServer JAR Server Application Inprise Classes