Hide Forgot
Date of First Response: 2008-07-04 06:17:50 project_key: SOA
Sun-only JDK for now.
"it seems this is mostly about i) compiling the sources with JDK5 (not 6) and ii) setting a system property (classloading behaviour has changed in the JVM) and, obviously, retesting everything as we will probably face a few glitches left and right (it seems the ordering of the returned value of some Reflection calls has changed - potentially having some side-effects on implicit assumptions we did - or glitches like that)."
Link: Added: This issue is a dependency of JBQA-1580
All of the projects as well as EAP, which should be done in their next CP. That means we'll need to tied up out CP02 release with the EAP JDK6 CP release.
from email I was able to complete the Seam EAP 4.3.GA_CP01 testing with JDK 6 earlier than estimated. I am happy to report that it was more successful than I expected, but I'm looking into why ;) The only issues found were known issues from previous testing, and were unrelated to JDK versions. I will update or enter jiras as needed.
Link: Added: This issue depends JBESB-1674
Link: Added: This issue depends JBPM-1337
Link: Added: This issue depends JBRULES-1666
Link: Added: This issue is a dependency of JBRULES-1666
ESB is now running CI against 1.5 and 1.6 jdks.
I ran the jBPM and JbossRules samples in soa-4.3.0.GA_IR1 release against Jdk 1.6.0_05-b13 . There are two sample failed : bpm_orchestration1---Passed bpm_orchestration2---Passed bpm_orchestration3---Passed bpm_orchestration4---Passed business_ruleservice_ruleAgent -- Standalone mode Failed business_ruleservice_stateful -----Standalone mode Failed business_rules_service ---Passed There are classpath problem causes the two samples failed . The error message is same as JBESB-1947 . This issue should be fixed because the fix for JBESB-1947 also works for these two samples.
Several people have tested the build and a build has been through the standard CI suite. One problem with WS reported which may be a problem in the CI build - investigating.
warn found in one of the quickstarts, was there in IR4 so not jdk 6 related. separate jira raised - SOA-799