[jira] [Resolved] (UNOMI-356) Refactor REST integration to support Swagger & more extensibility

["Serge Huber (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/UNOMI-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Serge Huber resolved UNOMI-356.
-------------------------------
    Resolution: Fixed

> Refactor REST integration to support Swagger & more extensibility
> -----------------------------------------------------------------
>
>                 Key: UNOMI-356
>                 URL: https://issues.apache.org/jira/browse/UNOMI-356
>             Project: Apache Unomi
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.0.0
>            Reporter: Serge Huber
>            Assignee: Serge Huber
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently, we use Apache CXF Blueprint registration of REST services. This has the following problems:
> - Multiple endpoints are created because of limitations registering multiple services using Blueprint
> - Miredot plugin to generate documentation is not standard, it is a proprietary tool. Switch to Swagger or even better OpenAPI make sense.
> The proposal is to replace the Blueprint integration of Apache CXF with a custom setup of a CXF JAX-RS server that would support extensibility through OSGi service registration. 
> We should also integrate Swapper and OpenAPI directly.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)