RMI-IIOP needs objects implementing Serializable.
EJBException does not directly implement Serializable, but inherits Serializable from its super class.
Perhaps your compiler or your j2sdkee is too old to take this into account.
Perhaps upgrading your J2SDKEE version to v1.3 could help.
> RMI-IIOP needs objects implementing Serializable.
> EJBException does not directly implement
> Serializable, but inherits Serializable from its
> super class.
> Perhaps your compiler or your j2sdkee is too old to
> take this into account.
> Perhaps upgrading your J2SDKEE version to v1.3 could
It's not because of the compiler. It's jboss verifier. This topic has been discussed in the mailing list a couple of months ago.
If your method has EJBException (or any subclass of RuntimeException), jboss verifier marks it as invalid according to RMI/IIOP. IMHO, it is ... but this is how it's working for now. Just remove EJBException from the throws clause and this message will disappear ..
Thanks for your responses.
I do not have EJBException thrown by any of the method in the entity bean classes. Also they are following EJB 1.1 so each get/set method in entity bean is implemented by me. The entity bean class is also not declared as abstract. Even after not declaring either the class or the methods as abstract, also not throwing EJBException I am getting the error message dumped on the screen.
I forgot to mention I am using latest stable release i.e JBOSS 2.4.4 release with tomcat and JDK1.3.1 version.