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 253940 - IllegalArgumentException: object is not an instance of declaring class
Summary: IllegalArgumentException: object is not an instance of declaring class
Status: RESOLVED WORKSFORME
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-29 10:39 UTC by josse173
Modified: 2016-01-22 16:58 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 218838

Attachments
stacktrace (3.14 KB, text/plain)
2015-07-29 10:39 UTC, josse173 		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 josse173 2015-07-29 10:39:08 UTC 
This bug was originally marked as duplicate of bug 168026, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.51-b03, Java(TM) SE Runtime Environment, 1.8.0_51-b16
OS: Windows 7

User Comments:
josse173: none




Stacktrace: 
java.lang.IllegalArgumentException: object is not an instance of declaring class
   at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:0)
   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:497)
   at org.netbeans.modules.form.RADProperty.getTargetValue(RADProperty.java:122)
   at org.netbeans.modules.form.FormProperty.checkCurrentValue(FormProperty.java:1011)
Comment 1 josse173 2015-07-29 10:39:10 UTC 
Created attachment 155003 [details]
stacktrace
Comment 2 Tomas Pavek 2015-09-11 16:42:15 UTC 
Similar to bug 243356. Involves custom components and it looks like if the bean instance is of a different class than remembered in method object in property. It is unclear how this might happen - the bean class is loaded once and kept in the component, then used for creating the instance and properties. We'd need exact steps to reproduce so this could be debugged.
Comment 3 Tomas Pavek 2016-01-22 16:58:22 UTC 
Need steps to reproduce this.