Hi BJ, there are parts of ofbiz that could be 'easily' used outside of ofbiz if they weren't all part of the same code base. The Entity Engine example is one part that could become a library. Other parts include the datatype coverters and temporal expressions. At the moment if I want to use these parts of ofbiz in external applications, I have to manually extract them from the ofbiz code base.
The framework would then be an assembly of libraries. By splitting ofbiz up, each library (entity engine, converters, temporal expressions, etc) could be developed independently of the rest of the ofbiz code. Do you want me do list the advantages of this approach? On Sat, Sep 18, 2010 at 10:02 AM, BJ Freeman <[email protected]> wrote: > Chris I may be dense, but what dependencies do you see from the entity > engine to the rest of ofbiz? > I agree that from the rest of ofbiz the entity engine is core, and is to me > the very reason that ofbiz is great. > But from a framework point of view you can strip away the application and > specialpurpose and build anything you want on top of the framework. > which is why it is called a framework. > > outside of the base and supporting files in framework, you could probably > reemove 50% of the framework and still have the entiy engine work. > > So is it just a technical thing or is there really a gain in what you are > saying? > > Just trying to get a Grasp on what you goal and scope is. > > chris snow sent the following on 9/18/2010 1:48 AM: >> >> I'm sorry for pushing this off-track by mentioning hibernate. The >> important >> point is that the technologies aren't important. There are many > > technologies that could be used for the entity engine, and as BJ has > pointed >> >> out, the ofbiz entity engine is very good. The problem for me is that the >> entity engine is deeply interwined with the rest of ofbiz. These >> dependencies need to be managed. Having a more modular ofbiz has >> advantages >> for ofbiz as a whole and for each module. >> >> On 18 Sep 2010 09:03, "BJ Freeman"<[email protected]> wrote: >> >> One of the reason I came to ofbiz was to get away from the bloat of ORM. >> if I read the modeler right that is swt based Gui which introduces a >> communication layer back to the server, unlike ofbiz being generated on >> the >> fly into html, from the server. >> >> BTw I have a Commercial Swt Gui Generator and use it for my legacy apps I >> converted to ofbiz, as well as the communications layer using JNL. >> >> ========================= >> BJ Freeman >> >> >> Strategic Power Office with Supplier Automation< >> http://www.businessesnetwork.com/automation/viewf... >> james_sg sent the following on 9/18/2010 12:24 AM: >> >> >> >> >>> >>> Hi all, >>> >>> Apache Cayenne has the closest match to OFBiz Entity Engine. >>> >>> A few points abo... >> > >
