Hi all.
In my opinion, OFBiz is not meant or built to be a major technological
framework, and I second the thought that its
strength resides in its data model, and functional readiness.
But the idea of separating some of the components may lead to the
possibility of having some of the technical parts
available and exposed as maven dependencies.
I'm having the difficulty myself, I need the OFBiz jar as a dependency
for the plugin project, and this means :
- Either having to manually update the lib (this is what I currently do,
but is not ideal at all)
- or setting up a quite heavy gradle task (seems a bit overkill)
Having the "ofbiz-delegator" or "ofbiz-dispatcher", or even a more
global "ofbiz-core" package available as a library
could be a valuable addition, but it would require some work indeed.
After some research, it seems a related discussion took place late 2023
[1] The different PRs seems to be closed though.
[1] https://lists.apache.org/thread/7vlyg45zv7sjgt1zgkmypjkb4zv06wjv
Best Regards,
Gaetan
On 10/23/25 14:02, Deepak Dixit wrote:
Hi Team,
I would like to propose restructuring the OFBiz architecture by moving core
applications out of the main OFBiz framework — similar to how plugins are
currently managed.
This change would enable developers to build *custom ERP solutions* without
being tied to all the default applications and their associated 750+
database tables. By decoupling applications from the framework, we can
provide a lighter and more modular foundation for building domain-specific
or microservice-based solutions.
I strongly believe this approach will *significantly increase OFBiz
adoption* and flexibility, allowing users to leverage the framework purely
as an enterprise-grade development platform rather than being constrained
by bundled modules.
Thanks & Regards
--
Deepak Dixit
