there are no
choices?
Thanks,
Tim.
-Original Message-
From: Frank Eggink [mailto:[EMAIL PROTECTED]]
Sent: 16 January 2001 10:31
To: Orion-Interest
Subject: RE: mapping of existing m2m tables
Maybe a bit late, but I guess using custom finder queries in the home
interface could be an option as wel
to copy and
> paste so much between beans!
>
> Two problems: one the JSP pages are getting a bit big, two the JSP
> programmers take a little longer to understand the theory.
>
> Thanks again and please post again if you have any more ideas,
> Tim.
>
> -Original Mes
AIL PROTECTED]]
Sent: 12 January 2001 14:46
To: Orion-Interest
Subject: Re: mapping of existing m2m tables
Hi Tim,
Sounds like you've implemented this with Entity EJBs. I could be wrong,
but most J2EE platform products (WebLogic, Orion, etc) implement Entity EJb
containers so that there is
Hi Tim,
Sounds like you've implemented this with Entity EJBs. I could be wrong,
but most J2EE platform products (WebLogic, Orion, etc) implement Entity EJb
containers so that there is an instance of a given Entity bean for every
existing row in your table -- for large databases, this means that
Hi,
Probably been asked before but I can't find it in archives.
I have a legacy database with over 80 tables, most of them represent many to
many relationships (M:N) just with 2 or 3 foreign keys. I'm building a EJB
layer on top and the initial load is proving to be a bit slow.
An example of s
