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 117052 - package not found
Summary: package not found
Status: RESOLVED DUPLICATE of bug 112736
Alias: None
Product: webservices
Classification: Unclassified
Component: Client (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milan Kuchtiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-28 17:15 UTC by hoodieboy
Modified: 2007-10-02 01:55 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
HELLOWEBSERVICE AND HELLOWEBSERVICE CLIENT PROJECTS WITH PACKAGE NOT FOUND ISSUE (3.40 MB, application/octet-stream)
2007-09-28 17:22 UTC, hoodieboy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description hoodieboy 2007-09-28 17:15:47 UTC
http://www.javapassion.com/handsonlabs/4353_wshelloworld.zip

This is a link to webservice class exercise.  When I follow instruction for webservice all is ok.  When I follow
instructions for webservice client things get funny.  The webserviceclient compiles and runs ok, but the editor tells me
that the "mypackage" package is not found and shows a red exclamation with "mypackage" underlined in red as if an error
exists. I think it is red, I'm color-blind.  But the message shown when cursor is placed over exclamation is package not
found.  But the package is there and the application works just fine. 

Running the following setup:
Product Version: NetBeans IDE 6.0 Beta 1 (Build 200709141330) Java: 1.5.0_12; Java HotSpot(TM) Client VM 1.5.0_12-b04
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb) Userdir: C:\Documents and
Settings\jerome\.netbeans\6.0beta1
Comment 1 hoodieboy 2007-09-28 17:22:33 UTC
Created attachment 49753 [details]
HELLOWEBSERVICE AND HELLOWEBSERVICE CLIENT PROJECTS WITH PACKAGE NOT FOUND ISSUE
Comment 2 Lukas Jungmann 2007-10-02 01:55:17 UTC
Seems like a duplicate of already filed issue, which has been fixed recently...

*** This issue has been marked as a duplicate of 112736 ***