This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 87181 - Test operation for JAX-RPC client does not work
Summary: Test operation for JAX-RPC client does not work
Alias: None
Product: webservices
Classification: Unclassified
Component: Client (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker with 2 votes (vote)
Assignee: bhate
Keywords: RELNOTE
: 95771 113930 121706 (view as bug list)
Depends on:
Blocks: 121706
  Show dependency tree
Reported: 2006-10-15 19:15 UTC by Lukas Jungmann
Modified: 2008-03-26 21:01 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2006-10-15 19:15:12 UTC
if IDE is running on Mustang, following exception is being thrown:

com.sun.xml.internal.messaging.saaj.soap.ver1_1.Message1_1Impl cannot be cast to
Comment 1 Lukas Jungmann 2006-10-15 19:16:41 UTC
Workaround is to run IDE on JDK 1.5.
Comment 2 Milan Kuchtiak 2006-11-29 17:20:27 UTC
It's a JDK16 <->JAX-RPC1.6 clash.

The bundled JAX-RPC library consists, exactly, of jar files taken from jwsdp-1.6.
Specifically :

WS Registry works with those classes .

The set of JDK1.6 (rt.jar) classes overlaps with those specified in JAX-RPC
library : specifically saaj-impl.jar.

JDK1.6 <-> JAX-RPC clash can be avoided by putting JAX-RPC jars at the beginning
of the Netbeans bootclasspath.
(I tested that and it works)

Now, I don't see any reasonable solution on Netbeans site.
Comment 3 Lukas Jungmann 2006-12-11 01:47:41 UTC
Milan, thanks for your evaluation. I've asked a question at JAX-RPC team's
mailing list. Let's see what do they think about this.
Comment 4 Lukas Jungmann 2006-12-12 09:54:55 UTC
Response from JAX-RPC team:

"...We fixed a bug in saaj to find the right factories when used with JDK 6.
Please update your saaj jars from and let us  know if
the issue is resolved."
Comment 5 Petr Blaha 2007-02-02 17:29:09 UTC
The saaj library was upgraded in issue #93423.
Comment 6 Jaroslav Pospisil 2007-02-07 14:42:34 UTC
I tested new 551 build with saaj 1.3 and issue is still there. However the issue
occurs only when testing default WS operation without any parameter and
returning null value (default WS template).
I tested also scenario with WS with one string parameter and it proceeded normally.
First case, on other hand, causes future exceptions in any type of WS operation,
even these with parameters.
Comment 7 Lukas Jungmann 2007-06-19 16:15:25 UTC
JAX-RPC in Java SE project works on JDK6 if the project is run with
"-Djavax.xml.soap.MessageFactory=com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl". I didn't check
anything related to web/ejb modules yet...
Comment 8 Lukas Jungmann 2007-08-28 09:01:08 UTC
*** Issue 113930 has been marked as a duplicate of this issue. ***
Comment 9 bhate 2007-09-28 20:44:58 UTC
Lukas do we still have test web service method in 6.0?
Comment 10 Lukas Jungmann 2007-09-30 01:08:29 UTC
yes, we do. But it's available only for JAX-RPC clients on the ws operation node in project view
Comment 11 Lukas Jungmann 2007-10-06 02:21:48 UTC
*** Issue 95771 has been marked as a duplicate of this issue. ***
Comment 12 Jaroslav Pospisil 2007-11-12 11:54:08 UTC
*** Issue 121706 has been marked as a duplicate of this issue. ***
Comment 13 bhate 2008-03-06 21:01:12 UTC
I have updated latest saaj version in the jaxrpc libraries.
changeset 6175104b11f5.
Comment 14 Lukas Jungmann 2008-03-26 21:01:45 UTC
v. (has been fixed in 6.1 => setting appropriate TM)