Hello,
Apologies to jump on this late. This is really a great evolution. I spent quite some time on exposing a REST API for a fairly small adoption of OfBiz (extending products to be Seats for an event like a concert along with seat maps etc.). I also truly appreciate that the PR comes with decent documentation. Where I have doubts is the following: - how can we leverage OpenAPI / Swagger documentation? I can see description and parameter documentation being possible (but who does consistently use service/attribute/description elements?) - how can we map proper HTTP protocol return codes in the 4xx range? I don’t see these are blockers to move forward, but adoption of REST APIs in enterprise environments w/o such features these days appears at risk. For example, in my project, this is where I spent most of the time honestly. In the app I mentioned, in the REST Controller classes: - approx. 10% of the code lines are input validation and service calls - approx. 40% of lines are OpenAPI annotations and - approx. 50% of code lines are logging, exception handling and mapping to proper HTTP returns. So in brief, I see the value of being able to simplify REST API exposure for OfBiz Services, but we need to find a way to amend the shortcomings of the underlying service engine with regards to documentation and return code mapping. Maybe I am overlooking something - I just threw a brief read into the doc on the PR. Then feel free to point me :) Warm regards Carsten > Am 10.06.2026 um 15:20 schrieb Lukas Finster <[email protected]>: > > ted pose the question to the com
