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.
Currently Netbeans 5.5.1 and 6 support web service clients using either JAX-WS 2.1 or JAX RPC. Given that the current release of the Sun JRE ships with JAX-WS 2.0 I think that you should offer the option of using this version for generating clients. I currently have to stick with using 5.5 as my clients are JRE 6.0 based, use web start and web services and because you can't use endorsed directories with web start I have no option other than to use JAX-WS 2.0. As I understand it, JRE 6 update 3 will include JAX-WS 2.1, but until this is released it is a shame that I cannot make use of the newer Netbeans features. You already offer the choice of selecting JAX-RPC for web service client generation, surely it would be easy enough to add support for different versions of JAX-WS ?
When I use the output of a NB 5.5.1 library project (a JAR file) that contains the JAX-WS 2.1 web service proxies in a NB project with JDK 6.0 (only JAX-WS 2.0), I get lots of problems: 1. Sometimes background error checking complains wrong. It suggests importing proxy classes (importing "*" is not enough), but javac compiles the source without problems. 2. Sometimes background error checking stops working completely with this message in the console: ErrorChecker: file javax\xml\bind\annotation\XmlSeeAlso.class not found 3. When compiling the source, that uses a web service proxy, I get a warning from javac 6.0: warning: Cannot find annotation method 'value()' in type 'javax.xml.bind.annotation.XmlSeeAlso': class file for javax.xml.bind.annotation.XmlSeeAlso not found How do I work around this? I'd like to use NB 5.5.1 and JAX-WS 2.0 with JDK 6.0. I do not want to bundle JAX-WS 2.1 with my application.
At last ! I was beginning to think that I was the only one with this problem. Maybe someone will take some notice now ?
I suggest to add another option to WS Client-> JAX Version dialog : It can be : JAX Version : JAX-WS 2.1 (default), JAX-WS 2.0. JAX-RPC The JAX-WS 2.1/JAX-WS 2.0 option will be related to wsimport:target option (version of generated java artifacts)
java 6u5 has jax-ws 2.1.1 http://download.java.net/jdk6/ hence the endorsing problem for clients is removed. (using custom classloader is not needed anymore for webstart apps...) I fail to see the need for devoting developer resources to support jax-ws 2.0. 2.0 is hardly a working webservice stack, theres reason for the complete redesignin in 2.1. theres 5500 bugs to fix in nb6, how can this non 'issue' be allowed to exist ?. Its been known for a long time that jax-ws 2.1 will be put into the jdk 6, so i really fail to understand people demanding 2.0 support.
And 6u5 is released when ? Come on, all I was asking for was that Netbeans supported the publicly release version of Java 6. Hopefully this will soon not be a problem as I understand that JAX WS 2.1 will be included in update 4 (a blog somewhere said that update 3 was the last version that would include JAX WS 2.0). I get bombarded with 'use NB 6.0/NB 5.5.1' they are really good messages all the time (and I do agree - they are great) but it would be nice if they supported older library versions - note that the web service stuff still gives you the option to use JAX RPC ! Anyway, I did find a (less than perfect) work around - all I do is copy the JAX WS 2.0 libraries over the top of the 2.1 libraries - this at least allows me to build me code using NB5.5.1/6. If I want to make any significant changes to the code I just have to do this with NB5.0. Rob
Why the rush ? java 6u5 will for sure be *production ready* before NB6 ... NB6 FCS with 4K+ bugs is the scenario slated for the end of this year it seems. 4K+ bugs can never be production ready for real, perhaps for "joe doing his homework". but not for true serious application. So in my book it a paper launch if anything. NB6 is almost a complete architectural rebuild, so a larget amount of bugs/problems is for granted. It does not help to clacify the bugs as p3, its still the extreme amount of them that matters at the end of the day. Myself is really looking forward for a *prod ready* NB6, but thats something happening in 2008.
I'm using NB6 in a production environment now. There are so many improvements that I am happy to live with this problem for now. The editor and code completion changes alone make it worthwhile. Anyway, hopefully NB6 will be released around the same time as 6u4 (which should hopefully have JAXWS2.1) so the problem should then disappear for me :)
Following the discussion in this issue I should note that JDK6u3, which has been already released and which is available at http://java.sun.com already contains JAX-WS 2.1.x ;) Try to give it a chance, please...
http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21_in_jav.html implies that u3 still contains JAXWS 2.0. Indeed the release notes for u3 don't make any mention of a new version of JAXWS. What makes you think it is in u3 ? Rob
See also: http://forums.java.net/jive/thread.jspa?threadID=29510&tstart=30
you're right, I found I'm using some pre-released u3 build which has 2.1.1 version in it... Thanks for the pointers and sorry for confusion
java 6u3 has NOT jax-ws 2.1 , please dont spread missinformation like that. http://weblogs.java.net/blog/ramapulavarthi/archive/2007/10/jaxws_21_in_jav.html "JDK 6 Update 3 will be the last Java SE 6 release using JAX-WS 2.0" 6u5 b04 is the available version that do have jax-ws 2.1.1
gustav3d: how your statement differs from what I've said??? u3-ea (my old version): lukas@pomeray:/space/java/sdk/jdk1.6.0_03/bin$ ./java -version java version "1.6.0_03-ea" Java(TM) SE Runtime Environment (build 1.6.0_03-ea-b02) Java HotSpot(TM) Client VM (build 1.6.0_03-ea-b02, mixed mode, sharing) lukas@pomeray:/space/java/sdk/jdk1.6.0_03/bin$ ./wsimport -version JAX-WS RI 2.1.1 in JDK 6 u3-fcs (final version, which is available): lukas@pomeray:/space/java/sdk/tmp/jdk1.6.0_03/bin$ ./java -version java version "1.6.0_03" Java(TM) SE Runtime Environment (build 1.6.0_03-b05) Java HotSpot(TM) Client VM (build 1.6.0_03-b05, mixed mode, sharing) lukas@pomeray:/space/java/sdk/tmp/jdk1.6.0_03/bin$ ./wsimport -version JAX-WS RI 2.0_02-b08-fcs
jungi , my apologies.
Providing support for jaxws 2.0 in NB is not possible at this time. Changing the target milestone to future.
Changing this into an enhancement. btw, if the requirement is simply to generate code that is in accordance with a specific JAXWS version (2.0 or 2.1), there is now a new enhancement in Netbeans 6.1 for specifying the wsimport target version. Right click on the ws or client node and select "Edit Web Service Attributes". Go to the "wsimport options" tab and enter "target" as the option name and "2.0" as the value.
moving opened issues where TM != dev to TM=TBD