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 50903 - IOE in MDR when expanding class node in WAR file.
Summary: IOE in MDR when expanding class node in WAR file.
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Daniel Prusa
URL:
Keywords:
Depends on:
Blocks: 49959
  Show dependency tree
 
Reported: 2004-10-27 13:42 UTC by Jiri Kovalsky
Modified: 2006-03-24 09:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Sample project where described bug can be reproduced. (8.89 KB, application/octet-stream)
2004-10-27 13:43 UTC, Jiri Kovalsky
Details
IOE thrown when rapidly expanding class node in WAR file. (7.37 KB, patch)
2004-10-27 13:45 UTC, Jiri Kovalsky
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2004-10-27 13:42:32 UTC
Development build #200410261800 of NetBeans 4.0
Windows XP, JDK 1.5 build #64

Description:
============
Fast users will always face exceptions when they
decide to explore WAR files without certain level
of patience. It happens when class is being parsed
for the first time and user continues to expand it
to see e.g. its fields.

Steps to reproduce:
===================
1. Launch IDE with empty userdir.
2. Create new WebApps project described in
http://www.netbeans.org/kb/articles/quickstart-webapps-40.html
or simply unzip the project I have attached.
3. Press F11 to build it.
4. Switch to Files view and expand the following
structure:
"HelloWeb|dist|HelloWeb.war|WEB-INF|classes|org|me"
to see "hello" package node.
5. Now you must be really fast. Expand "hello"
node and without hesitation expand
"NameHandler.class" and its "NameHandler" subnode
too before parsing of the class is finished.
6. After a while the IDE throws below attached
exceptions.

Note:
=====
Furthermore, the tree structure is corrupted
because it displays only:

- hello
   - NameHandler.class
      - NameHandler
         + Bean Patterns
Comment 1 Jiri Kovalsky 2004-10-27 13:43:53 UTC
Created attachment 18561 [details]
Sample project where described bug can be reproduced.
Comment 2 Jiri Kovalsky 2004-10-27 13:45:14 UTC
Created attachment 18562 [details]
IOE thrown when rapidly expanding class node in WAR file.
Comment 3 Martin Matula 2004-10-27 13:48:38 UTC
The problem is in clazz module. Dan will look at it.
Comment 4 Daniel Prusa 2004-10-29 18:08:22 UTC
Fixed.

Checking in ClassElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/ClassElementImpl.java,v  <--
 ClassElementImpl.java
new revision: 1.44; previous revision: 1.43
done
Checking in ConstructorElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/ConstructorElementImpl.java,v
 <--  ConstructorElementImpl.java
new revision: 1.26; previous revision: 1.25
done
Checking in FieldElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/FieldElementImpl.java,v  <--
 FieldElementImpl.java
new revision: 1.17; previous revision: 1.16
done
Checking in MemberElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/MemberElementImpl.java,v 
<--  MemberElementImpl.java
new revision: 1.33; previous revision: 1.32
done
Checking in MethodElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/MethodElementImpl.java,v 
<--  MethodElementImpl.java
new revision: 1.16; previous revision: 1.15
done
Checking in SourceElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/SourceElementImpl.java,v 
<--  SourceElementImpl.java
new revision: 1.35; previous revision: 1.34
done
Comment 5 Jiri Kovalsky 2004-11-01 15:02:58 UTC
Can you please Dane integrate the fix into QBE200410261800 branch ? 
This bug is a Q-build stopper. Thanks.
Comment 6 Martin Matula 2004-11-02 09:19:36 UTC
Done.

Checking in src/org/netbeans/modules/clazz/ClassElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/ClassElementImpl.java,v  <--
 ClassElementImpl.java
new revision: 1.42.18.1; previous revision: 1.42
done
Checking in src/org/netbeans/modules/clazz/ConstructorElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/ConstructorElementImpl.java,v
 <--  ConstructorElementImpl.java
new revision: 1.24.20.1; previous revision: 1.24
done
Checking in src/org/netbeans/modules/clazz/ElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/ElementImpl.java,v  <-- 
ElementImpl.java
new revision: 1.17.4.1; previous revision: 1.17
done
Checking in src/org/netbeans/modules/clazz/FieldElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/FieldElementImpl.java,v  <--
 FieldElementImpl.java
new revision: 1.15.20.1; previous revision: 1.15
done
Checking in src/org/netbeans/modules/clazz/MemberElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/MemberElementImpl.java,v 
<--  MemberElementImpl.java
new revision: 1.31.4.1; previous revision: 1.31
done
Checking in src/org/netbeans/modules/clazz/MethodElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/MethodElementImpl.java,v 
<--  MethodElementImpl.java
new revision: 1.14.20.1; previous revision: 1.14
done
Checking in src/org/netbeans/modules/clazz/SourceElementImpl.java;
/cvs/clazz/src/org/netbeans/modules/clazz/SourceElementImpl.java,v 
<--  SourceElementImpl.java
new revision: 1.33.4.1; previous revision: 1.33
done
Comment 7 Jiri Kovalsky 2005-03-24 14:35:54 UTC
Yes, it seems to be really fixed in development build #200503232205 of NetBeans 4.1.