I do what Lars recommended and it work!
I did a compare of the file before/after and the only diff is the number of that properties: org.objectstyle.wolips.componenteditor.sashWeights=805,194 so you can simply remove that properties and it will work again.
From what I looked at, the fix from Frank Cobia was commenting out the line culprit. I did not looked enough to conclude if it was a real fix, or a mere workaround for now.
jfv
Objet : Workaround for annoying NPE bug when opening WOComponent Editor
Date : 22 octobre 2013 06:49:28 HAE
Hi List,
I don't know if you're also affected by this, but all my coworkers experience from time to time those annoying cascades of NPEs when opening a WOComponent in the WOComponent Editor on Eclipse Kepler (4.3) and WOLips 4.3 which, once they're happening, never go away by themselves.
Now my coworker Tommy has found a workaround for this:
- shutdown Eclipse
- delete .metadata/.plugins/org.eclipse.core.runtime/.settings/org.objectstyle.wolips.wodclipse.core.prefs from your workspace
- restart Eclipse
-> everything should work fine now. When the problem recurs just delete this file again.
I hope this was helpful to some of you.
cheers,
Lars
Le 2014-02-04 à 09:05, Hugi Thordarson < email@hidden> a écrit : I’m getting an error on 4.3 where if I open a component (the component editor), it just shows up empty and then proceeds to throw bazillion nullpointerexceptions at me.
I seem to recall having seen this before, but can’t for the life of me remember what I did to fix it. Light any bulbs for anyone?
Cheers, - hugi
3.x does the same thing... On Feb 3, 2014, at 8:47 AM, Frank Cobia < email@hidden> wrote: Unfortunately I got side tracked this weekend, so I did not get a chance to clean up the code.
However, I have not seen the issue you are describing in EOModeler. There are times when the properties panel does not populate, but you just have to click on something else and then click back. So it is just an annoyance and not a problem.
Frank
On Jan 31, 2014, at 12:22 PM, Lon Varscsak < email@hidden> wrote: There was some wonkiness in the EOModeler tool too. I vaguely remember you'd go to edit a field (like class name) and it would clear all the contents...so it was sort of impossible to work with. Did that ever get resolved?
|