Cool! Who knew.
Still, in OFBiz I don't even have to write the Person class. Its already
there. I don't even need to find a database and load the schema. All
that happens for me transparently. If I let it.
Ruth
huang.mi...@gmail.com wrote:
On Fri, 2010-02-26 at 09:06 -0500, Ruth Hoffman wrote:
How about the seamless and transparent database support by way of the
Entity Engine? If you want to develop an application or implement
ERP,
then you don't need to worry about the database. You don't need to
stress over whether to use Hiberanate or JDO or native SQL or
whatever
the latest database technology fad happens to be. The EE is here, its
proven and best of all I don't have to deal with it! I can get on to
developing my applications.
I'm sorry to say this is also a Grails built in feature. Grails can
simply write the domain model as a Groovy bean. Just give a really
feature rich and yet simple example:
class Person {
String pid
String firstName
String lastName
BigDecimal salary
Date birthday
String notes
static constraints = {
pid(blank:false, unique: true)
firstName(blank:false)
lastName(blank:false)
notes(blank:true, nullable:true, maxSize:5000)
}
}
This is all the code you need to write to define a entity model, then
CRUD methods, nearly every possible simple finder methods (up to 2
fields composite criteria), auto SQL table DML maintenance with re-sync
ability on every time you change the model, are all ready for you. You
can also add some constraints for validation logic and storage hint
(most have default value so you don't need to code for every one), just
declaration, that's enough.
Constraints check are available on presentation/service/persistence
tier. Quite like OFBIZ entity engine, but more coding efficient, isn't
it?
And the sophisticated model relation management and auto
optimized-locking mechanism, which seems to be a weak point of OFBIZ
entity engine.
Or all the framework tools that have been integrated and proven.
Everything from Internationalization and localization support to XML
document handling. (Personally, I'm tired of having to integrate XML
parsers every time I need that functionality in an application.)
XML process, persistence, i18n support, are all readily built in Grails
platform.
