Jim,
My comments below.

> > 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.

I agree...partially... with your comment, when I will write docs on that, I
have to be clear it is JBoss specific.
Partially because for a value object such as Quantity (a double and a
String) or Amount, ...  the EJB 2.0 entity bean relationship is not a
solution.  It is for Address, and these kind of objects.
With dependant object it would have been possible (even if I do not like the
idea) to have a Quantity d.o., make a client view of it and solve the OO
design.  Without I need to serialize my Quantity or decompose it in two
primitive type fields, both solutions being unacceptable for me (it is a
strong word, but cmp are very far from OO design for now)
These kinds of objects (we can them as java primitive types extensions in
the business object world) were the main reason for my change.

Thanks for opening the discussion.

>
> Jim
>
>

Vincent.


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to