 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | | Pattern Composite Entity is still good for EJB 2.0 | Pattern Composite Entity is still good for EJB 2.0 2003-08-28 - By Le Quang Tu
Back
Hi all,
In "The Core J2EE pattern" book, the Composite Entity Pattern is recommended
for the Coarse-Grained Entity bean. But in another book - "the EJB Pattern"
which is available in theserverside.com, the author recommends that "Don't Use
the Composite Entity Bean Pattern", because it is built for the 1.x
specification. The problem with dependent objects is that they are impossible
to create, using your application server's CMP engine and extremely difficult
to implement using BMP. Managing the life cycle of a set of dependent objects
in BMP is equivalent to writing your own persistence engine.
EJB 2.0 can support the CMP EJB relationship among entity beans. With this
enhancement, including Local interface, entity bean can now be used to domain
objects in your design model as finely as you like.
So is Composite Entity Pattern still good for EJB 2.0 now?
Le Quang Tu
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859 (See http://iso-8859.ora-code.com)-1">
<META content="MSHTML 6.00.2800.1170" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Hi all, </FONT></DIV>
<DIV><FONT face=Arial size=2>In "The Core J2EE pattern" book, the
Composite Entity Pattern is recommended for the Coarse-Grained Entity
bean. But in another book - "the EJB Pattern" which is available
in theserverside.com, the author recommends that "Don't Use the
Composite Entity Bean Pattern", because it is built for the
1.x specification. The problem with dependent objects is that they
are
impossible to create, using your application server's CMP engine and
extremely difficult to implement using BMP. Managing the life cycle of a set of
dependent objects in BMP is equivalent to writing your own
persistence
engine. </FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>EJB 2.0 can support the CMP EJB relationship
among entity beans. With this enhancement, including Local interface, entity
bean can now be used to domain objects in your design model as finely as
you like.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>So is Composite Entity Pattern still good for EJB
2.0 now?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Le Quang Tu<BR></FONT></DIV></BODY></HTML>
====================================================================
Companion Site: http://www.corej2eepatterns.com
J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns
List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
|
