ansaurus

Question

Answer 1

+2 A:

You get an ExceptionInInitializerError if something goes wrong in the static initializer block.

class C
{
  static
  {
     // if something does wrong -> ExceptionInInitializerError
  }
}

Because static variables are initialized in static blocks there are a source of these errors too. An example:

class C
{
  static int v = D.foo();
}

=>

class C
{
  static int v;

  static
  {
    v = D.foo();
  }
}

So if foo() goes wild, you get a ExceptionInInitializerError.

Christian Ullenboom 2010-07-30 22:33:02

I don't understand. It seems to be wrapped up in code which I cannot touch.

Adam Outler 2010-07-30 23:24:42

@Adam - I assume you mean the `org.jdesktop.beansbinding.*` code. You can at least look at that code, set breakpoints in it, single step, etc.

Stephen C 2010-07-31 01:08:05

Answer 2

+1 A:

@Christian Ullenboom' explanation is correct.

I'm surmising that the OBD2nerForm code you posted is a static initializer block and that it is all generated. Based on that and on the stack trace, it seems likely that generated code is tripping up because it has found some component of your form that doesn't have the type that it is expecting.

I'd do the following to try and diagnose this:

Google for reports of similar problems with NetBeans generated forms.
If you are running an old version of NetBeans, scan through the "bugs fixed" pages for more recent releases. Or just upgrade try a newer release anyway to see if that fixes the problem.
Try cutting bits out of the form design until the problem "goes away" ... and try to figure out what the real cause is that way.
Run the application under a debugger to figure out what is being (incorrectly) type cast as what. Just knowing the class names may help. And looking at the instance variables of the objects may reveal more; e.g. which specific form component is causing the problem.

My suspicion is that the root cause is a combination of something a bit unusual (or incorrect) with your form design, and bugs in the NetBeans form generator that is not coping with your form. If you can figure it out, a workaround may reveal itself.

Stephen C 2010-07-31 01:05:13

how did you figure out that the problem was improper casting?

Adam Outler 2010-07-31 01:14:30

Oh... class cast exception. thanks!

Adam Outler 2010-07-31 01:14:57

@Adam - it is amazing what you can figure out by looking carefully at the evidence you already have :-)

Stephen C 2010-07-31 01:18:19

Answer 3

A:

I found that I had bound jFormattedCheckBox1.foreground to jCheckBox1[${selected}].... this was the problem. Thank you for your help.

It seems that a color should not be able to be bound to a boolean. I guess bindings are an "advance feature"?

I found the problem by deleting all of the controls, then running, then undoing and then deleting one at a time. When I found the offending control, i examined the properties.

Adam Outler 2010-07-31 01:11:00

Answer 4

A:

Thanks for the tip! I had the same problem here =D

Leonardo Kasperavicius 2010-09-08 02:36:38

ansaurus

tags:

views:

answers:

exception in initializer error

related questions