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 174557 - [68cat] Incompatible JAX-WS implementation
Summary: [68cat] Incompatible JAX-WS implementation
Status: RESOLVED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-14 14:48 UTC by Peter Nabbefeld
Modified: 2009-10-28 16:51 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2009-10-14 14:48:27 UTC
[ JDK VERSION : 1.6.* ]

The JAX-WS module uses JAX-WS RI 2.2-b02-rc1, which generates
incompatible code, e.g.:

public class IntegerAdderService extends Service {
    ...
    public IntegerAdderService(WebServiceFeature... features) {
        super(INTEGERADDERSERVICE_WSDL_LOCATION,
INTEGERADDERSERVICE_QNAME, features);
    }
    ...
}

There's no three-argument constructor in class Service.
Even worse, it seems 2.2 is only used for generating, not for
compiling and running the code. And I cannot find any
description/specification for 2.2. Probably it's available at
jax-ws.dev.java.net, but this web site doesn't work anymore - having
tried several days at different times :(
Comment 1 swpalmer 2009-10-16 14:16:50 UTC
I've had similar problems trying to use 6.8.  I can't compile my project because 6.8 has switched the project to JAX-WS 
2.2 from 2.1 and does so in a manner that leaves the build scripts broken.

I get this error:

W:\MyProject\nbproject\jaxws-build.xml:17: You are running on JDK6 which comes with JAX-WS 2.1 API, but this tool 
requires JAX-WS 2.2 API. Use the endorsed standards override mechanism 
(http://java.sun.com/javase/6/docs/technotes/guides/standards/), or set xendorsed="true" on <wsimport>. 

I tried adding the JAX-WS 2.2 library to the project, but that doesn't change anything.  Why isn't NB 6.8 putting the 
appropriate JAX-WS 2.2 jars on the classpath for Ant?  I'm expecting NB to make an ant build file that "just works".
Comment 2 Jiri Kovalsky 2009-10-20 20:16:02 UTC
Milane, can you please comment on this issue? Thanks!
Comment 3 Milan Kuchtiak 2009-10-21 08:59:40 UTC
These problems has been resolved by adding endorsed classpath.
See the issue 173427, issue 173428 and issue 172952.

> W:\MyProject\nbproject\jaxws-build.xml:17: You are running on JDK6 which comes with JAX-WS 2.1 API, but this tool 
requires JAX-WS 2.2 API. Use the endorsed standards override mechanism 

Please, go to Client Node (WS Reference node) -> Edit WS Attributes -> Wsimport options
 and set xendorsed option to true 
Comment 4 swpalmer 2009-10-27 21:05:45 UTC
So the "solution" is to force users to upgrade to JAXWS 2.2?  JAXWS 2.1 is not longer supported in NetBeans 6.8?

In any case I don't understand the fix, or rather I can't find what is meant by "Client Node (WS Reference node) -> Edit 
WS Attributes -> Wsimport options"  What exactly is "Client Node (WS Reference node)" and where do I find it?  I see 
nothing with that name in the NetBeans UI.  I've looked in the Project properties, the Projects window, all the menus, 
etc.
Comment 5 swpalmer 2009-10-27 21:48:41 UTC
Since I am still unable to build my projects with NetBeans 6.8 due to this issue, I've voted for this as a showstopper.

I manually edited the jaxws-build.xml so that the xendorsed="true" attribute is set on the <wsimport> element.  But then 
my application fails to compile.  I get many errors that look like this:


W:\path\to\MyProject\build\generated-sources\jax-ws\my\package\myClass.java:36: cannot find symbol
symbol  : method required()
location: @interface javax.xml.bind.annotation.XmlElementRef
    @XmlElementRef(name = "return", type = JAXBElement.class, required = false)


Are we really expected to change all our code just to update our IDE?
Comment 6 swpalmer 2009-10-28 16:51:34 UTC
Ok... I have found what was going wrong.. I reverted all my nbproject files back to their 6.7 state and opened them again 
with NB 6.8 and the problem is gone.  An earlier 6.8 build must have made a change to the project files that broke things 
for later builds. 

Sorry for the noise.