Thanks for the quick feedback everyone!
I created an issue https://issues.apache.org/jira/browse/OFBIZ-13415 for
moving the plugin into framework.
For some reason I could not figure out how to assign it to myself, there
did not seem to be an option (Still new to jira). Just know that I will
start working on it soonish, depending on capacitys.
Best regards,
Lukas
Am 19.05.26 um 15:00 schrieb Nicolas Malin via dev:
Hey Michael,
On 5/19/26 11:15, Michael Brohl wrote:
Hi Nicolas,
in the course of the refactoring we would also contribute our
enhancements to the functionality, of which parts are already listed
in the subtasks of https://issues.apache.org/jira/browse/OFBIZ-11328.
There are other ideas and implementations not listed there.
Ok nice, I didn't follow this subject so no vision on this issue, it
great if before merging it on framework the most identify improvement
will be done.
Tests and an example are a good idea, we'll take this into account.
Sure, that important for other to be sure if I apply a framework
change, I'll not break this work and can introduce many frustration.
The separation of services and the rest api definition is
intentional: services can be used independently of the REST API as
usual. Only if you want to make them available to REST, you'll
configure them in the REST definition. I do not recommend to mix
those definitions.
I would talk, not merge api element on the service definition, but
more like seca.
If api it's a part of the framework, we can follow like other
framework element
<service-resource type="model" loader="main"
location="servicedef/services.xml"/>
<service-resource type="eca" loader="main"
location="servicedef/secas.xml"/>
<service-resource type="api" loader="main"
location="servicedef/service-rest.xml"/>
Cheers,
Nicolas
Thanks and regards,
Michael Brohl
ecomify GmbH - www.ecomify.de
Am 19.05.26 um 10:25 schrieb Nicolas Malin via dev:
Hi,
I thinks it's a good idea if we growing the quality code to include
it as real component and not only move it from plugins to framework.
What bothers me (or I missed something) :
* No integration test and unit test
* Rename the webapp docs for less generic word
* Separation of service and api xml definition, perhaps thinking
how define it on the same model
* Have implement example (in logic present with test by the way)
At Néréide we currently work on different improvement on the
framework, I don't know if we have the time to help on this task but
if some window will be present, I would be a pleasure.
Nicolas
On 5/18/26 15:56, Lukas Finster wrote:
Hi all,
I'd like to bring up a topic that has been briefly touched upon in
the past: integrating the REST-API plugin directly into the
framework as a core component.
As many of you know, the REST API plugin has become an increasingly
important building block for OFBiz-based projects. Rather than
leaving it as an optional add-on, I think it could benefit the
community to have it maintained and shipped as part of the standard
framework.
We at ecomify have been working with the plugin for years and
discussed this internally. If the community approves, we would love
to put in the work to make this happen.
Looking forward to hearing your thoughts
Lukas
--
Lukas Finster
Softwareentwickler & Berater
ecomify GmbH, Stralsunder Straße 63, 33605 Bielefeld
Fon: +49 521 448157-90 | Fax: +49 521 448157-99 | www.ecomify.de
Court Registration: Amtsgericht Bielefeld, HRB 41683 | CEO: Martin Becker,
Michael Brohl
