> > That is true and untrue. There is nothing in the EJB specification that
> > limits EB's (EntityBeans) to be single row/single table. This is a
> > common misconception, and is a problem with knowing what's in the spec
> > and what are limitations of a specific implementation. I would advise
> > you to look at for example TOPLink or similar O/R tools for more
> > advanced implementations.
>
> Rickard,
>
> I see your point, but isn't it likely that *portable* beans will be limited
> to only the simplest schemes for container-managed persistence? It seems we
> are trying to have things both ways, by touting EJB as a technology (not a
> product), but deferring to specific products to solve the hard problems in
> building systems.
I have been able to build fairly complex EJBean relationships using CMP and
standard Finders, including references, inner table links, and one to many.
I will grant you that it would be nice if these were handling by CMP for me,
and that my performance may not blow your socks off. However, I am quite happy
that I did not have to invest in BMP, and the code that I did have to write
was simple and of modest size. And the application I am writing does not have
to support eToys at Christmas time! :)
tim.
Tim Endres - [EMAIL PROTECTED]
ICE Engineering, Inc. - http://www.ice.com/
"USENET - a slow moving self parody." - Peter Honeyman
===========================================================================
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".
