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 7885 - Fatal Error: unable to locate java.lang in classpath during parsing
Summary: Fatal Error: unable to locate java.lang in classpath during parsing
Status: CLOSED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 3.x
Hardware: Other Windows 3.1/NT
: P4 normal (vote)
Assignee: issues@platform
URL: Radek.Matous@netbeans.com
Keywords:
Depends on:
Blocks:
 
Reported: 2000-10-12 10:26 UTC by Jan Chalupa
Modified: 2007-09-26 09:14 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Log file with exception stack-traces (5.59 KB, text/plain)
2001-07-20 20:46 UTC, Jan Chalupa 		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 Jan Chalupa 2000-10-12 10:26:25 UTC 
1. Unzipped the fresh NB-dev-45 build.
2. Started it up using runide.exe w/ netbeans.debug.exceptions=true
3. Selected the Development:examples.advanced.MemoryView node
4. Exception stack-trace appeared on the console (see the attachment) and the
node icon was marked with the "red cross" i.e. non-parseable
5. Clicked on the examples.texteditor.Ted node with the same results
6. Opened the files and closed them without saving. Red crosses disappeared.
Comment 1 Jan Chalupa 2000-10-12 10:29:59 UTC 
Created attachment 191 [details]
Log file with exception stack-traces
Comment 2 Svata Dedic 2000-10-13 09:36:59 UTC 
[Builds 44,45] The parser crates a JARFilesystem for each jar/zip file it tries
to work with, then uses its methods to search through the archive.
According to the debug messages, the JarFS for rt.jar *is* created before this
error is produced, so the findResource() called after the JarFS is created and
initialized probably produces incorrect results.
Comment 3 Jesse Glick 2000-10-13 14:25:59 UTC 
Probably a side-effect of apparent JarFileSystem bug.

*** This bug has been marked as a duplicate of 7892 ***
Comment 4 Quality Engineering 2003-07-01 13:11:58 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.
Comment 5 Quality Engineering 2003-07-01 13:16:03 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.