[
https://jira.jboss.org/jira/browse/JBAS-7807?page=com.atlassian.jira.plug...
]
Carlo de Wolf resolved JBAS-7807.
---------------------------------
Resolution: Rejected
Any class used as an argument (or return type) on an EJB method is considered to be an
user / application class.
It's not up to the container to ensure that both client and server have the same
version of those classes installed.
EJB method having QName as an argument fails on jboss
------------------------------------------------------
Key: JBAS-7807
URL:
https://jira.jboss.org/jira/browse/JBAS-7807
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB3
Affects Versions: JBossAS-5.1.0.GA
Environment: linux
Reporter: Rishi Agarwal
Assignee: Carlo de Wolf
I have a EJB method that has javax.xml.namespace.QName as an argument. On trying to
connect to it from the jse client it gives the following exception: Our EJBs are deplyed
on JBOSS AS 5.
java.lang.RuntimeException: java.io.InvalidClassException: javax.xml.namespace.QName;
local class incompatible: stream classdesc serialVersionUID = -9120448754896609940, local
class serialVersionUID = -711357515002332258
After removing QName class from stax-api.jar in the endorsed\lib directory , i could
successfully invoke the EJB method. This is the due to the fact the QName class is
available as part of JRE libraries as well and i guess this is a well-known fact that
there are issue around it due to incompatible serialVersionUID.
Now my point is what is the solution to resolve this.We can't recommend removing
QName class from stax-api.jar for EJBs( methods with QName as argument) to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira