The deployment descriptor tells the EJB container what middleware services
the EJB will need. They are XML documents, and are often generated.
Here's a sample Orion deployment descriptor for an EJB I use at my full
time job. How might we modify this for our bean? (Note, this
snippet has been significantly modified to protect the security and intellectual
property of my employer.)
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<display-name>Sample App Beans</display-name>
<enterprise-beans>
<session>
<display-name>SampleSession</display-name>
<ejb-name>SampleSession</ejb-name>
<home>com.edlending.beans.SampleSessionHome</home>
<remote>com.edlending.beans.SampleSession</remote>
<ejb-class>com.edlending.beans.SampleSessionBean</ejb-class>
<session-type>Stateful</session-type>
<transaction-type>Container</transaction-type>
<env-entry>
<env-entry-name>LogFile</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>[detag:log
path]</env-entry-value>
</env-entry>
<env-entry>
<env-entry-name>LogLevel</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>[detag:log
level]</env-entry-value>
</env-entry>
<ejb-ref>
<ejb-ref-name>Site</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.edlending.beans.SiteHome</home>
<remote>com.edlending.beans.Site</remote>
<ejb-link>SampleBeans.jar#Site</ejb-link>
</ejb-ref>
<ejb-ref>
<ejb-ref-name>SiteProduct</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.edlending.beans.SampleProductHome</home>
<remote>com.edlending.beans.SampleProduct</remote>
<ejb-link>SampleBeans.jar#SampleProduct</ejb-link>
</ejb-ref>
[...]
(insert deployment descriptor for HelloWhirled)