Watch, Follow, &
Connect with Us

Please visit our new home

Public Report
Report From: JBuilder 2007/Migration Issues    [ Add a report in this area ]  
Report #:  47213   Status: Open
visual editor fails to render classes that worked in earlier versions
Project:  JBuilder 2007 Build #:  v20061116_0221
Version:    2007 1.0 Submitted By:   Byron Jones
Report Type:  Basic functionality failure Date Reported:  6/7/2007 11:48:41 PM
Severity:    Serious / Highly visible problem Last Updated: 3/20/2012 2:24:39 AM
Platform:    All versions Internal Tracking #:   2913
Resolution: None (Resolution Comments) Resolved in Build: : None
Duplicate of:  None
Voting and Rating
Overall Rating: (2 Total Ratings)
5.00 out of 5
Total Votes: None
we have a largish gui java application that has been developed over many years.

the visual editor worked in all versions of jbuilder prior to 2007.  however 2007 gives us a collection of problems and error messages.

many components are not positioned correctly; the object hierarchy is not recognised.  in one case in particular there's two buttons on a panel, declared and added identically within a few lines of code from each other.  one is positioned within the frame, the other is not.

frequently stuck on "loading".  unable to determine if it's due to a complicated form, or if it has crashed.  i can't afford to wait 5 minutes for jbuilder to open an editor.

older jbuilder versions were also a lot more tolerant of problems (especially when it comes to very complex designs).

error messages:

paneText: org.eclipse.jem.internal.proxy.initParser.tree.NoExpressionValueException(Proxy id:275)

get this one a lot

java.lang.NoSuchMethodException(gui.sys.SysReportPrintDialog.<init> (
generator gui.sys.SysReportPrintDialog

init() doesn't exist, however jbInit() does.  there's no reference to init() in the class.

java.lang.IllegalStateException(IWAV0190E No Bean instantiated for some reason.)
java.lang.NullPointerException(public void,int))

my favourite .. "for some reason".

columnTitle: java.lang.IllegalArgumentException(IWAV0177E Expression "columnTitles" is too complicated. - columnTitles)

this also happens a lot.  earlier jbuilders dealt with it ok.

this gui.ed.PmiAdmissionEd

items: org.eclipse.jem.internal.proxy.common.AmbiguousMethodException(javax.swing.JMenuItem)
A previous error prevented bean from being created.
menuParent javax.swing.JMenu

i would like to see much better error reporting when the visual editor fails.  ideally i'd like to be able to drop into debug mode within the visual editor so i can diagnose why it's so unhappy.

another large problem we have is there's no way to tell the visual editor to ignore methods and/or blocks of code.

for example:

we have a class with a cleanup() method that is only called from external classes.  for reasons unknown the cleanup() method sets the buttons, etc to null.  the visual editor throws null pointer exceptions with this method in place -- comment out the null assignments and it's ok(ish).

we also have a lot of classes that add components dynamically at run-time (outside of the constructor).  the visual editor see these components being created and trys to render them (and fails).

in both cases i'd like to be able to flag to the visual editor to ignore the assignments when trying to reverse engineer the visual design from the code.

Steps to Reproduce:

Steve Casselman at 10/12/2007 3:59:02 PM -
I had this same problem...

In my jbInit I had

contentPane = (JPanel) this.getContentPane();

Now I have

contentPane = (JPanel) getContentPane();

and it works...


Server Response from: ETNACODE01