[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316879 ] Scott M Stark commented on JBAS-1552: - A testJ2EERI141Compatibility has been added to the org.jboss.test.compatibility.test.SerialVersionUIDUnitTestCase to validate the serialVersionUIDs between jboss and the 1.4.1 j2ee reference implementation binary values. JBoss use wrong version of javax.resource.ResourceException class file -- Key: JBAS-1552 URL: http://jira.jboss.com/jira/browse/JBAS-1552 Project: JBoss Application Server Type: Bug Components: JCA service Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 Environment: All platforms Reporter: Manfred Rosenboom Fix For: JBossAS-4.0.2 Final Attachments: build.properties, build.xml When passing a javax.resource.ResourceException via RMI into the JBoss application server we get the following error message: ... javax.resource.ResourceException; local class incompatible: stream classdesc serialVersionUID = 547071213627824490, local class serialVersionUID = 4770679801401540475 at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.invocation.Invocation.performCall(Invocation.java:345) ... When comparing class files, you can see, that JBoss 4.0.x doesn't use the same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference implementation). Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss version. So I assume, that this is a JBoss related problem. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[
http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316835 ]
Scott M Stark commented on JBAS-1552:
-
The change in setting the serialVersionUID is sufficient if there are no serial
fields involved, however if there are, then the serialPersistentFields must be
conditionally set and readObject/writeObject methods added to control the names
of the fields to read/write. For example, the
javax.enterprise.deploy.spi.status.ProgressEvent changes include:
/** @since 4.0.2 */
static final long serialVersionUID;
// Constants -
/**
* These field names match the j2ee 1.4.1 ri version names
*/
private static final ObjectStreamField[] serialPersistentFields;
private static final int STATUS_IDX = 0;
private static final int MODULE_ID_IDX = 1;
static
{
if (SerialVersion.version == SerialVersion.LEGACY)
{
serialVersionUID = 3097551795061550569L;
serialPersistentFields = new ObjectStreamField[] {
/** @serialField statuscode DeploymentStatus current deployment status
*/
new ObjectStreamField(status, DeploymentStatus.class),
/** @serialField targetModuleID TargetModuleID id of the event target
*/
new ObjectStreamField(moduleID, TargetModuleID.class)
};
}
else
{
// j2ee 1.4.1 RI values
serialVersionUID = 7815118532096485937L;
serialPersistentFields = new ObjectStreamField[] {
/** @serialField statuscode DeploymentStatus current deployment status
*/
new ObjectStreamField(statuscode, DeploymentStatus.class),
/** @serialField targetModuleID TargetModuleID id of the event target
*/
new ObjectStreamField(targetModuleID, TargetModuleID.class)
};
}
}
...
private void readObject(ObjectInputStream ois)
throws ClassNotFoundException, IOException
{
ObjectInputStream.GetField fields = ois.readFields();
String name = serialPersistentFields[STATUS_IDX].getName();
this.status = (DeploymentStatus) fields.get(name, null);
name = serialPersistentFields[MODULE_ID_IDX].getName();
this.moduleID = (TargetModuleID) fields.get(name, null);
}
private void writeObject(ObjectOutputStream oos)
throws IOException
{
// Write j2ee 1.4.1 RI field names
ObjectOutputStream.PutField fields = oos.putFields();
String name = serialPersistentFields[STATUS_IDX].getName();
fields.put(name, status);
name = serialPersistentFields[MODULE_ID_IDX].getName();
fields.put(name, moduleID);
oos.writeFields();
}
JBoss use wrong version of javax.resource.ResourceException class file
--
Key: JBAS-1552
URL: http://jira.jboss.com/jira/browse/JBAS-1552
Project: JBoss Application Server
Type: Bug
Components: JCA service
Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1
Environment: All platforms
Reporter: Manfred Rosenboom
Fix For: JBossAS-4.0.2 Final
Attachments: build.properties, build.xml
When passing a javax.resource.ResourceException via RMI into the JBoss
application server we get the following error message:
...
javax.resource.ResourceException; local class incompatible: stream classdesc
serialVersionUID = 547071213627824490, local class serialVersionUID =
4770679801401540475
at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
...
When comparing class files, you can see, that JBoss 4.0.x doesn't use the
same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference
implementation).
Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and
Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss
version. So I assume, that this is a JBoss related problem.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316638 ] Scott M Stark commented on JBAS-1552: - These are the current mismatches I am seeing in the javax.ejb javax.enterprise javax.jms javax.resource javax.security javax.transaction javax.xml and javax.management package namespaces: Class NameJ2EE RI 1.4.1 SerialVersionUIDBranch_4_0 SerialVersionUID javax.enterprise.deploy.spi.status.ProgressEvent 7815118532096485937 3097551795061550569 javax.management.InvalidApplicationException -3048022274675537269 2164571879317142449 javax.management.InvalidAttributeValueException 2164571879317142449 -3048022274675537269 javax.management.relation.RelationNotFoundException -3793951411158559116 5434016005679159613 javax.resource.ResourceException 547071213627824490 4770679801401540475 javax.resource.spi.ConnectionEvent5611772461379563249 2776168349823367611 javax.resource.spi.InvalidPropertyException -485903720300735741 -2395559483586818078 javax.resource.spi.work.WorkEvent -30636126350150472186971276136970053051 javax.security.jacc.EJBMethodPermission 1 141000 javax.security.jacc.EJBRoleRefPermission 1 141000 javax.security.jacc.WebUserDataPermission 1 141000 javax.security.jacc.WebRoleRefPermission 1 141000 javax.security.jacc.WebResourcePermission 1 141000 javax.xml.rpc.ServiceException-6582148924441189775-4042547292194127311 javax.xml.soap.SOAPException 5083961510786058130 -4385552115225336830 javax.xml.registry.JAXRException -396751348710944315 -4890474253443089374 javax.xml.namespace.QName -38520601203469050004418622981026545151 javax.xml.rpc.JAXRPCException 5213579554532711730 2012915834079496799 javax.xml.rpc.soap.SOAPFaultException -7224636940495025621 -290987278985292477 javax.xml.registry.RegistryException -2972094643801708304 5830899222180533586 JBoss use wrong version of javax.resource.ResourceException class file -- Key: JBAS-1552 URL: http://jira.jboss.com/jira/browse/JBAS-1552 Project: JBoss Application Server Type: Bug Components: JCA service Versions: JBossAS-4.0.1 SP1, JBossAS-4.0.1 Final Environment: All platforms Reporter: Manfred Rosenboom Fix For: JBossAS-4.0.2 Final Attachments: build.properties, build.xml When passing a javax.resource.ResourceException via RMI into the JBoss application server we get the following error message: ... javax.resource.ResourceException; local class incompatible: stream classdesc serialVersionUID = 547071213627824490, local class serialVersionUID = 4770679801401540475 at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.invocation.Invocation.performCall(Invocation.java:345) ... When comparing class files, you can see, that JBoss 4.0.x doesn't use the same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference implementation). Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss version. So I assume, that this is a JBoss related problem. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[
http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316170 ]
Adrian Brock commented on JBAS-1552:
I just submitted a potential fix to JBoss Head
on how to change the SerialVersionUID to allow both j2eeri and legacy JBoss
compatibility.
In javax.resource.ResourceException:
private static final long serialVersionUID;
static
{
if (SerialVersion.version == SerialVersion.LEGACY)
serialVersionUID = -1809703985388987999L;
else
serialVersionUID = 547071213627824490L;
}
Where SerialVersion decides which version to use from a system property:
/*
* JBoss, the OpenSource J2EE webOS
*
* Distributable under LGPL license.
* See terms of license at gnu.org.
*/
package org.jboss.j2ee.util;
import java.security.AccessController;
import java.security.PrivilegedAction;
/**
* Serialization Helper.p
*
* Contains static constants and attributes to help is serialization
* versioning.p
*
* Set the system property preorg.jboss.j2ee.LegacySerialization/pre
* to serialization compatibility with older jboss.
*
* @author a href=mailto:[EMAIL PROTECTED]Adrian Brock/a.
* @version $Revision: 1.1 $
*/
public class SerialVersion
{
// Static
/** Legacy */
public static final int LEGACY = 0;
/** The serialization compatible with Sun's RI */
public static final int J2EE = 1;
/**
* The serialization version to use
*/
public static int version = J2EE;
/** Determine the serialization version */
static
{
AccessController.doPrivileged(new PrivilegedAction()
{
public Object run()
{
try
{
if (System.getProperty(org.jboss.j2ee.LegacySerialization) !=
null)
version = LEGACY;
}
catch (Throwable ignored)
{
}
return null;
}
});
}
}
JBoss use wrong version of javax.resource.ResourceException class file
--
Key: JBAS-1552
URL: http://jira.jboss.com/jira/browse/JBAS-1552
Project: JBoss Application Server
Type: Bug
Components: JCA service
Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1
Environment: All platforms
Reporter: Manfred Rosenboom
Fix For: JBossAS-4.0.2 Final
When passing a javax.resource.ResourceException via RMI into the JBoss
application server we get the following error message:
...
javax.resource.ResourceException; local class incompatible: stream classdesc
serialVersionUID = 547071213627824490, local class serialVersionUID =
4770679801401540475
at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown
Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.invocation.Invocation.performCall(Invocation.java:345)
...
When comparing class files, you can see, that JBoss 4.0.x doesn't use the
same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference
implementation).
Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and
Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss
version. So I assume, that this is a JBoss related problem.
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1552) JBoss use wrong version of javax.resource.ResourceException class file
[ http://jira.jboss.com/jira/browse/JBAS-1552?page=comments#action_12316172 ] Adrian Brock commented on JBAS-1552: I've attached a simple ant build that can be used to determine serialVersionUID for both JBoss and J2EE classes. e.g. ant jboss -Dclass=javax.resource.ResourceException ant j2ee -Dclass=javax.resource.ResourceException JBoss use wrong version of javax.resource.ResourceException class file -- Key: JBAS-1552 URL: http://jira.jboss.com/jira/browse/JBAS-1552 Project: JBoss Application Server Type: Bug Components: JCA service Versions: JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1 Environment: All platforms Reporter: Manfred Rosenboom Fix For: JBossAS-4.0.2 Final Attachments: build.properties, build.xml When passing a javax.resource.ResourceException via RMI into the JBoss application server we get the following error message: ... javax.resource.ResourceException; local class incompatible: stream classdesc serialVersionUID = 547071213627824490, local class serialVersionUID = 4770679801401540475 at net.fsc.jca.tutorial.SimpleOltpConnectBean.callService(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.jboss.invocation.Invocation.performCall(Invocation.java:345) ... When comparing class files, you can see, that JBoss 4.0.x doesn't use the same class file as is used in Sun's j2ee.jar (J2EE 1.4 reference implementation). Both Sun Java System Application Server Platform Edition 8.1 2005Q1 and Oracle OC4J 10.1.3 use the same class file, which differes from the JBoss version. So I assume, that this is a JBoss related problem. -- 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 - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
