Fake errors about binding errors

[maiksd]

These have been there for ages and occur often after switching branches with lots of recompiles. There is no error, but one is reported. Happens both in WOOGNL and in WOD bindings.

[nullterminated]

Can you point me to a component in wonder that is doing this for you? I've seen this happen before, but I need to find something that reproduces the error so I can work on it.

[maiksd]

I'm afraid this isn't 100% reproducible anyway. I open a component, and it's quite random if such an error gets shown or not. Sometimes it is, sometimes it isn't. If I rebuild the project, the errors often disappear, but not always. I don't use any Wonder components, and I don't even have Wonder imported in Eclipse any more, so unfortunately I can't point to any that could help. If I would create a minimal sample project, I'm sure it wouldn't occur due to the low complexity.

Right now I can't think of a better approach than a static analysis of any condition that might bring up that error message, and look out for anything that will likely occur only in bigger projects, like race conditions, concurrency issues and so on. Or randomly try the biggest components in the biggest projects you have.

Sorry I don't have anything better to offer at this point.

[nullterminated]

Keep an eye out for anything that triggers the behavior. That's probably a big clue. I've seen this too, but I can't find anything that it exhibits it at the moment.