Model Architectural Question

[GaryKopp]

Hello again, Andres. I have a general question -- let me know if there is somewhere else I should ask things like this.

Quoting from Griffon in Action, where Griffon "models" are likened to Smalltalk application models rather than domain models (emphasis added):

"All this work in domain models on the web has resulted in some great objectrelational
mapping (ORM) libraries and database façade libraries that interact with
plain old Java objects (POJOs). This effort isn’t lost to a Griffon application, because
all the objects needed to access these domain models can be placed directly in the
model class and accessed by the view and the controller. These database-driven
domain models, however, lie outside the scope of this book."

My target application is for the desktop, not the web (so Grails is out), but I still need a Hibernate-based domain model backend hooked into the Griffon application. Can you suggest some sources for ideas on the best way to integrate domain models into Griffon application models, or perhaps some examples (outside the scope of your book :-)? There are obviously many ways to implement this, and I just don't want to reinvent the wheel and wondering if there are tried and true methods (patterns) for this in the Griffon world.