Java Reference
In-Depth Information
bean-class interfaces and implementations. We also have a tag showing that
this bean is a session bean, and it implements the stateless session bean proto-
col from an
EJB
container.
<env-entry id="EnvEntry_5">
<env-entry-name>ejb10-properties/postHomeName
</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>com/bitterjava/bbs/ejb/Post
</env-entry-value>
</env-entry>
.
.
</enterprise-beans>
We then have environment entries for the bean, describing the parameter
names in detail and providing descriptive information that we'll need to man-
age the bean. We omit similar descriptions for other session facade session
beans, as well as our
discussion
and
post
entity beans.
<assembly-descriptor id="AssemblyDescriptor_ID">
<container-transaction id="MethodTransaction_1">
<method id="MethodElement_1">
<ejb-name>Board</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
.
.
</assembly-descriptor>
</ejb-jar>
The assembly descriptor describes security roles (we don't have any here). The
descriptor also includes transactional details. Since many different
EJB
s might
have the same transactional and security details, they are broken out into a
separate section so that they might be handled in a single pass.
8.2.7
Using the model
Conceptually, this model can be used in the place of our command model in
the triangle architecture specified in chapter 3. We'd use the controller to pro-
vide entry points for various actions required by our user interface. In a high-
performance environment, we'd typically deploy the
EJB
server on different
hardware from the web application server. Such a deployment would force us
to pay careful attention to the interface between the hardware containing our
JSP
and controller and the hardware containing our model. We'd have to
