Quoting Aria Aram <[EMAIL PROTECTED]>:
> The problem with the entity beans are that even if the app server supports
> one-to-many, it would be a proprietary implementation since that's not in
> the EJB spec., In my opinion until problems such as this and scalibility is
> not addressed with entity beans, we should avoid using them. So stick to
> session beans and an O/R mapping tool.
alternatively, you could use a OneToMany relationship bean that I've got under
beta testing (if you can stand using beta code). It's as portable as I could
make it -- entity bean using bean-managed persistence, uses standard SQL,
scalable (if the 'many' side is large), etc.
It's open source -- http://www.simscomputing.com/products/etk/
regards,
david
--
David Sims [EMAIL PROTECTED]
Sims Computing, Inc. www.simscomputing.com
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
