[
https://issues.apache.org/jira/browse/OFBIZ-4274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482251#comment-16482251 ]
Scott Gray commented on OFBIZ-4274:
-----------------------------------
One option to consider, that is maybe a bit unconventional:
* Create a mapping DSL similar to entity definitions that maps a "resource" (complex JSON document) to the entity model
* Implement logic similar to the entity-auto engine that allows search/get/create/update/delete operations on the resources without any additional logic beyond the mapping DSL
* Implement all non-auto logic as Resource ECAs (RECAs) that can validate and modify the document and initiate operations on other related resources
Rather than resulting in a REST-like set of web APIs, it would essentially make OFBiz a fully RESTful architecture from the ground up. The entire system would operate via the REST API rather than directly interacting with the delegator. Instead of dealing with the ~3700 services we have currently, we'd basically have maybe 50 or so "resources" that would represent the entire API. Obviously there would be a lot of ECA services but they could be hidden away a bit since they aren't intended to be called directly.
Unfortunately it would involve re-writing pretty much everything.
> Implement a REST Servlet
> ------------------------
>
> Key: OFBIZ-4274
> URL:
https://issues.apache.org/jira/browse/OFBIZ-4274> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Affects Versions: Trunk
> Reporter: Adrian Crum
> Priority: Minor
> Labels: REST
> Attachments: RestExampleSchema.xsd, RestXmlRepresentation.xml, rest-conf.xml, swagger-pos-openapi.png
>
>
> Implement a REST servlet that will map REST requests to OFBiz services. Details are in the comments.
> [here is the discussion which took place on the dev ML|
http://markmail.org/message/ai6q2fbksowaayn4]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
