On Mon, Dec 12, 2016 at 3:26 AM Romain Manni-Bucau
wrote:
> 2016-12-12 9:13 GMT+01:00 Mark Struberg :
>
> >
> > > Am 11.12.2016 um 22:24 schrieb John D. Ament :
> > >
> > > However, using bean.getBeanClass() is more correct.
> >
> > Nope, read the spec paragraph for producer methods and fields:
>
2016-12-12 9:13 GMT+01:00 Mark Struberg :
>
> > Am 11.12.2016 um 22:24 schrieb John D. Ament :
> >
> > However, using bean.getBeanClass() is more correct.
>
> Nope, read the spec paragraph for producer methods and fields:
>
> 11.1. The Bean interface
> "• getBeanClass() returns the bean class of t
> Am 11.12.2016 um 22:24 schrieb John D. Ament :
>
> However, using bean.getBeanClass() is more correct.
Nope, read the spec paragraph for producer methods and fields:
11.1. The Bean interface
"• getBeanClass() returns the bean class of the managed bean or session bean or
of the bean that decl
Le 12 déc. 2016 01:08, "John D. Ament" a écrit :
On Sun, Dec 11, 2016 at 5:38 PM Romain Manni-Bucau
wrote:
> Le 11 déc. 2016 22:24, "John D. Ament" a écrit :
>
> Romain,
>
> On Sun, Dec 11, 2016 at 4:08 PM Romain Manni-Bucau
> wrote:
>
> > Le 11 déc. 2016 21:30, "John D. Ament" a écrit :
> >
On Sun, Dec 11, 2016 at 5:38 PM Romain Manni-Bucau
wrote:
> Le 11 déc. 2016 22:24, "John D. Ament" a écrit :
>
> Romain,
>
> On Sun, Dec 11, 2016 at 4:08 PM Romain Manni-Bucau
> wrote:
>
> > Le 11 déc. 2016 21:30, "John D. Ament" a écrit :
> >
> > All,
> >
> > So Romain had a good point, let's
Le 11 déc. 2016 22:24, "John D. Ament" a écrit :
Romain,
On Sun, Dec 11, 2016 at 4:08 PM Romain Manni-Bucau
wrote:
> Le 11 déc. 2016 21:30, "John D. Ament" a écrit :
>
> All,
>
> So Romain had a good point, let's not pollute the vote thread with this
> issue. I raised a problem with the curr
Romain,
On Sun, Dec 11, 2016 at 4:08 PM Romain Manni-Bucau
wrote:
> Le 11 déc. 2016 21:30, "John D. Ament" a écrit :
>
> All,
>
> So Romain had a good point, let's not pollute the vote thread with this
> issue. I raised a problem with the current release, its related to an
> issue that's exist
Le 11 déc. 2016 21:30, "John D. Ament" a écrit :
All,
So Romain had a good point, let's not pollute the vote thread with this
issue. I raised a problem with the current release, its related to an
issue that's existed in the CDI integration for some time, but was made
worse by a recent change in
All,
So Romain had a good point, let's not pollute the vote thread with this
issue. I raised a problem with the current release, its related to an
issue that's existed in the CDI integration for some time, but was made
worse by a recent change in CXF for the 3.1.9 release.
In old versions of CXF