[JBoss JIRA] Created: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
by Brian Fitzpatrick (JIRA)
Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
----------------------------------------------------------------------------------------------------------
Key: JBIDE-6450
URL: https://jira.jboss.org/browse/JBIDE-6450
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.0.M1
Reporter: Brian Fitzpatrick
Assignee: Brian Fitzpatrick
Priority: Critical
Fix For: 3.2.0.M1
Finally got to the heart of the java.lang.VerifyError issue I've been running into with the WS Tester.
javax.xml.soap (1.2) is an old-school plug-in jar wrapper that takes saaj.jar and exposes it in Eclipse.
javax.xml.soap (1.3) is a new-school OSGI-compatible wrapper that builds the individual saaj classes and wraps them to expose them in Eclipse.
As Nick said in a recent IRC chat - ".jar!/org/whatever/*.class is better than .jar!foo.jar". But in my case, it causes the lovely java.lang.VerifyError when I try to use a utility class that takes advantage of classes from javax.xml.soap.
After doing some digging, it turns out the javax.xml.soap (1.3) plug-in is coming from the Atlassian update site for the latest & greatest version of their JIRA/Mylyn plug-ins. Without Atlassian JIRA connectors installed, it runs just fine.
So this presents an issue... If we're meant to certify against Atlassian JIRA connectors, this is going to come up again. So how do we work around it?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-6398) SeamValidatorsAllTests fail intermittently on slaves soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64 for both JBT & JBDS builds
by Nick Boldt (JIRA)
SeamValidatorsAllTests fail intermittently on slaves soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64 for both JBT & JBDS builds
--------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-6398
URL: https://jira.jboss.org/browse/JBIDE-6398
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing
Affects Versions: 3.1.1
Reporter: Nick Boldt
Not sure why these tests appear here:
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly-3.... (vmg20-rhel5-x86)
Then disappear (failed? disabled? missing?) for all builds since.
And, similarly:
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa6-rhel5-x86_64)
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (soa6-rhel5-x86_64)
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... (vmg20-rhel5-x86)
But once again disappear (failed? disabled? missing?) for these builds:
#109, 110, 111 (soa4-rhel5-x86_64, vmg19-rhel5-x86, vmg18-rhel5-x86_64)
I wonder if the problem is one of configuration of the slaves (bad config? low ram? low disk?) or that the tests are too greedy/misconfigured?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months