Hi all, I’ve opened a pull request proposing some internal refactoring for the rest-api plugin. The PR is available at [*]. The changes do not affect any features or functionality, all usage notes and instructions (such as those in the OFBiz rest-api plugin documentation [**]) remain valid.
The goal of this work is to improve and simplify the internal organization of the plugin. In particular, the changes include: * Grouping all custom annotations within a dedicated package * Cleaning up and rationalizing annotation usage * Removing unnecessary base classes * Simplifying error and response handling * Misc cleanups. These improvements should make the codebase easier to understand and maintain. In my opinion, any future work or enhancements to this component would benefit from being built on top of this refactoring. For this reason, I’d like to merge it into trunk once (and if) the community agrees. I’m aware Michael’s team has been working on enhancements to this component: On Thu, Oct 23, 2025 at 10:48 PM Michael Brohl <[email protected]> > wrote: > We are using OFBiz for nearly 25 years now, building complex custom > projects using more or less parts of the datamodel/services and > sometimes even without any UI to serve as a database plus REST API > (using a very much enhanced REST-API plugin). It would be great if you could consider rebasing your work on top of this refactored version. I believe this cleaner internal structure will make it easier to maintain even custom or extended functionality moving forward. Please have a look at the PR and share your feedback. Once I get the green light from the community, I’ll proceed with the merge. Thanks, Jacopo [*] https://github.com/apache/ofbiz-plugins/pull/146 [**] https://cwiki.apache.org/confluence/display/OFBIZ/How+to+implement+RESTful+APIs+using+the+OFBiz+rest-api+plugin
