Tom Ziemer wrote:
a) If you send p to the server, your persistence layer will save it for
you and update the id-field, yet this is not visible in the object on
the client, this will force you to have an API like
public Parent saveParent(Parent p);
or
public Long saveParent(Parent
Hi,
actually its the problem of the proper architectural design. If you
assume that your client works with objects internally used in the
business layer like in your parent-child example, you are screwed
regardless of hidden updates.
(Btw with CORBA your use-case won't happen, if you design Pare
Hi everybody,
This is rather off topic (and a repost from a different list), but this
is bugging me and I am sure, lots of you have faces a similar problem.
Basically it boils down to remoting via web services, RMI, Corba, etc.
and passing objects by value instead of by reference.
Please consider
3 matches
Mail list logo
