EjbRemove, remove(), bean logic, database row logic

Question

In some Sun examples the remove() method is not exposed trhu the home interface, but anyway it is called from the client thru the home interface, I would like to know the reason; another question is the logic after the remove() method exposed thru the remote interface versus the ejbRemove() method exposed (?) thru the home interface, so the question is:
- there is a logic directed to the bean (to delete de entity bean) and another logic directed to the persistent row represented by the bean?.
If I delete a row it is obvious the entity bean representing it should be deleted, but what happens if the client (or the container) invokes ejbRemove() either directly (the container) or trhu the home interface (the client) and I only want to delete the bean, but not the persistent row? Iin fact, the container could call ejbRemove as part of the bean lifecycle, and this should not imply the persistent database row delete, so it appears that the row delete code should not be in the ejbRemove() ?!
thanks.

Answer 1

I think that that the removing of an entity ejb should not imply the removing of the database row, thought the remove of the database row really implies the removing of the entity ejb representation. So, if you code an sql delete statement in the ejbRemove method, it implies that as consequences of the lifecycle of ten entity bean the row could be removed, and I think it is not allway rihgt, for if you want to remove the ejb representing your account (for example), to free server memory, it should not imply that yout account database row should be removed too, unless the ejbRemove method woulnd't be never called by the container, so, to cut it short: what happens if the container, as a consequence of the lifecycle of the bean, call ejbRemove and you coded in this method a sql delete, your account (for example) in your bank would dissapppear!, and you only wanted to free the memory associated to the entity ejb.
I think the remove() and ejbRemove() are tricky!
Maybe I don't understand well the basics of ejb, but I really thought a lot about this question.
thanks!