Re: 3.2.2 cdi integration and @Context.

created https://issues.apache.org/jira/browse/CXF-7643 @John: not sure how it can work in any container integrated with a servlet container since you would not have the instance in a lot of cases so it can only work when the servlet layer is not usable in your environment and therefore the beans d

Re: 3.2.2 cdi integration and @Context.

Feel free to raise an issue on JIRA and a PR. Personally, I'd like for the javax.servlet stuff to remain, so maybe we make this configuration driven instead. On Mon, Feb 12, 2018 at 9:42 AM Romain Manni-Bucau wrote: > side note: temporary work around which makes 3.2.2 usable directly: > > Injec

Re: 3.2.2 cdi integration and @Context.

side note: temporary work around which makes 3.2.2 usable directly: InjectionUtils.STANDARD_CONTEXT_CLASSES.removeIf(s -> s.startsWith("javax.servlet.")); Romain Manni-Bucau @rmannibucau | Blog | Old Blog

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 >