Just use your dependent class object to wrap the actual value object and you do
not need to do any manual copying. In my architecture, all ejbs reside in
their own directory, so I could use a mycompany.ejb.Address to wrap a
mycompany.bo.Address.
mycompany.ejb.Address -> a dependent class object with only one field.
mycompany.bo.Address -> actual business object.
An extra layer to isolate business level solutions to hedge against the
day EJB may become passe or the day your application needs to run in a
non-ejb environment.
Anh
On Thu, 15 Jun 2000, Jason Sando wrote:
> Looking at page 123 of the ejb 2.0 public draft (May 31 2000), it shows them
> manually copying the attributes over. First, what a waste of my personal
> time to do such coding. Second, what a waste of memory: creating all these
> objects just to serialize them.
>
> I'm wondering why, if the spec is defining the o/r mapping, why is it not
> specifying the dependent objects <-> client view of dependent objects
> mapping? Is that coming?
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
