From J2EE 1.3 EJB API: public void remove(java.lang.Object primaryKey) throws java.rmi.RemoteException, RemoveException Remove an EJB object identified by its primary key. This method can be used only for an entity bean. An attempt to call this method on a session bean will result in a RemoteException. From EJB 2.0 Specification: Because session objects do not have primary keys that are accessible to clients, invoking the javax.ejb.EJBHOME.remove(Object primaryKey) method on a session bean result in the javax.ejb.RemoveException
I got yeah Mr. Chen: The issue is actually about RemoteException and RemoveException. Sorry I jumped in without invitation. I do not think that I am qualified right now to contribute to this topic until I get my HF EJB from Amazon. Thanks, Anselm.
Even I was carried away a bit by the question, as it had 2 stmts with no question. I tried to remove a stateless session bean in Sun's RI with the home handle and I obtained on the client side. javax.ejb.RemoveException: Invalid remove operation. <<no stack trace available>> So the EJB2.0 Spec is right. Isn't it?