ObservableValue: a value to-be or to-wrap-only?

Question

Hi experts,
it's a question which turned up in the other thread:
ObservableList: notification on property changes of contained elements?
as a code snippet (just for clarity, if allowed, it would extend the one or other implementing class):
public Person implements ObservableValue<Person> {
       @Override
       public Person getValue() {
            return this;
} the basic idea (Darryl's - and I'm delighted by it : - ) is to have an in-system handle for getting notified whenever any property of the object changes - the Swing equivalent would be to register a PropertyChangeListener and trigger some update independent of the propertyName.
API doc says: "is an entity that wraps a value" - taken literally, the above wouldn't be allowed .. ideas?
Thanks
Jeanette

Answer 1

Hi,
am not expert but I dig a lot with API doc.
try instead
       @Override
       public Person getValue() {
            return this;
       }this :
       @Override
       public Person getValue() {
            return get();
       }Why implementing ObservableValue while you can extend ObservableValueBase?
Api doc says :
"A convenience class for creating implementations of ObservableValue. It contains all of the infrastructure support for value invalidation- and change event notification. This implementation can handle adding and removing listeners while the observers are being notified, but it is not thread-safe."
You can read rest here http://download.oracle.com/javafx/2.0/api/javafx/beans/value/ObservableValueBase.html
Or maybe you should try extending ObjectPropertyBase class http://download.oracle.com/javafx/2.0/api/javafx/beans/property/ObjectPropertyBase.html
Both of these classes implement ObservableValue.
Hope it helps.