On Apr 28, 2015, at 10:39 AM, David E. Jones <[email protected]> wrote: > > +1 - with the clarification that to me "begin replacing" implies a PoC effort > in a branch. > > I just saw this thread and need a little time to think over the best > approach, but off the top of my head it would look something like: > > - add the moqui-framework-<version>.jar file and all dependent jars to a > component directory under ofbiz/framework (these could go in the base or > common components, but might be best separate for clarity); if needed update > jars currently used in OFBiz where an older version is used (don't know if > this is the case for any, mention for the sake of completeness) > > - add a Moqui runtime directory somewhere in the OFBiz directory tree (Moqui > uses this for various things); this would contain the Moqui tools components > (with the Tools and System apps) so we have a UI to look at Moqui internals, > OFBiz data, etc > > - either in the Moqui runtime directory or as an OFBiz component add a > "webroot" webapp; Moqui is designed to run in a single webapp, and I'd > recommend this be separate from the existing OFBiz webapps for now; when this > webapp loads it will init the Moqui ExecutionContextFactory, when it shuts > down it will destroy it > > - because initializing Moqui when the webroot webapp starts may not be > adequate, make sure the Moqui static init stuff is in place and working (in > the Moqui.java class) > > - run my little templates to transform current OFBiz data model XML files > into Moqui ones and put those in a Moqui component in the Moqui runtime > directory > > This would be a basic PoC to get Moqui running inside OFBiz, and then we > could start the real PoC of either a "thunk" layer as Adrian proposed, > probably accessing the statically initialized Moqui ExecutionContextFactory > since most OFBiz framework classes are statically initialized, or using the > more dynamic initialization through the Moqui webroot webapp. > ... > I would be happy to participate in this effort... if nothing else should be > an interesting technical diversion. > > -David
-1 to "Begin Replacing OFBiz Framework With Moqui": the decision is very important and cannot be done on such uncertain basis; an experimental branch/poc is required to better understand the best architecture (there are several options) and impact for the applications; after that a cleaner roadmap could be discussed and only at that point a vote could be called; the persons willing to work on this should be prepared to accept that the community may not decide to accept the switch because I doubt they will get a "pre-approval" +1 to this proposal by David, especially if we will be inclined to listen to David's advices because he is the one who designed the architecture of OFBiz and created Moqui: David's experience, knowledge and, more generally, skills will be invaluable in this process Jacopo
