On Thu, 2010-02-25 at 05:31 -0800, Chris Snow-2 [via OFBiz] wrote: > Plugins could be used for separating the modules, this will be more > interesting in Grails 2.0 when the plugin framework will use OSGi - > http://jira.codehaus.org/browse/GRAILS-2221 >
This is a good side witness on the correctness of "Don't re-invent wheels". Would it be nice to upgrade a 3rd-party library and sit-back, then suddenly an excellent new feature bring in? On Thu, 2010-02-25 at 05:31 -0800, Chris Snow-2 [via OFBiz] wrote: > Rather than bring ofbiz to grails, you may find it would be easier to > bring grails to ofbiz, for example it should be relatively trivial to > sit a grails app on top of ofbiz (i.e. as a war file), and use grails > to > access the current ofbiz services. > Nice idea. Instead of move the whole platform to Grails as a huge step, bring in Grails to OFBIZ, a reversed way could be an easier and more acceptable choice. May be one or some components could be re-written in Grails, while keep interoperability with other components. When this could be done, more people can make judgement based on the running code. And this bring in a gradational upgrade path. -- View this message in context: http://n4.nabble.com/Brain-storm-OFBIZ-on-Grails-is-this-a-right-way-for-the-future-tp1568009p1570179.html Sent from the OFBiz - User mailing list archive at Nabble.com.
