Thanks for the help! This may be helpful to all out there using the EJB
books in circulation as their mentor. The book I'm using, which is a
very very useful and clean, so much that I didn't think to doubt it,
provided me some flawed code as an example for Bean Managed Persistence.
It does not use the EntityContext in the ejbRemove method as it does in
the ejbLoad method. I have adjusted the code and it works perfect now.
Thanks!
Steven E. Sobczak
Email: [EMAIL PROTECTED]
-----Original Message-----
From: arkin [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, January 08, 2000 3:08 PM
To: EJB-INTEREST
Cc: arkin
Subject: Re: Enumeration of Remotes and their removal
> My question is, am I wrong to assume the container should invoke
ejbLoad
> after I have been given an Enumeration of Remote References and
before I
> invoke an ejbRemove on any of them?? Does this seem like a bug in
the
> container?
Yes. The enumeration you get has sufficient information to remove the
entity beans (ii.e. the primary keys), it does not have to load them
in
order to remove them. Most likely the container is trying to access
the
bean itself, unknowing that it is not initialized.
arkin
>
> Steven E. Sobczak
> Email: [EMAIL PROTECTED]
=====================================================================
======
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".
