Pattern Composite Entity is still good for EJB 2.0 2003-08-28 - By Sean Brydon
Back Hi, Yes it is valid, especially for EJB2.0 and higher. Local EJBs make this a valuable design. This pattern is discussed and updated in the second edition of the patterns book, now available. An example of this strategy is at http://java.sun.com/blueprints/patterns/CompositeEntity.html and this is done in the petstore application.
hope that helps, Sean Le Quang Tu wrote:
> 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)
==================================================================== 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)
|
|