I would like to use Hibernate with the jgoodies swing binding API.

The jgoodies binding API requires all your POJO classes to extend their abstract class com/jgoodies/binding/beans/Model. This abstract class doesn't have any fields that are related to the fields in the concrete POJO classes or fields in any database tables.

Does anyone have any suggestions how to map the fields in the POJOs that extend the jgoodies Model class? Like maybe some way to ignore the Model class all together?

Does anyone have any experience using the jgoodies binding API with Hibernate?

Does anyone have any experience with using some other swing binding API with Hibernate?

TIA for any clues/suggestions!


Hibernate version:
Hibernate 2.1.7

Full stack trace of any exception that occurs:
java.lang.NoClassDefFoundError: com/jgoodies/binding/beans/Model
(more...)

try spring RCP (www.springframework.org)

regards

I don't really see your problem.
What you have is your domain model extending a base class Model. Just ignore that information and map you "real" domain model classes (and pout the Model class in your CP).
Hibernate doesn't care about your superclasses in the xml mapping.

emmanuel,

You where absolutely correct. The issue was yet another classpath issue.

I use JBuilder and I forgot that it doesn't build an updated classpath unless you close and reopen the run window after making changes to the classpath.

Thanks for pointing out the obvious!

Hi SwingCoder,

AFAIK it should not be necessary/recommended to let your domain objects extend the ValueModel in jgoodies binding. What you do insted is to have standard javabean PropertyChangeEvents for your domainmodel and uses the BeanAdapter/PropertyAdapter to manage all the other stuff.

just my 2 cents
max

Swing Coder,

Your POJOs don't need to extends Model, however, your POJOs DO need to support bound properties using JavaBean conventions. What JGoodies looks for when binding your POJOs to components, is these 2 methods:

addPropertyChangeListener
removePropertyChangeListener

Additionally, your setter methods should fire property change events when the values change.

I too was faced with a similar problem and I did not want to have to update 29 classes to support bound propertie, nor did I see much value in writing a proxy class to support the bound properties requirement. So, using JBoss AOP, I created an aspect that would do it for me. I have a somewhat lengthly post on my blog on the topic here:

http://www.damnhandy.com/?page_id=17

So far, it works great but still needs a few tweaks here and there. Hope this helps.

Ryan-