[
http://jira.jboss.com/jira/browse/EJBTHREE-749?page=all ]
Brian Stansberry updated EJBTHREE-749:
--------------------------------------
Fix Version/s: EJB 3.0 RC11 - FD
AS 4.2.0 CR2
Affects Version/s: AS 4.2.0 CR1
EJB 3.0 RC9 - Patch 1
I was doing other work on this class and noticed the missing serialVersionUID, so this was
fixed for the AS 4.2.0.CR2 release. I'll close the JIRA once I confirm it's fixed
in trunk as well.
org.jboss.ejb3.remoting.IsLocalInterceptor does not has a
SerialVersionUID and causes problems when using jboss-ejb3-client.jar to access remote
session bean
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: EJBTHREE-749
URL:
http://jira.jboss.com/jira/browse/EJBTHREE-749
Project: EJB 3.0
Issue Type: Bug
Components: EJB3 Extensions
Affects Versions: EJB 3.0 RC9 - FD, AS 4.2.0 CR1, EJB 3.0 RC9 - Patch 1
Environment: Sun JDK 1.5.0.06 / Ubuntu 6.0.6
Reporter: Peter Salomonsen
Assigned To: Brian Stansberry
Fix For: EJB 3.0 RC11 - FD, AS 4.2.0 CR2
When using jboss-ejb3-client.jar to lookup a remote interface of an ejb3 stateless
session bean I get this exception:
Exception: javax.naming.CommunicationException [Root exception is
java.io.InvalidClassException: org.jboss.ejb3.remoting.IsLocalInterceptor; local class
incompatible: stream classdesc serialVersionUID = -3758782076801249473, local class
serialVersionUID = 595045557897063404]
When removing jboss-ejb3-client.jar and instead using the same jar as the server, it
works fine.
I guess the resolution may be to add a SerialVersionUID for
org.jboss.ejb3.remoting.IsLocalInterceptor
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira