> I think ejbStore and ejbLoad is an overhead in case of Entity
> beans because unnecessary DB calls are made even if i haven't updated
anything
> in my bean.
??
I dont think that is a very huge performance killer.
> Implement only ejbCreate and ejbLoad methods and do not implement
> ejbStore. For DB consistency, After each update operation, i write sql for
> updating into the database. This also solves my problems of table joins
(joins are
> inevitable in my application).
Where are you then going to write the sql for updates?
Whats the problem with table joins?
The ejbStore is neccesary to let the container take care of updates, this
happens e.g. on the transaction demarcation - when you are doing something
that changes the entity and finish it. (se the 1.1 spec. at page 106).
Table joins etc. are handled in the database you use.
/Jon
===========================================================================
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".
