May be the Grails plugin mechanism is a good solution for the modularity problem. If we separate the OFBIZ components into stand-alone Grails plugins, each component is just like separated Grails applications, which can be maintained in their own source directory structure. And during development period, the Grails framework can provide sophisticated mechanisms to resolve the OFBIZ module dependency. At runtime, the dependent components are just deployed alongside with the referencing components in the same web application, remote service call is not required.
I'm not familiar with OSGi, so I can't say much about it. But if we need to support dynamical deploy/undeploy componets and multi-version module, the OSGi promise sounds attractive. Through a quick glance at the presentation from spring source ( OSGi 4.2 the Blueprint Service RI provider ), my understanding is the OSGi will take the responsibility to manage the web application dynamic module, while the web app framework such as Grails will take the responsibility to construct the dynamic module implementation framework. Does this mean OSGI and Grails technology can be integrated without overlaps and conflicts? -- View this message in context: http://n4.nabble.com/Brain-storm-OFBIZ-on-Grails-is-this-a-right-way-for-the-future-tp1568009p1568878.html Sent from the OFBiz - User mailing list archive at Nabble.com.
