Re: 3.2.2 cdi integration and @Context.

Mainly but I strongly think cxf shouldnt assume it can own default. At least we should observe beans to skip the add if already here and have a bus property to fully skip it - or extension event to configure jaxrs extension. Le 6 févr. 2018 20:53, "John D. Ament" a écrit : > So then your issue i

Re: 3.2.2 cdi integration and @Context.

So then your issue is simply the javax.servlet ones, right? On Tue, Feb 6, 2018 at 2:14 PM Romain Manni-Bucau wrote: > Le 6 févr. 2018 20:07, "John D. Ament" a écrit : > > If we remove @Default then it won't be injectable without > @ContextResolved. Are you seeing an issue though? > > > Yes. O

Re: 3.2.2 cdi integration and @Context.

Le 6 févr. 2018 20:07, "John D. Ament" a écrit : If we remove @Default then it won't be injectable without @ContextResolved. Are you seeing an issue though? Yes. Owb-web provides all servlet beans so it leads to ambiguous resolution. Also not being in the spec it must use a custom classifier

Re: 3.2.2 cdi integration and @Context.

If we remove @Default then it won't be injectable without @ContextResolved. Are you seeing an issue though? On Tue, Feb 6, 2018 at 1:59 PM Romain Manni-Bucau wrote: > Cdi provides a servlet context, request etc... bean. With cxf contextbean > it is now ambiguous and you cant use a cdi container

Re: 3.2.2 cdi integration and @Context.

Cdi provides a servlet context, request etc... bean. With cxf contextbean it is now ambiguous and you cant use a cdi container with cxf. The default qualifier must be dropped from that bean. Le 6 févr. 2018 19:57, "John D. Ament" a écrit : > Sorry don't really understand your response. > > On Tu

Re: 3.2.2 cdi integration and @Context.

Sorry don't really understand your response. On Tue, Feb 6, 2018 at 1:52 PM Romain Manni-Bucau wrote: > @Inject X x; should match not a single CXF injection but > ContextProducerBean matches @Default. Read too fast and though it was > @Context but just looks like @Default shouldnt be in the bean

Re: 3.2.2 cdi integration and @Context.

@Inject X x; should match not a single CXF injection but ContextProducerBean matches @Default. Read too fast and though it was @Context but just looks like @Default shouldnt be in the beans. Romain Manni-Bucau @rmannibucau | Blog

Re: 3.2.2 cdi integration and @Context.

On Tue, Feb 6, 2018 at 1:49 PM Romain Manni-Bucau wrote: > Hi guys, > > doesn't cdi integration of jaxrs miss a: > > bbd.addQualifier(Context.class); > > What class is that? > ? > > > > Romain Manni-Bucau > @rmannibucau | Blog >

3.2.2 cdi integration and @Context.

Hi guys, doesn't cdi integration of jaxrs miss a: bbd.addQualifier(Context.class); ? Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

[GitHub] sberyozkin commented on issue #378: [CXF-7636] wadl2java: support Oneway annotation

sberyozkin commented on issue #378: [CXF-7636] wadl2java: support Oneway annotation URL: https://github.com/apache/cxf/pull/378#issuecomment-363500413 Hi Alexey, looks fine to me, please merge This is an automated message fro

[RESULT] [VOTE] CXF 3.2.2

We have 14 +1 votes and no other votes.This vote passes. Dan > On Feb 2, 2018, at 2:57 PM, Daniel Kulp wrote: > > This is a vote to release CXF 3.2.2. We’ve fixed over 60 JIRA issues, > definitely time to release it. This also includes releases of build-utils > (3.4.0) and xjc-uti

[GitHub] amarkevich opened a new pull request #378: [CXF-7636] wadl2java: support Oneway annotation

amarkevich opened a new pull request #378: [CXF-7636] wadl2java: support Oneway annotation URL: https://github.com/apache/cxf/pull/378 This is an automated message from the Apache Git Service. To respond to the message, plea

Re: Remove obsolete RxJava code and keep RxJava2 only one

I'd still favour removing RxJava, if you would like to keep it then I guess the new module would indeed have to be introduced Cheers, Sergey On 06/02/18 03:49, John D. Ament wrote: I was just about to remove the optional marking on reactive streams, and noticed that rxjava was still around. I