Hi Manoj: Yes.
When a client calls remove in a session bean, the state changes from method ready to does not exist. When the client calls remove in an entity bean the state changes from ready to pooled. The container then manages pooled instances with unsetEntityContext. The container calls unsetEntityContext to move the entity bean's state from pooled to does not exist. -- Best Wishes, Richard C. Murphy, Sun Certified Enterprise Architect Manoj Kumar wrote:
Hi, Just have a query on the methods available in SessionBean interface against the methods available with EntityBean Interface. EnttityBean Interface has methods setEntityContext and unsetEntityContext, however the sessionbean interface has only setSessionContext and no unsetSessionContext. Can someone give a reason for this that why we donot need unsetSessionContext method in the SessionBean Interface! Thanks Manoj =========================================================================== 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".
-- Best Wishes, Richard C. Murphy, Sun Certified Enterprise Architect =========================================================================== 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".
