Re: microprofile openapi @asf?

Hi, as written in the JIRA comment https://issues.apache.org/jira/browse/CXF-7601?focusedCommentId=1675&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1675 there is now a branch for the implementation with a working draft. Cheers Dennis

Re: microprofile openapi @asf?

Hi Dennis, yes likely, you can also probably starts from the maven plugin which just uses a manually listed set of classes and bypasses cdi integration (since it is at build time without a container launch) Romain Manni-Bucau @rmannibucau | Blog

Re: microprofile openapi @asf?

Hi, I want to catch up with this topic and start to think about CXF-7601. My suggestion is to add a new module description-microprofile-openapi oder description-openapi-microprofile for it. > RMB> Just to update you: we just passed the TCK. Impl is likely not perfect > but I proposed @geronimo

Re: microprofile openapi @asf?

This is great, Romain! Congrats on making a huge progress in such a short term. Best Regards, Andriy Redko Sunday, July 8, 2018, 2:32:53 PM, you wrote: RMB> Hi guys, RMB> Just to update you: we just passed the TCK. Impl is likely not perfect but I proposed @geronimo to start a 1.0.0 RMB>

Re: microprofile openapi @asf?

Hi guys, Just to update you: we just passed the TCK. Impl is likely not perfect but I proposed @geronimo to start a 1.0.0 vote with that since we are tck friendly and then iterate with the classical reports/bugs/... flow. I introduced a very light reflection abstraction to isolate most of the logi

Re: microprofile openapi @asf?

Le dim. 24 juin 2018 21:59, Andriy Redko a écrit : > Hi Romain, > > Just went through the issues and comment threads. I am not really involved > in MP (sadly) > but the YAML+JSON discussion makes sense to me, at least from the platform > perspective. JSON > should be a must, YAML is optional (alt

Re: microprofile openapi @asf?

Hi Romain, Just went through the issues and comment threads. I am not really involved in MP (sadly) but the YAML+JSON discussion makes sense to me, at least from the platform perspective. JSON should be a must, YAML is optional (although it is very popular in OpenAPI community). My personal p

Re: microprofile openapi @asf?

Hi guys, opened several issues about the spec and a few of them are serious concerns for me (others are easier): 1. https://github.com/eclipse/microprofile-open-api/issues/231 2. https://github.com/eclipse/microprofile-open-api/issues/230 3. https://github.com/eclipse/microprofile-open-api/issues

Re: microprofile openapi @asf?

Great! On Thu, Jun 21, 2018 at 10:12 AM, Romain Manni-Bucau wrote: > @Raymond: the diff between CDI and OSGi will be where the OpenAPI instance > will be created mainly so very doable (aries can even import G-openapi for > that). Only diff which can be quite intrusive is that @G we don't use pl

Re: microprofile openapi @asf?

@Raymond: the diff between CDI and OSGi will be where the OpenAPI instance will be created mainly so very doable (aries can even import G-openapi for that). Only diff which can be quite intrusive is that @G we don't use plain reflection to enable CDI meta model to be mutated during startup and ther

Re: microprofile openapi @asf?

It would be _nice_ if we could figure out a way for this to be usable by Apache Aries JAXRS Whiteboard [1] which is an implementation of OSGi JAXRS Whiteboard [2]. It would seem that a small SPI on the part of Geronimo's mp-openapi might be enough (so as not to pressure this up onto the mp spec).

Re: microprofile openapi @asf?

I think it fits well to geronimo. The question is rather if CXF is fine with relying on CDI for openapi? But since MicroProfile _requires_ CDI I think there is safe to assume so. LieGrue, strub > Am 21.06.2018 um 09:59 schrieb Romain Manni-Bucau : > > Hello guys, > > we created a repo for that

Re: microprofile openapi @asf?

Hello guys, we created a repo for that and to be able to share what we do: https://gitbox.apache.org/repos/asf?p=geronimo-openapi.git I pushed a basic starting structure of the code. The big TODO is the conversion from the model (annotations) to OpenAPI instance (which should be somewhere here ht

Re: microprofile openapi @asf?

Basically read metadata from AnnotatedTypes (cdi) used by jaxrs cdi extension. Im not yet sure i will need the extension itself or not (doesnt seem hard to not use it for that and would stay portable). Le mar. 19 juin 2018 00:36, Andriy Redko a écrit : > Hey Romain, > > Thanks for starting work

Re: microprofile openapi @asf?

Hey Romain, Thanks for starting work on that. Indeed, https://issues.apache.org/jira/browse/CXF-7601 is opened but not started yet, sadly. So what is your plan / scope, generate the OpenAPI 3.x specs from JAX-RS 2.1 metadata? Or someting else? May be we could also help you with that? Thanks

Re: microprofile openapi @asf?

Independent, cdi based (not reflection based) Le lun. 18 juin 2018 22:34, John D. Ament a écrit : > If it's hosted at Geronimo will it be platform independent? Or only work > with CXF? > > On Mon, Jun 18, 2018, 3:30 PM Romain Manni-Bucau > wrote: > > > Hi guys, > > > > I'm planning to implemen

Re: microprofile openapi @asf?

If it's hosted at Geronimo will it be platform independent? Or only work with CXF? On Mon, Jun 18, 2018, 3:30 PM Romain Manni-Bucau wrote: > Hi guys, > > I'm planning to implement microprofile-openapi at geronimo (next to other > microprofile specs) soon (probably beginning of next month). Befo

Re: microprofile openapi @asf?

Hi Romain, currently we have an open issue for that https://issues.apache.org/jira/browse/CXF-7601 but afaik nobody has started an implementation yet. In my view CXF should work with both Swagger Core annotations and Microprofile OpenAPI annotations in the end, I don't mind where it's hosted. Re

microprofile openapi @asf?

Hi guys, I'm planning to implement microprofile-openapi at geronimo (next to other microprofile specs) soon (probably beginning of next month). Before doing so I wanted to get in touch with you to ensure it was not already there (@asf). I know CXF has a swagger impl but here, we speak about a new