Hi Scott, it was just an example. The point I was trying to make is that by making the entity engine a separate module, the implementation doesn't matter as long as the entity engine module fullfilled its api contract. One of the benefits of this modular approach is that it would enable developers or are interested in working on the entity engine could do so without having to first isolate the persistence code from the configuration code.
On 18 Sep 2010 06:49, "Scott Gray" <scott.g...@hotwaxmedia.com> wrote: Hi Chris, Could you explain how you envisage swapping the entity engine with hibernate considering one uses Maps (GenericValue) and the other uses POJOs to represent data? Thanks Scott HotWax Media http://www.hotwaxmedia.com On 18/09/2010, at 1:32 AM, chris snow wrote: > I would see entity engine and service engine as se...
