Hi,
  But if we do NOT have a class's source code. Such
reference id instrution seems impossible.

Regards,
Rice


--- Mahler Thomas <[EMAIL PROTECTED]> wrote:
> Hi Rice,
> 
> this kind of intrusion would be avoidable.
> But at a tremendous cost of complexity.
> We decided to have this intrusion to OJB internals
> simple.
> I don't think it's a *real* problem. those extra
> attributes can be
> effectively hidden from application developers.
> 
> cheers,
> Thomas
> 
> 
> > -----Original Message-----
> > From: Rice Yeh [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, February 27, 2003 3:52 PM
> > To: [EMAIL PROTECTED]
> > Subject: Does reference id intrusion to the domain
> model necessary?
> > 
> > 
> > Hi,
> >   I just read discussion on tss website
> >
>
http://www.theserverside.com/home/thread.jsp?thread_id=18066&a
> > rticle_count=33#75045
> > I find that ojb has similar problem "reference id
> > intrusion to the domain model" for reference
> mapping.
> > For example, in Article we have to introduce
> another
> > field productGroupdId although we already have
> > productGroup. It seems that for jdo implementatin
> > without code enhancement , such intrusion is not
> > avoidable.
> > 
> > Regards,
> > Rice
> > 
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Tax Center - forms, calculators, tips, more
> > http://taxes.yahoo.com/
> > 
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> > 
> > 
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to