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 106904 - Creator Project with Web Service Still shows Unresolved References after Importing project
Summary: Creator Project with Web Service Still shows Unresolved References after Impo...
Status: VERIFIED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: visualweb (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Quy Nguyen
URL:
Keywords:
Depends on: 110040
Blocks:
  Show dependency tree
 
Reported: 2007-06-16 02:29 UTC by Yousuf Haider
Modified: 2007-11-05 20:28 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Web Service Support Deprecated (64.82 KB, image/jpeg)
2007-06-16 02:30 UTC, Yousuf Haider 		Details
Unresolved References (28.05 KB, image/jpeg)
2007-06-16 02:31 UTC, Yousuf Haider 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Haider 2007-06-16 02:29:57 UTC 
Steps to reproduce:
1. Create a project in Creator 2 with a simple dropdown list bound to a webservice.
2. Import the the project in NB6. 

The IDE will still show unresolved library refernces for "WEBSVC_SUPPORT_LIB", even though project will deploy and run
without any problems. This is because the 'Web Service Support' library in NB 6 references jars that are no longer
available. They are all marked as red in the library manager. ( See attached images)

To remove the red badge from the project remove the 'Web Service Support' library from:
Project Properties->Libraries.
Project Properties->Building->Packaging.
Comment 1 Yousuf Haider 2007-06-16 02:30:42 UTC 
Created attachment 43829 [details]
Web Service Support Deprecated
Comment 2 Yousuf Haider 2007-06-16 02:31:18 UTC 
Created attachment 43830 [details]
Unresolved References
Comment 3 Yousuf Haider 2007-06-16 23:55:46 UTC 
This was on Build: 200706150933
Comment 4 Ch Nguyen 2007-06-19 02:04:03 UTC 
This sounds similar to this issue 101642 which depends on issue 100114.

Po-Ting, any update on this?
Comment 5 Quy Nguyen 2007-06-27 21:49:39 UTC 
Reassigning to Po-ting for the requested updates.
Comment 6 _ potingwu 2007-06-27 21:55:04 UTC 
Project module already implemented the following APIs that websvc module can use for removing unresolved references if
they no longer needed:

In org.netbeans.modules.visualweb.project.jsf.api.JsfProjectUtils.java

   public static boolean removeLibraryReferences(Project project, Library[] libraries, String type) throws IOException;

   public static boolean removeRootReferences(Project project, URL[] rootFiles, String type) throws IOException;

If your libraries are not 'just' but for both Compile and Package (i.e., Libraries with the packaging check box
enabled), then use the method without 'type':

   public static boolean removeLibraryReferences(Project project, Library[] libraries) throws IOException;

   public static boolean removeRootReferences(Project project, URL[] rootFiles) throws IOException;
Comment 7 Quy Nguyen 2007-06-28 00:51:21 UTC 
I don't understand how these APIs help during project import.  From the email discussion:

  The mechanism of importing (actually Opening) an old project from the new IDE is:
   - the IDE does NOT touch or change the contents of the project
   - the IDE setup an environment to handle backwards compatibility
Comment 8 _ potingwu 2007-06-28 01:35:07 UTC 
Edwin uses these APIs to remove old libraries that are no longer needed for complib. From Chau's comments that she said
websvc has the same issue and would like to do the same scheme. If not, then websvc can have anything to fix.
Comment 9 Quy Nguyen 2007-07-17 08:51:50 UTC 
The library jars no longer exist and is not needed for projects that use glassfish since this server contains the
necessary JAX-RPC and JAX-WS classes.
Comment 10 Quy Nguyen 2007-08-14 19:22:52 UTC 
Since the related complib and NB API addition issues are both P3, downgrading this as well.
Comment 11 Quy Nguyen 2007-11-01 00:08:31 UTC 
Fixed in trunk.  This uses the api provided in 110040 and is similar to the fix used in complib migration.

Checking in resources/layer.xml;
/cvs/visualweb/project/jsf/src/org/netbeans/modules/visualweb/project/jsf/resources/layer.xml,v  <--  layer.xml
new revision: 1.33; previous revision: 1.32
done
RCS file:
/cvs/visualweb/project/jsf/src/org/netbeans/modules/visualweb/project/jsf/libraries/WebServicesBrokenLibraryRefFilterProvider.java,v
done
Checking in libraries/WebServicesBrokenLibraryRefFilterProvider.java;
/cvs/visualweb/project/jsf/src/org/netbeans/modules/visualweb/project/jsf/libraries/WebServicesBrokenLibraryRefFilterProvider.java,v
 <--  WebServicesBrokenLibraryRefFilterProvider.java
initial revision: 1.1
done
Comment 12 Yousuf Haider 2007-11-05 20:28:43 UTC 
verified fix on :

Product Version: NetBeans IDE Dev (Build 200711050000)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)