Weird issue with WS code and Eclipse 3.6
by Brian Fitzpatrick
Hey all...
I'm trying to fix https://jira.jboss.org/browse/JBIDE-6428 and am running into some bizarre issues...
As I say in the last JIRA comment I just added:
"It looks like I can take care of the compile errors, but then I end up with this:
An internal error occurred during: "Invoking web service...".
(class: org/jboss/tools/ws/ui/utils/JAXWSTester, method: doTest signature: (Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V) Incompatible object argument for function call
I'm guessing there are incompatibilities with the WSDL libraries, but nothing I do has managed to work around this yet except for removing the 1.3 version of the javax.soap plug-in from the runtime plugins. I've tried enforcing the 1.2 version as the upper bound and that doesn't help at all."
Any suggestions on how to work around this? I'm using JDK 1.6.0_14 and Eclipse 3.6 RC3 plus the latest trunk build and a few fixed plug-ins from the 3.2_Helios branch.
Thanks in advance. I'm pulling my hair out on this one...
--Fitz
_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat
16 years, 1 month
- 2
- 5
Importance of testing on Helios
by Andersen Max
Hi,
It's important we test Helios and report any issue we find that can possibly hurt our adoption and if
needed mark them as hotbugs at Eclipse.
Just today Alexey K. pointed me to https://bugs.eclipse.org/bugs/show_bug.cgi?id=315390 which is really
a big usability issue in Helios when it comes to EJB3/JEE 6 usage of Eclipse.
I've gone and marked this as an hotbug in an attempt to get it fixed before the main release.
Please be sure if you find such usability issues to report them in our jira with a link to bugzilla
and ping me and ill help raise them as hotbugs if needed.
Thanks,
/max
16 years, 1 month
- 1
- 0
3.1.x branch is open for business again
by Andersen Max
Hi,
3.1.1 have been tagged and JBoss Tools 3.1.1 is out.
3.1.x branch is therefore open for 3.1.2 issues.
Please ensure you resolve issue against 3.1.2 and not just 3.1.x :)
/max
16 years, 1 month
- 1
- 0