[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-1455) WS Tester View can't be loaded in JBDS after 3rd party plugins installation (subversive, m2eclipse, ....)

[Brian Fitzpatrick (JIRA)]

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

Brian Fitzpatrick updated JBDS-1455:
------------------------------------

         Assignee: Brian Fitzpatrick
    Fix Version/s: 4.0.0.CR1


This is a known issue. The problem is most likely that you have the Atlassian JIRA connector for Mylyn in your workspace or some other tooling installed that pulls in the javax.soap 1.3 version.

This will be fixed in the next version of Eclipse (Indigo, due out in June) but doesn't help us out in the short term. 

The workaround is to remove the 1.3 version of the javax.soap plug-in from your environment. 

I have it on my to-do list to implement Snjeza's shorter-term solution for CR1. 

> WS Tester View can't be loaded in JBDS after 3rd party plugins installation (subversive, m2eclipse,....)
> --------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-1455
>                 URL: https://issues.jboss.org/browse/JBDS-1455
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: runtime
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Jiri Peterka
>            Assignee: Brian Fitzpatrick
>            Priority: Critical
>             Fix For: 4.0.0.CR1
>
>
> This issue is related JBIDE-6450. When javax.xml.soap (1.3) bundle is loaded, it's unable to start WS Tester (java.xml.soap 1.2 can't be loaded properly). There is no problem on JBT 3.2.beta2, so it seems it's JBDS related (at least for some cases). 
> Error message:
> Could not create the view: Plug-in "org.jboss.tools.ws.ui" was unable to instantiate class "org.jboss.tools.ws.ui.views.JAXRSWSTestView2".
> java.lang.VerifyError: (class: org/jboss/tools/ws/ui/views/JAXRSWSTestView2, method: getOpNameFromRequestBody signature: ()Ljava/lang/String;) Incompatible object argument for function call
> 	at java.lang.Class.getDeclaredConstructors0(Native Method)
> 	at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> 	at java.lang.Class.getConstructor0(Class.java:2699)
> 	at java.lang.Class.newInstance0(Class.java:326)
> 	at java.lang.Class.newInstance(Class.java:308)
> 	at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> 	at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:904)

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira