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 61963 - javax.jmi.reflect.InvalidObjectException and broken code after use of autocorrect
Summary: javax.jmi.reflect.InvalidObjectException and broken code after use of autocor...
Status: VERIFIED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Javadoc (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jan Pokorsky
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-08-09 10:33 UTC by Lukas Hasik
Modified: 2006-09-14 10:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
javax.jmi.reflect.InvalidObjectException: Object with MOFID 8DDC1CA5-08B6-11DA-97D6-48132AE3AA77:00000000000007B8 no longer exists. (4.43 KB, text/plain)
2005-08-09 10:33 UTC, Lukas Hasik 		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 Lukas Hasik 2005-08-09 10:33:11 UTC 
nb42-0508080823 + me050808, jdk1.5.0_04

I had a HelloMidlet and I wanted to "Auto Correct" method destroyApp with "Auto
Comment Tool" after press the "Auto Correct" button I received
javax.jmi.reflect.InvalidObjectException (in attachment) and the source code was
broken to :
   public void destroyApp(boolean uncondi    /**
     * 
     * @param unconditional 
     */
tional) {
    }
Comment 1 Lukas Hasik 2005-08-09 10:33:47 UTC 
Created attachment 23594 [details]
javax.jmi.reflect.InvalidObjectException: Object with MOFID 8DDC1CA5-08B6-11DA-97D6-48132AE3AA77:00000000000007B8 no longer exists.
Comment 2 Jan Pokorsky 2005-08-15 15:12:43 UTC 
It looks like some problem with offset validity of a JMI element. Passing to
java/javacore for evaluation since I am not aware of any change in javadoc
module that could cause this.
Comment 3 Tomas Hurka 2005-08-16 15:50:03 UTC 
There is missing check for validity of element at ParamTag.java:72 
In addition to that code in JavaDocEditorPanel.java:219-221 should run in transaction and should check 
validity of element.getSrcElement() at the beginning of such transaction.
Comment 4 Jan Pokorsky 2005-08-23 15:25:26 UTC 
Most likely caused by an async task (CVS?). I'll try to tweak the javadoc module
to cope with this issue. Nevertheless it is a bug of JMI impl to break the
source file as shown in the first comment.
Comment 5 Jan Pokorsky 2005-09-20 17:29:36 UTC 
fixed in

/cvs/javadoc/src/org/netbeans/modules/javadoc/comments/AutoCommentPanel.java
new revision: 1.59; previous revision: 1.58
/cvs/javadoc/src/org/netbeans/modules/javadoc/comments/AutoCommenter.java
new revision: 1.46; previous revision: 1.45
/cvs/javadoc/src/org/netbeans/modules/javadoc/comments/Bundle.properties
new revision: 1.40; previous revision: 1.39
/cvs/javadoc/src/org/netbeans/modules/javadoc/comments/JavaDocEditorPanel.java
new revision: 1.55; previous revision: 1.54

User is notified about external changes now. The customizer also checks validity
of each element before propagating changes to the model.
Comment 6 Lukas Hasik 2006-09-14 10:32:48 UTC 
v