[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=12563691#comment-12563691 ] 

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

The problem is that javax.xml.ws, javax.xml.rpc and org.apache.axis import javax.xml.soap, but don't declare any version.
This can be solved in the following ways:

1) 
- fixing the above mentioned plugins
This could affect plugins that depend on javax.xml.ws, javax.xml.rpc and/or on org.apache.axis

2) 
- adding axis.jar from org.apache.axis and jaxrpc.jar from javax.xml.rpc to o.j.t.ws.ui/lib
- removing the javax.xml.rpc and org.apache.axis dependencies
- removing the javax.xml.ws and javax.xml.soap dependencies (o.j.t.ws.ui requires the JavaSE-1.6 environment; JDK 1.6 contains those packages)
- adding dependencies required by axis.jar and jaxrpc.jar
- adding log4j.properties from org.apache.axis to the src directory

The attached patch (org.jboss.tools.ws.ui2.patch) implements the second solution.
After applying the patch, it is necessary to add the attached axis.jar and jaxrpc.jar to the lib directory.

After that you will be able to open the WS Tester view and call the WS operations you described (with and without javax.xml.soap 1.3).

> 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: org.jboss.tools.ws.ui.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