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.
1. Start IDE with jdk 1.6.0_01. 2. Create "Visual Web Application". 3. Rightclick application in Projects window and select "New > File/Folder...". 4. Select "Web Services" in Categories and "Web Service Client" in File Types. Click Next. 5. Enter http://www.webservicemart.com/uszip.asmx?WSDL for WSDL URL, select package and click Finish. Result: Web Service Client's build fails with message: "init: wsimport-init: Created dir: C:\Documents and Settings\rm153204.GRIF\WebApplication2\build\generated\wsimport\client Created dir: C:\Documents and Settings\rm153204.GRIF\WebApplication2\build\generated\wsimport\binaries wsimport-client-check-uszip.asmx: wsimport-client-uszip.asmx: C:\Documents and Settings\rm153204.GRIF\WebApplication2\nbproject\build-impl.xml:295: You are running on JDK6 which comes with JAX-WS 2.0 API, but this tool requires JAX-WS 2.1 API. Use the endorsed standards override mechanism (http://java.sun.com/javase/6/docs/technotes/guides/standards/), or set xendorsed="true" on <wsimport>. BUILD FAILED (total time: 2 seconds)"
Issue occurs for Java EE 5 project.
For J2EE 1.4 projects there is no build error, but Web Service Client is not generated and can be used. It's true for "Java EE Container-generated static stub" and for "IDE-generated static stub".
which target server do you use? It works fine for me with GlassFish-v2-b57... BTW: did you update web project from hotfixes UC?
also check whether it cannot be related to space in path to your project (ie create project in c:\tmp), please
Please, add information about Sun Java System Application Server version. Please, attach also the build-impl.xml file to see the wsimport-client-uszip.asmx target. Seems like a problem with endorsed mechanism.
I downloaded NetBeans 5.5.1 aтв VWP from http://www.netbeans.info/downloads/index.php. Also downloaded СТВ pack from http://smetiste.czech.sun.com/builds/cnd/5.5.1u1/Build070731/installers. I also use GlassFish V2-b57. But I have spaces in project path. Is there filed bug for this?
It works fine with jdk 1.5.0_11.
Could you please also attach the build-impl.xml file.
Created attachment 46122 [details] Application
Added application, which causes this issue. And I tried with path without spaces. The same result.
The issue is fixed in Netbeans 60 (by introducing an xendorsed attribute for wsimport).
and the fix should be already available on the hotfix UC. We need confirmation from Roman...
I installed all HotFixes from UC, but still can reproduce this problem.
Created attachment 46134 [details] Application
The problem lies in Visual web project type's XSLT template for build-impl.xml - it is not taken care about JAX-WS 2.1 on JDK 6 related issues there. I'm not sure whether anything in that module was implemented by our team. Shouldn't this be moved to some other place and evaluated by someone else? Milane, Petre B.?
Milane, please evaluate the bug. In case the bug is in XSLT template for Visual Web project type assign the bug to somebody from visual web team.
Yes, I got it. Though, the wsimport/wsgen in classical Web Application works correctly, the wsimport/wsgen in Visual Web Appication didn't apply the endorsed mechanism for jax-ws APIs. Please, apply the changes that were made in web/project : 1. add jaxws.endorsed.dir property to private.properties The property should point to directory with jax-ws 2.1 API jars (netbeans551_home/ide7/modules/ext/jaxws21/api) 2. add xendorsed="true" for wsimport ("wsimport-client-XYZ" target) 3. add xendorsed="true" and <jvmarg value="-Djava.endorsed.dirs=${jaxws.endorsed.dir}"/> for wsgen ("wsgen-XYZ-nonJSR109" target) 4. add the following line to "-init-macrodef-javac" target : <compilerarg line="-Djava.endorsed.dirs='${jaxws.endorsed.dir}'"/>
The bug not applied to NetBeans 6.0.
Passing to the visual web project type owner.
There is no plan to release patch for VWP 5.5.1. And this is fixed in NetBeans 6.0 that we are now focused on. As I known from the management team, we will not fix it in VWP 5.5.1. We will ask users to use NetBeans 6.0 instead. BTW, VWP 5.5 uses exactly the same copy of build-impl.xml as NetBeans web project. I guess NetBeans 5.5 web project should have the same issue.
You are right NB 5.5 web project has same issue but the bug is fixed in NB 5.5.1 web project.