This bug is identical to RT-35957, which is marked as fixed, but it is still happening. I'm raising a new bug instead of re-opening that other one because I read somewhere that that's how you guys prefer to handle situations like this.

Issue RT-35957 was fixed by changing a bunch of Logging.getLogger().warning() calls in the Bindings class into Logging.getLogger().fine() calls. Unfortunately, a lot of relevant .warning() calls were missed.

For an example, see ObjectBinding<E> valueAt(final ObservableList<E> op, final int index). The computeValue() method still spits out a nasty looking stack trace and error message to the console whenever the index is "behind" the ObservableList. But that's not an error in any way; the documentation for the method says "The ObjectBinding will contain null if the index points behind the ObservableList."

The same problem occurs in all of the other Bindings.*ValueAt() methods, and maybe other methods in Bindings too. In some methods there are some calls to that were converted from warning() to fine(), but even these calls are not actually handling the situation where the index is "behind" the ObservableList.

As a result, the problem that exists in RT-35957 still exists: I can't use Bindings.*ValueAt() methods without getting a bunch of spurious stack traces to the console.