The EJB 1.1 specification identifies the EJBs in the deployment descriptor, so it no longer needs the information in the Manifest. Additionally, EJB 1.1 deprecated serialized deployment descriptor components. An XML-based deployment descriptor also has replaced the mechanism of using serialized JavaBean components as deployment descriptors. Understanding the process The jetace tool is somewhat cryptic when compared to the features of VisualAge for Java, but I have found it quite useful for grasping an understanding of the relationships between the various Beans, the EJB container and the EJB server. With an understanding of the complete deployment cycle comes a better understanding of the power of the technology.
Students run the tool remotely from a single application server.
The jetace example in this article is based on this scenario and the assumption that the user is running jetace from the directory containing the jar files. Developers create a session EJB to perform the logic required and an entity EJB to access the data store. Along with each Bean and in accordance with the specification, developers must write home interface and a remote interface files. An entity EJB also requires a primary key file. To build the class files related to a particular EJB, invoke the Java compiler on each file.