[JBoss JIRA] Created: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
6:03 p.m.
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
1:18 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
Created a bug against Eclipse Orbit for this one to see if they have any ideas...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=317625
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
11:45 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
Also have been speaking to the folks at Atlassian about it, who seemed surprised that
their build had sucked in the 3.0 version of the plug-in...
https://support.atlassian.com/browse/ECSP-85
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
noon
New subject: [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6450:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Fix Version/s: 3.2.x
(was: 3.2.0.M1)
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.x
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
7:33 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
Well, seems that my faith in the Atlassian folks was misplaced... They're not going to
do anything about the issue, instead putting it back on us.
So short of somehow removing that javax.xml.soap (1.3) version of the plug-in if they
install JEE + JBT + Atlassian JIRA Connector, I'm at a loss.
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.x
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
1:25 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
The Atlassian folks have decided this isn't their problem.
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.x
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
2:51 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6450:
-------------------------------------
Fix Version/s: 3.2.0.Beta
(was: 3.2.x)
Need to find a) whether this is still an issue with the latest stuff from Atlassian and b)
how to fix it.
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.Beta
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
10:12 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
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
4:21 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Max Andersen updated JBIDE-6450:
--------------------------------
Assignee: Brian Fitzpatrick (was: Max Andersen)
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
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
4:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Max Andersen commented on JBIDE-6450:
-------------------------------------
Did we get this solved !?
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
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
6:47 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Max Andersen commented on JBIDE-6450:
-------------------------------------
After having a chat with Chris A. at Eclipse Summit we found the diff between 1.2 and 1.3
is the following:
1.2 manifest.mf:
Export-Package: javax.xml.soap;version="1.2.0"
1.3 manifest.mf:
Export-Package: javax.xml.soap;version="1.3.0"; uses:="javax.activatio
n, javax.xml.namespace, javax.xml.transform, org.w3c.dom"
Chris's hunch said that the "uses" clause might cause org.w3c.dom to be
"linked" to 1.3 even though our plugin is using 1.2 while also using
org.w3c.dom.
Suggestion is to try remove the uses clause completely in 1.3 manifest.mf and see if that
solves the problem.
If it does - we got a bugreport ;)
Brian, want to try this out ASAP and we might take it further ?
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
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
8:06 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
No love with the "uses" tweak. I get the same result. But thanks for the
suggestion! :)
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
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
10:07 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
At Max's suggestion, I also tried updating the 1.2 version of the plug-in and adding
the uses tweak (instead of removing it as we did initially with 1.3)... when both 1.2 and
1.3 are in the workspace with the uses clause in their MANIFEST.MF files, I still get the
same issue.
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
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
3:28 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco commented on JBIDE-6450:
--------------------------------------
If you want your plugin to use a specific version of some other plugin, it is better to
use Import-Package than Require-Bundle. Require-Bundle doesn't work if there are
indirect dependencies. The attached patch fixes the problem.
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
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
3:30 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco updated JBIDE-6450:
---------------------------------
Attachment: org.jboss.tools.ws.ui.patch
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
3:42 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
Actually it does and it doesn't. Much like many of my initial attempts to fix this,
with your patch I'm able to open the view, but unable to actually execute a web
service and retrieve results.
To test this with the WS Tester:
1) Copy "http://footballpool.dataaccess.eu/data/info.wso?WSDL" into the combo
box at the top of the view.
2) Click the button to the right of the combo box and select one of the available
operations.
3) Click the right-most button to the right of the combo box to execute the web search.
4) Now I get:
javax.xml.ws.WebServiceException: Unknown class type javax.xml.soap.SOAPMessage
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
3:44 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
The full exception I get now is:
!ENTRY org.jboss.tools.ws.ui 4 0 2010-11-15 14:40:06.591
!MESSAGE No message
!STACK 0
javax.xml.ws.WebServiceException: Unknown class type javax.xml.soap.SOAPMessage
at com.sun.xml.internal.ws.api.pipe.Stubs.createDispatch(Stubs.java:177)
at
com.sun.xml.internal.ws.client.WSServiceDelegate.createDispatch(WSServiceDelegate.java:377)
at
com.sun.xml.internal.ws.client.WSServiceDelegate.createDispatch(WSServiceDelegate.java:388)
at
com.sun.xml.internal.ws.client.WSServiceDelegate.createDispatch(WSServiceDelegate.java:370)
at javax.xml.ws.Service.createDispatch(Service.java:325)
at org.jboss.tools.ws.ui.utils.JAXWSTester2.doTest(JAXWSTester2.java:144)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.handleWSTest(JAXRSWSTestView2.java:1275)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2.access$25(JAXRSWSTestView2.java:1261)
at org.jboss.tools.ws.ui.views.JAXRSWSTestView2$18.run(JAXRSWSTestView2.java:1198)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
And again, this seems to be because the two versions (1.2 and 1.3) clash somehow in the
Eclipse classloader when it's trying to resolve any javax.xml.soap.* class at
runtime.
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
3:46 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
Thanks for looking into this though Snjezana - I'm out of ideas and have been beating
my head on my desk for months on this.
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
3 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
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
3:04 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Snjezana Peco updated JBIDE-6450:
---------------------------------
Attachment: org.jboss.tools.ws.ui2.patch
axis.jar
jaxrpc.jar
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
8:47 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
Thanks Snjezana, I'll give this a go today.
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
10:31 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
I'm still bouncing ideas back and forth with David Williams (WTP) over at Bugzilla
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=317625) as well.
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
1:51 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
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
5:49 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
Though comment 18, option #1 may not be the recommended way, it works great!! :)
I've brought it up with David Williams to see what they want to do.
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
3:52 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Max Andersen commented on JBIDE-6450:
-------------------------------------
Brian, is this something you want to do for Beta2 or not ?
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
8:18 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
I'm going to push this to CR1, to see if we can get this fixed in the Orbit plugin
javax.xml.soap 1.3 for the Helios SR2 release (and Indigo), but I suspect for 3.2 JBT/4.0
JBDS I'm simply going to have to wrap the jars as Snjeza suggested earlier. I hate to
do that, but it seems like the only way to get around this in the short term.
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.CR1
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
8:19 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://jira.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6450:
-------------------------------------
Fix Version/s: 3.2.0.CR1
(was: 3.2.0.Beta2)
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.CR1
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
3:07 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://issues.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-6450:
------------------------------------------
I have delivered the fix recommended by Snjeza in comment 15 (#2) for this release to
trunk (CR1). Once the Eclipse Indigo release goes out in June 2011 we should be able to
roll this back to just point to the plug-in wrapper vs. including the jars directly.
Classloader incompatibilities between javax.xml.soap (1.2) and
javax.xml.soap (1.3) when running WS Tester
----------------------------------------------------------------------------------------------------------
Key: JBIDE-6450
URL: https://issues.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.CR1
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
3:07 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://issues.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick resolved JBIDE-6450.
--------------------------------------
Resolution: Done
Classloader incompatibilities between javax.xml.soap (1.2) and
javax.xml.soap (1.3) when running WS Tester
----------------------------------------------------------------------------------------------------------
Key: JBIDE-6450
URL: https://issues.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.CR1
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
10:06 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester
[
https://issues.jboss.org/browse/JBIDE-6450?page=com.atlassian.jira.plugin...
]
Lukas Jungmann closed JBIDE-6450.
---------------------------------
v. in v20101218-0505-H346-CR1
Classloader incompatibilities between javax.xml.soap (1.2) and
javax.xml.soap (1.3) when running WS Tester
----------------------------------------------------------------------------------------------------------
Key: JBIDE-6450
URL: https://issues.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.CR1
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
5590
days inactive
5784
days old
jbosstools-issues@lists.jboss.org
29 comments
4 participants
participants (4)
-
Brian Fitzpatrick (JIRA) -
Lukas Jungmann (JIRA)
-
Max Andersen (JIRA)
-
Snjezana Peco (JIRA)