-
15. Re: JBAS-1854 - Compatibility 3.2.x vs 4.2.x
Ryan, is the content of 3_2_x & 4_0_x updated dynamically with libs as the source code changes, or are they statically copied by hand?
-
16. Re: JBAS-1854 - Compatibility 3.2.x vs 4.2.x
We have a server that's running 3.2.6 and would like to be able to talk to it using 4.0.3.
Looking at the source, apparently 4.0.3 -> 3.2.6 compatibility was not added, specifically 4.0 has no way to assign the OLD serial version ID to GUID.
http://fisheye.jboss.com/viewrep/JBoss/jboss-common/src/main/org/jboss/util/id/GUID.java
Should I go ahead and fix this? -
17. Re: JBAS-1854 - Compatibility 3.2.x vs 4.2.x
I'm not sure if we are interested supporting backwards compatibility for those old versions, I guess you can try.
Currently we check in org.jboss.util.id.SerialVersion the property org.jboss.j2ee.LegacySerialization to fall back to legacy serialVersionUIDs. But if you enchance this with yet older versions (3.2.6-) with e.g. setting org.jboss.j2ee.LegacySerialization=3.2.6 or whatever, you'll need to check every place where SerialVersion is used to make sure it still works. -
18. Re: JBAS-1854 - Compatibility 3.2.x vs 4.2.x
Do we have a wiki that documents the 3.2.x/4.0.x configuration settings that resulted from this work? I have not found one searching so far.
-