The only library that is not friendly right now is the Redstone XMLRPC library, which is LGPL licensed. That could be replaced by the Apache XML-RPC project. The only reasons I used Redstone are that it is much smaller (library bloat is a real problem), and it is a bit easier to use.
There are a couple of libraries that use CDDL (winstone servlet container) and EPL (Mylin WikiText), but they are in binary form only so should be fine. If there is enough interest I'd be happy to change Moqui to use Apache XML-RPC instead of Redstone. -David Jacopo Cappellato wrote: > David, > > a side note (but important): is Moqui using (or there are plans to use) jars > or external tools whose license would prevent us from bundling Moqui in an > OFBiz release under the ASL 2.0? This would be a show stopper... > > Jacopo > > On Mar 15, 2012, at 6:08 AM, David E Jones wrote: > >> This might actually be good in a separate email, but anyway... >> >> The Moqui Framework would be a separate project from OFBiz, and while >> some OFBiz committers could certainly become moderators for Moqui that >> would be based on their personal efforts and merits and not anything to >> do with what happens or has happened in OFBiz. >> >> Moqui has a lot more extension points built-in than the OFBiz Framework, >> so you can actually do quite a bit without changing the framework >> itself. For cases where changes are needed (or wanted) to Moqui itself >> they would go through the normal feature request and patch submission >> process for Moqui to be reviewed by a moderator. Initially this would be >> me, and I obviously have some skin invested in an effort like this so >> I'd try to be responsive as possible (I have been so far with Moqui, but >> most of the time it has had light traffic so I've been able to get >> things reviewed and changed/fixed within a couple of days). >> >> One of the easiest ways to do that is with a pull request on GitHub. In >> fact, if the OFBiz variation of the Moqui Framework was managed on >> GitHub you could customize things there as desired while still being >> able to submit changes back to Moqui and get updates from Moqui so that >> OFBiz can more easily participate in the Moqui community. In git >> terminology this would actually be a "fork", and I think is what Jacopo >> was talking about. >> >> Still, for the most part my guess is that this would not be needed and >> I'd recommend starting with just the jar files (or even just the war >> file) and not set things up for easily changing the framework until the >> need for doing so is well established. >> >> For this interested in considering Moqui for use in OFBiz, the tutorial >> and framework intro docs are probably the best places to start, and the >> Run/Deploy doc is also helpful (BTW, the moqui.org site is actually >> running on Moqui, and the tutorial and run/deploy docs are actually >> cwiki documents (confluence-style wiki text)): >> >> http://www.moqui.org/framework/docs/Tutorial.html >> >> http://sourceforge.net/projects/moqui/files/IntroductionToMoquiFramework-1.0.1.pdf/download >> >> http://www.moqui.org/framework/docs/RunDeploy.html >> >> Anyway, sorry for the delay in responding to this. I'm still a bit busy >> on contracts and I only catch up on the OFBiz mailing lists every week >> or so. >> >> -David >
