Hello Vincent... --On Wednesday, May 02, 2001 12:15 PM +0200 Vincent Harcq <[EMAIL PROTECTED]> wrote: > Hi, > I have made added some feature to the way "dependant value objects" are > mapped to table fields. > This is for example when I have a UserBean cmp entity bean that have a > cmp-field address of non primitive type Address, and I want to store each > fields of Address into the database using a specific Jaws feature. > IMHO, with dependant objects being dropped of EJB 2.0, I think this > feature is important because the standard way to that with ejb 2.0 would > be to define a cmp bean for my value object which is really going too far. This is a great feature, but the removal of dependents from the EJB 2.0 spec probably has not too much bearing on it. This, as were dependents, are essentially an implementation issue used to reduce complexity and improve performance by avoiding a remote interface call. In EJB 2.0 PFD2, we now have a "local interface" which does not use RMI as the remote interface does. This should provide the same reduction in complexite and overhead dependents would have, but does not introduce into the spec a non-design feature that may be confuseing. With EJB 2.0 PFD2, you can concentrate on the design of your system from an object modeling standpoint without thought of performance due to coupeling. Once you have that, you can decide what are local vs remote interfaces. So you have added a great feature, but I don't agree it is an improvement because of the removal of dependents from 2.0. Using the 2.0 local interface between EBs is a portable solution that should not have performance issues. Jim ******************************************** I shall be telling this with a sigh Somewhere ages and ages hence: Two roads diverged in a wood, and I - I took the one less traveled by, And that has made all the difference. - Robert Frost, 1916 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
