Watch, Follow, &
Connect with Us
Public Report
Report From: JBuilder/Designers/UI Designer    [ Add a report in this area ]  
Report #:  9476   Status: Closed
JBuilder 2005: major UI-Designer Bug using own UI-Components
Project:  JBuilder Build #:
Version:    12 Submitted By:   Mike Wilhelm
Report Type:  Basic functionality failure Date Reported:  10/28/2004 2:58:05 AM
Severity:    Serious / Highly visible problem Last Updated: 3/20/2012 2:24:39 AM
Platform:    All versions Internal Tracking #:   220140
Resolution: Fixed (Resolution Comments) Resolved in Build: :
Duplicate of:  None
Voting and Rating
Overall Rating: (15 Total Ratings)
5.00 out of 5
Total Votes: 73
I get the following warning, if I use an own UI Component with some additional properties in the UI Designer of JBuilder 2005:

Warning: cannot set "myValue" property  for myField1 -- java.lang.IllegalArgumentException: object is not an instance of declaring class
Steps to Reproduce:
I have a class MyField which extends JdbTextField with a property myValue.
I also have a BeanInfo for this class to use it in the palette of the UI Designer.
This classes are packed in a Jar-File (MyGui.jar).

Another project uses this library to design panels with MyField.
After starting JBuilder, I can add new MyField-Components and edit the property "myValue" in the property-Editor of the UI Designer.
Up to this point everything works fine.
But if I compile the project (Make Project) and reopen the panel class (close the UI Designer, close the panel class "MyPanel" and then open the UI Designer again with the panel class)
then I can't edit the property "myValue". The designer shows the warning:

Warning: cannot set "myValue" property  for myField1 -- java.lang.IllegalArgumentException: object is not an instance of declaring class

The other properties, which came from the super classes, are editable.

The only way to edit the property "myValue" is to restart the JBuilder.

See attachment for the example projects.



Mike Wilhelm at 12/2/2004 1:16:56 AM -
The bug is getting bigger with Update 1 (Build
Now I get the warning if I change from Designer to Editor and back to Designer and then edit an own property. Before Update 1 I got the warning only after compiling the project.

It's unpossible to work with this bug!!!!

George Willard at 12/3/2004 6:23:34 AM -
My development team has been experiencing the same problem when trying to set ILOG JViews 6.0 bean properties.  This really makes using the UI-Designer impossible for us to use with ILOG components.  I tried applying Update 1, and as Mike Wilhelm observed - it did not help.

George Willard at 12/21/2004 6:31:55 AM -
Is anyone at Borland looking at this reported bug?

George Willard at 12/30/2004 2:30:47 PM -
Why even bother entering information into this system?

abubakar saddique at 2/8/2005 3:04:11 AM -
Any body  can find the way to use jbuilderX designer with jbuilder2005........removing the compatibility bugs of 2005 designer , and taking advantage of its new fetures

Dirk Ollmann at 5/27/2005 8:40:57 PM -
The only thing that made switch to JBuilder 2005 was JDK 1.5 support.
The only thing that made me still use JBuilder was its good Gui-designer.

So what are my Options ?

1. Stay with the old JDK's and old JBuilder
2. Switch to Netbeans
3. Do Gui by hand and use IDEA

JBuilder Team !!!  Please keep the old good Gui-Designer or you lose the last customers that pay your salery !!!!!!

Sergey Ivanov at 3/1/2005 3:20:26 PM -
I would definitely vote for that!

abubakar saddique at 2/8/2005 3:05:28 AM -

J. Dannenberg at 2/10/2005 1:11:51 AM -
This product is becoming more and more annoying. We paid a lot of money for 5 enterprise licenses and since patch 1 things have gotten worse. I am no longer able to parse my existing dialogs (which worked more or less ok before patch 1).

Markus Schlegel at 7/28/2005 5:02:32 AM -
We too upgraded to JBuilder because of its good GUI-Designer in JB7. With these bugs, there is no reason to stay with JBuilder...

So Please fix those Crash-Bugs or go back to the old Designer (but it has to work with 1.5 code)!

Mikael Grev Grev at 8/11/2005 11:32:37 AM -
Is this bug ever going to be fixed???

Server Response from: ETNACODE01