If we change it we change what request scope is making impossible to move
to the spec OOTB - and btw this is how it behaves in any app pre cdi 2.0
and webapp evzn in cdi 2. Im really in favor of a flag to support both
without having to know any internal/classname and enable users to rely on
it for
On Mon, Aug 14, 2017 at 8:19 AM Romain Manni-Bucau
wrote:
> 2017-08-14 13:50 GMT+02:00 John D. Ament :
>
> > On Mon, Aug 14, 2017 at 1:03 AM Romain Manni-Bucau <
> rmannibu...@gmail.com>
> > wrote:
> >
> > > Le 14 août 2017 04:31, "John D. Ament" a
> écrit
> > :
> > >
> > > Hey guys
> > >
> > >
2017-08-14 13:50 GMT+02:00 John D. Ament :
> On Mon, Aug 14, 2017 at 1:03 AM Romain Manni-Bucau
> wrote:
>
> > Le 14 août 2017 04:31, "John D. Ament" a écrit
> :
> >
> > Hey guys
> >
> > Good news on the SE support front. Looks like there were two features
> just
> > missing outright in OWB 2 f
On Mon, Aug 14, 2017 at 1:03 AM Romain Manni-Bucau
wrote:
> Le 14 août 2017 04:31, "John D. Ament" a écrit :
>
> Hey guys
>
> Good news on the SE support front. Looks like there were two features just
> missing outright in OWB 2 from CDI 2.0.
>
> - Support for a config property javax.enterprise
Le 14 août 2017 04:31, "John D. Ament" a écrit :
Hey guys
Good news on the SE support front. Looks like there were two features just
missing outright in OWB 2 from CDI 2.0.
- Support for a config property javax.enterprise.inject.implicit.scan which
works the opposite of org.apache.webbeans.sca
