Thank you Yoann
Implementing the old interface has let me progress.
From: Yoann Rodiere
To: Benjamin Confino
Cc: Hibernate Dev
Date: 08/03/2019 16:55
Subject:Re: [hibernate-dev] ExtendedBeanManager
Sent by:hibernate-dev-boun...@lists.jboss.org
>From your st
t;> >
>> > If it helps I'm running with hibernate-core-5.4.1.Final.jar - I'm not
>> sure
>> > what other info will help you but if you let me know I can send it over.
>> >
>> > Regards
>> > Benjamin
>> >
>> >
>&g
let me know I can send it over.
> >
> > Regards
> > Benjamin
> >
> >
> >
> >
> > From:Yoann Rodiere
> > To:Benjamin Confino
> > Cc:Hibernate Dev
> > Date:08/03/2019 15:52
> > Subject:Re:
end it over.
>
> Regards
> Benjamin
>
>
>
>
> From:Yoann Rodiere
> To:Benjamin Confino
> Cc:Hibernate Dev
> Date:08/03/2019 15:52
> Subject:Re: [hibernate-dev] ExtendedBeanManager
> Sent by:hibernate-dev-boun...@lis
lps I'm running with hibernate-core-5.4.1.Final.jar - I'm not sure
what other info will help you but if you let me know I can send it over.
Regards
Benjamin
From: Yoann Rodiere
To: Benjamin Confino
Cc: Hibernate Dev
Date: 08/03/2019 15:52
Subject: Re: [hibernate
Hello,
It's supposed to work as you described.
Have you tried making your class implement *only* ExtendedBeanManager?
It should have worked even if your class implements both, but there might
be a bug... As far as I know we only ever pass objects implementing either
BeanManager or ExtendedBeanMan
Hello
I'm attempting to write a prototype implementation for Hibernate's
Extended Bean Manager and I seem to have hit a problem. I have placed a
proxy class that implements both BeanManager and ExtendedBeanManager into
the property javax.persistence.bean.manager. I can see that the invocation
