Hi John,
Neither, do I want this technology to die over performance
issues. But, this definitely is a problem. I believe, the problem stems from
the basic nature of how an Entity Bean interface was defined and how they
would be accessed & updated. The inherent problem of developing a
distributed application is the constant need to talk between components over
the network layer with a proprietary protocol. This could become a serious
bottle neck, if the application starts to have a lot of distributed
components. I'm hoping that Sun would probably come with a new kind of an
EJB with an interface that would help access data at a bulk and update them
in a bulk. That would avoid the network chattiness between distributed
components. The new interface could probably be modeled like the DAO
components. If the "stale data" issue is also addressed in the design
itself, I guess we would have a winner.
Lets hope Sun does something about it soon.
Winston.
John Harby wrote:
I really think there needs to be more tunables in terms of controlling when
database calls are made and obviously tighter integration with the database
optimization process to enhance performance of generated SQL.
BEA offers a "db-is-shared" tag and notes it isn't really too useful
because
most databases will not be exclusively used by the app server but what if
this became more granular and when I created a CMP I could have a DD tag
stating that the table(s) was exclusively for the use of
the app server (in terms of writes)? The container may not have to load as
often.
I'd hate to see this technology die over performance - Just my $.02
===========================================================================
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".
