Hello,
I've read carefully the posts concerning entity beans
performance issue. I made up my mind that it's a waste
of resources to use ejbFind methods in Entity Beans
because this will cause an useless trip to ejbLoad and
ejbStore methods (if I have understood correctly).....
rather for find methods one could always use Session Beans...
maybe even if I'm looking for the primary key.
What do you think about it?
An one more issue - this I have to post it again sorry-
In which key of the Context do I have to put the
Transaction, in order to retrieve it via JNDI like this :
UserTransaction ut =
(UserTransaction)context.lookup("javax.jts.UserTransaction");
I cannot find a key like USER_TRANSACTION..maybe I have
to insert into my Server's properties file (weblogic) ?
Thanks
Francesco
===========================================================================
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".
