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

[Snjezana Peco (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564178#comment-12564178 ] 

Snjezana Peco commented on JBIDE-6450:
--------------------------------------

I have found two ways to use org.apache.axis and javax.xml.rpc plugins instead of axis.jar and jaxrpc.jar:

1) 
- add "Require-bundle : system.bundle" to the javax.xml.soap 1.3.0 plugin (javax.xml.soap 1.2 has this dependency). System bundle (org.eclipse.osgi) will export all packages contained in the current VM. o.j.t.ws.ui will import javax.xml.soap and javax.xml.ws from JDK.
- remove the javax.xml.soap and javax.xml.ws dependency from the o.j.t.ws.ui plugin
This isn't a recommended way to add the system.bundle dependency.

2) 
- set the JavaSE-1.6 environment to the org.apache.axis and javax.xml.rpc plugin
- remove the javax.xml.soap and javax.xml.ws dependencies from the o.j.t.ws.ui, org.apache.axis and javax.xml.rpc plugin. 
I am not sure if the Orbit team will accept the plugins that declare the JavaSE-1.6 environment. 

Note : javax.xml.ws is added using Require-Bundle and Import-Package to o.j.t.ws.ui.You have to remove both.

> 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.Beta2
>
>         Attachments: axis.jar, jaxrpc.jar, org.jboss.tools.ws.ui.patch, org.jboss.tools.ws.ui2.patch
>
>   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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira