> Consider this problem...
> I am obtaining a ref to home from my client and then calling a
>findByMethod .. at the server side the following methods are called in
>sequence..
> First an ejbLoad...
> then an setEntityContext..
> Then if i call any other method on the instantiated bean it calls the
>ejbLoad once again..
> What i thought that in order to instantiate a bean setContext should
>have been the first method to be called..
>Iam using weblogic 5
I have BMP EJBs running on Weblogic 5.1. Here I know for a fact that the
order of the calls are:
1) ejbFindByXXX - returns one or more PrimaryKey(s), which then the
container stores in new newly generated EntityContext
2) setEntityContext - sets the EntityContext reference of the
about-to-be-instantiated bean with that generated from above
3) ejbLoad - Grabs the primary key from the EC to do db row lookup
For CMP, I believe the container "fleshes out" the bean somewhere between
steps #2 and #3, or at least that's what makes sense...
Gene
===========================================================================
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".
===========================================================================
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".
