Thanks, Ashish, for the details.

The permission-related entities are already part of the framework itself,
so we don’t need to move them separately into the framework.

Also, the Party entity belongs to the application layer, and I believe it’s
not required for the core framework functionalities.

Kind Regards,
Deepak Dixit
*www.hotwax.co <http://www.hotwax.co/>*


On Thu, Oct 23, 2025 at 6:44 PM Ashish Vijaywargiya <[email protected]>
wrote:

> +1 Deepak.
>
> Thank you for sharing this email.
>
> We should definitely consider moving the applications folder out of the
> OFBiz framework, similar to how we handle plugins.
>
> >>>>>>>>>>>>>>>
> By decoupling applications from the framework, we can
> provide a lighter and more modular foundation for building domain-specific
> or microservice-based solutions.
> >>>>>>>>>>>>>>>
>
> Big +1 on the above lines.
>
> I tried setting up OFBiz without the “applications” and “plugins” folders
> and performed the following operations on the Release24.09 branch:
>
> 1) Removed the applications and plugins folders.
>
> 2) Commented out the entries for the applications and plugins folders in
> the component-load.xml file located under framework/base/config/.
>
> Ran the following command:
> ./gradlew cleanAll loadAll -x test
> (excluded test cases, as I have been facing some issues there)
>
> 3) The OFBiz build and data load operations completed successfully, and
> OFBiz started without issues.
>
> 4) When I tried accessing WebTools, I encountered an error related to the
> UserLogin entity’s dependency on Party.
>
> If we decide to move applications folder out of the framework then I think
> we need to manage the framework with the User Permission Model.
> For example, we could define a few entities—such as SecurityGroup,
> UserLoginSecurityGroup, Party, SecurityPermission, and
> SecurityGroupPermission - as framework-only entities or something
> alternative to manage user permissions. Currently, these entities are
> defined under the applications/party component.
>
> Anyway, these are just a few quick thoughts off the top of my head.
>
> Thank you,
> Ashish Vijaywargiya
>
>
> On Thu, 23 Oct 2025 at 17:32, Deepak Dixit <[email protected]> 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
> >
>

Reply via email to