There is even a term for this: object-relational impedance mismatch. Of course, that is true for many other things, like object-service impedance mismatch, object-XML impedance mismatch, etc, etc. It comes down to the simple idea that modeling everything as a custom object is full of problems.
I agree Scott, this is definitely something worth researching for those into building enterprise systems. -David On Feb 26, 2010, at 10:13 AM, Scott Gray wrote: > My point still stands, OFBiz intentionally does not use an ORM layer and if > the reasons behind that are not understood then any discussions about it are > going to be somewhat fruitless. > > Regards > Scott > > On 26/02/2010, at 10:06 AM, huang.mi...@gmail.com wrote: > >> Use Grails doesn't means bundle with Hibernate. Grails also supports >> GORM-JPA combine, license compatible products such as OpenJPA can be >> used instead. It can defer to the deploy time (thus up to end user) to >> choose Hibernate or some other JPA implementation. >> >> On Fri, 2010-02-26 at 09:00 -0700, Scott Gray wrote: >>> Hi Chris >>> >>> With all due respect, your desire to replace the entity engine with >>> hibernate exhibits a serious lack of understanding of one of OFBiz's core >>> design philosophies. This has been discussed many times so I don't want to >>> rehash the debate here but I do strongly suggest that you search the >>> mailing lists for discussions pertaining to hibernate and ORM in general. >>> >>> Regards >>> Scott >>> >>> HotWax Media >>> http://www.hotwaxmedia.com >>> >> >> >
