RCP bindings vs. JGoodies bindings

[siggy]

We're looking into using a binding framework. Looking at RCP and JGoodies, they're obviously very similar. From skimming the code and forums, it looks like the primary differences are RCP enhances for Spring, adds a declarative binding selection mechanism, and adds nested bindings (bean.internalBean.bar). Is this correct? Any other important differences?

Also, in the JGoodies example the domain objects extend a JGoodies Model class to add Java bean bound properties for update notifications. Is this the recommended method in RCP as well?

john

[Kees de Kooter]

In RCP you don't need to subclass your pojos, you can bind them as is. That's a big plus for RCP I think.

[t.n.a.]

How mature is the spring databinding framework?

[Kees de Kooter]

I think the core is pretty mature. It works fine with a coding-only of swing development.

In my project we use JFormBuilder to build the windows and add some binding code later on. This was quite easy to do too for the basic controls. For comboboxes I had to make a subclass of SwingBindingFactory. But that was not difficult to do.

[jbalint]

You don't need to subclass Model for the JGoodies binding library. However, if your bean properties are not bound, any changes that happen directly to the domain object won't be updated in the view. I don't know how Spring RCP/Binding does it, but unless they have a polling thread, they can't get updates from non-bound properties either.

Jess

[Kees de Kooter]

I think you could if you use AOP. I would not be surprised if spring binding uses this.