Thank you for reporting and even more important for taking time to reproduce in a small example.
Le ven. 2 déc. 2022, 02:21, W.H. Tsang <wh.ts...@lukfook.com.invalid> a écrit : > Hi, > > Thanks alot and look forward for the new release. > > > Cheers, > Hong. > ________________________________ > 寄件者: Jean-Louis Monteiro <jlmonte...@tomitribe.com> > 寄件日期: 2022年12月1日 21:28 > 收件者: users@tomee.apache.org <users@tomee.apache.org> > 主旨: Re: question on openapi ( 9.0.0rc1-mp ) > > Hi, > > I reworked the SmallRye OpenAPI integration in the server. The short story > is that it uses a Jandex index to find annotations, endpoints, and POJOs, > but you need to provide him with a complete index for him to work. Using a > CDI Extension did the trick at the beginning but in the end, we were > missing some classes, for instance POJOs with private constructors, > interfaces, etc. > > I ended up plugin in the integration during the deployment process, so we > can read from jars, from classes, interfaces, etc. > > It's currently building on our CI system. I'll monitor and see if there > isn't any TCK regression. > > Hopefully this helps. > > > -- > Jean-Louis Monteiro > http://twitter.com/jlouismonteiro > http://www.tomitribe.com > > > On Mon, Nov 28, 2022 at 10:51 AM Jean-Louis Monteiro < > jlmonte...@tomitribe.com> wrote: > > > Hi, > > > > I'm still working on some regressions after patching the first place. > I'll > > test your scenario in a test case, and let you know. Thanks for the help. > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > > > On Fri, Nov 25, 2022 at 8:42 AM W.H. Tsang <wh.ts...@lukfook.com.invalid > > > > wrote: > > > >> Hi, > >> > >> Thanks alot. > >> I have downloaded tomee-4117, compiled and tried. > >> I confirmed the /openapi can generated the api spec. > >> > >> However, it still find some questions. I have created 3 projects ( web, > >> api, impl ) as attached. > >> First, I create "HelloService.class" in web project and expose in > >> /api/hello/ > >> Second, I create "IOops.class" interface in api project and expose in > >> /api/oops/ > >> Finally, I create "OkService.class in impl project and expose in > /api/ok/ > >> ; and implemetation class for "IOops" interface. > >> ( For IOops, I put the jaxrs annotation on interface. For > >> HelloServer/OkService, I put the annotaion on class ) > >> > >> When I run in netbeans using tomee-4117, the result is: > >> /api/hello, /api/ok/, /api/oops/ three api are exposed correctly. > >> but openapi didn't generate the api/oops docs > >> > >> > >> best regards, > >> Hong. > >> > >> ------------------------------ > >> *寄件者:* Jean-Louis Monteiro <jlmonte...@tomitribe.com> > >> *寄件日期:* 2022年11月24日 4:12 > >> *收件者:* users@tomee.apache.org <users@tomee.apache.org> > >> *主旨:* Re: question on openapi ( 9.0.0rc1-mp ) > >> > >> Never mind, I created it > https://issues.apache.org/jira/browse/TOMEE-4117 > >> Here is the PR with a minimal happy path itest > >> https://github.com/apache/tomee/pull/978 > >> -- > >> Jean-Louis Monteiro > >> http://twitter.com/jlouismonteiro > >> http://www.tomitribe.com > >> > >> > >> On Wed, Nov 23, 2022 at 6:44 PM Jean-Louis Monteiro < > >> jlmonte...@tomitribe.com> wrote: > >> > >> > Hi Hang, > >> > > >> > I managed to reproduce the issue and fix the problem. > >> > Would you like to create an issue in TomEE so I can refer to it in the > >> > commit? > >> > Otherwise, nevermind, I'll create it tomorrow and create the PR > >> tomorrow. > >> > > >> > Best > >> > -- > >> > Jean-Louis Monteiro > >> > http://twitter.com/jlouismonteiro > >> > http://www.tomitribe.com > >> > > >> > > >> > On Sat, Nov 19, 2022 at 12:55 PM W.H. Tsang > >> <wh.ts...@lukfook.com.invalid> > >> > wrote: > >> > > >> >> Dear Jean-Louis, > >> >> > >> >> Many thanks and have a nice weekend. > >> >> > >> >> Cheers, > >> >> Hong > >> >> > >> >> Get Outlook for Android<https://aka.ms/AAb9ysg> > >> >> ________________________________ > >> >> From: Jean-Louis Monteiro <jlmonte...@tomitribe.com> > >> >> Sent: Saturday, November 19, 2022 12:59:20 AM > >> >> To: users@tomee.apache.org <users@tomee.apache.org> > >> >> Subject: Re: question on openapi ( 9.0.0rc1-mp ) > >> >> > >> >> Hi, > >> >> > >> >> I've been able to successfully build and test your project. I think I > >> >> found > >> >> a bug in the deployment process and the openapi model does not get > >> >> generated. I know how to fix it, but I'm in the middle of a CXF mess. > >> I'd > >> >> like to get this finished before but I'll fix the OpenAPI bug and > >> publish > >> >> a > >> >> new snapshot for you to try so we can create another release quickly. > >> >> > >> >> Thanks for reporting and your patience. > >> >> -- > >> >> Jean-Louis Monteiro > >> >> http://twitter.com/jlouismonteiro > >> >> http://www.tomitribe.com > >> >> > >> >> > >> >> On Fri, Nov 18, 2022 at 9:08 AM Jean-Louis Monteiro < > >> >> jlmonte...@tomitribe.com> wrote: > >> >> > >> >> > Hi, > >> >> > > >> >> > Good idea to create a small example. I'll run that and let you > know. > >> >> > > >> >> > Jean Louis > >> >> > > >> >> > Le ven. 18 nov. 2022, 05:02, W.H. Tsang > <wh.ts...@lukfook.com.invalid > >> > > >> >> a > >> >> > écrit : > >> >> > > >> >> >> Dear Tomee developer, > >> >> >> > >> >> >> > >> >> >> > >> >> >> I am new to microprofile and would like to test the openapi > feature. > >> >> >> > >> >> >> I use NetBeans12 and Tomee 9.0.0rc1 microprofile. > >> >> >> > >> >> >> I have created a minimal project with just one jaxrs service. > >> >> >> > >> >> >> However, I cannot get the openapi spec via > >> >> http://localhost:8080/openapi > >> >> >> . > >> >> >> > >> >> >> > >> >> >> > >> >> >> Really appreciate if anyone can point out my problem. > >> >> >> > >> >> >> Attached is my sample project and many thanks in advanced. > >> >> >> > >> >> >> > >> >> >> > >> >> >> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> > for > >> >> >> Windows > >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > >> > -------------------------------------------------------------------------------------------------- > >> >> >> > >> >> >> This e-mail message (together with any email attachments) is > >> >> >> confidential. It may also be legally privileged. If you are not > >> >> recipient, > >> >> >> you should not copy, forward, disclose or use any part of it. If > you > >> >> have > >> >> >> received this message in error, please delete it and all copies > from > >> >> your > >> >> >> system and notify the sender immediately by return e-mail. > Internet > >> >> >> communications cannot be guaranteed to be timely, secure, error or > >> >> >> virus-free. The sender and the entity through which this message > is > >> >> sent do > >> >> >> not accept liability for any errors or omissions. > >> >> >> > >> >> > > >> >> > >> >> > >> >> > >> > -------------------------------------------------------------------------------------------------- > >> >> This e-mail message (together with any email attachments) is > >> >> confidential. It may also be legally privileged. If you are not > >> recipient, > >> >> you should not copy, forward, disclose or use any part of it. If you > >> have > >> >> received this message in error, please delete it and all copies from > >> your > >> >> system and notify the sender immediately by return e-mail. Internet > >> >> communications cannot be guaranteed to be timely, secure, error or > >> >> virus-free. The sender and the entity through which this message is > >> sent do > >> >> not accept liability for any errors or omissions. > >> >> > >> > > >> > >> > -------------------------------------------------------------------------------------------------- > >> > >> This e-mail message (together with any email attachments) is > >> confidential. It may also be legally privileged. If you are not > recipient, > >> you should not copy, forward, disclose or use any part of it. If you > have > >> received this message in error, please delete it and all copies from > your > >> system and notify the sender immediately by return e-mail. Internet > >> communications cannot be guaranteed to be timely, secure, error or > >> virus-free. The sender and the entity through which this message is > sent do > >> not accept liability for any errors or omissions. > >> > > > > > -------------------------------------------------------------------------------------------------- > This e-mail message (together with any email attachments) is confidential. > It may also be legally privileged. If you are not recipient, you should not > copy, forward, disclose or use any part of it. If you have received this > message in error, please delete it and all copies from your system and > notify the sender immediately by return e-mail. Internet communications > cannot be guaranteed to be timely, secure, error or virus-free. The sender > and the entity through which this message is sent do not accept liability > for any errors or omissions. >
