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.
Created attachment 150382 [details] example project Steps to reproduce: - Configure Java Platform "JDK 1.6" (I am using jdk1.6.0_45, win 32bit) - Open attached example project - Build project Result: Project builds fine using Maven 3.0.5 (and JDK 1.6) Problem: Test_Service.java is marked with a red exclamation mark, because Netbeans cannot resolve constructor Service(URL, QName, WebServiceFeature[]) in lines 29, 37 and 45. (Possible) Cause: Netbeans uses Service.java from rt.jar instead of the one in jaxws-api-2.2.9.jar which is correctly listed under "Java Dependencies" and has the corresponding three-elements-constructor. Info: The example project is a simplified version from an actual service generated by jaxws-maven-plugin 2.5 (metro wsimport).
Created attachment 150383 [details] Screenshot of editor after successful build
Created attachment 150386 [details] example project removed some unnecessary files contained in the first version
could not reproduce in current dev build - NetBeans IDE Dev (Build 20141114-6d69c6f9fae6) niether in 8.0.1 after opening Test_Service was marked broken, but after compiling everything got fine what NB version do you use? are you able to reproduce with a dev build? thanks
From my NB installation, Help-About: Product Version: NetBeans IDE 8.0.1 (Build 201408251540) Updates: NetBeans IDE is updated to version NetBeans 8.0.1 Patch 1.1 Java: 1.7.0_55; Java HotSpot(TM) 64-Bit Server VM 24.55-b03 Runtime: Java(TM) SE Runtime Environment 1.7.0_55-b13 System: Windows 8 version 6.2 running on amd64; Cp1252; en (nb) I've tried the dev build 201411170001 which showed no issues related to this topic. However, somehow the Java Dependencies-Folder inside the project is broken in this version: It does not refresh the Java version, and the other two endorsed lib are not shown by its names, but a more than 20 digit long hex string. I also let another colleague try the example project. He had the same issues with NB 8.0.1 but with the 64bit version of jdk 1.6. With the 32 bit version of jdk 1.6 it first worked, but after some switching between 32 and 64 bit, the problem also occurred with 32 bit. Hence, I've tried the 64bit version of jdk 1.6 on my computer, to see if it makes any difference, and there it works. Since the behaviour is rather arbitrary, I suspect that it might be a caching issue. The dev version is a fresh install (nothing imported from 8.0.1). And after I deleted the cache in my 8.0.1 version, it works again (with both 32 and 64 bit jdk). Let's see, how long...