Ok, but jboss4.2 requires jdk5 so this is a non-issue.
If we are doing jboss-4.0.x to jboss-4.2.x compatibility tests, the
jboss-4.2.x based client needs to run under jdk5. You still should be
able to run jboss-4.0.x based clients under jdk14. The interop issues
will be along the lines of jmx remoting, and leaking jdk5 based classes
in return values (like new util classes deep in a proxy). For the
interop we need to support we'll have to test it.
Dimitris Andreadis wrote:
I tried jbossxb 1.0.0.CR8 in jboss 4.2, that was compiled with jdk5,
due
to jboss-test (imported by jbossxb) being compiled with jdk5.
So all 1.4 based testsuite builds of jbossas 4.2 break immediately due
to the jbossxb jdk5 compiled classes.
Do we need to just drop those builds?
Also, how to deal with the compatibility tests? The way we use client
libs from one jboss version against a running server of another version
(e.g. 4.2 client libs against 4.0 server) will not work, unless we run
the client with jdk5.
Is this what we are supposed to do? i.e. require all jboss 4.2 compiled
code to need a jdk5 runtime?
Do you see any other issue interoperating with older servers running on
jdk1.4 ?