[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester

[Brian Fitzpatrick (JIRA)]

     [ https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Fitzpatrick updated JBIDE-6450:
-------------------------------------

    Fix Version/s: 3.2.0.Beta2
                       (was: 3.2.0.Beta1)


> 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: Max Andersen
>            Priority: Critical
>             Fix For: 3.2.0.Beta2
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> 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