WindowBuilder internal error

[aschilling]

Hello!

we updated to the new version of WB (7.0) as it now features a lot of things we use daily. however, we encountered that it's not able to open nearly any of our dialogs in our application anymore, most of them because of a NullPointerException. The cause is easy to spot: most of our dialogs access logic from our business layer, which is a different plugin. So retrieving objects from the business layer of course returns NULL (as the plugin does not exist when WB parses the gui code) and calling any methods from them results in the NPE.
The older versions didn't have this kind of problem, it seemed to accept just everything except for some really rare cases where it also wasn't able to parse the code.
Any ideas on how to solve this issue? It's really important for us, because at the moment we can not use the new version at all, which is a pity as it looks really, really promising.

best regards,

Andreas

[Eric Clayberg]

The the NPE triggered in the code for the dialog or for a custom component used in the dialog?

Does a null check or Beans.isDesignTime() check fix it?

It would really help to see an actual test case here.