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 ExtendedBeanManager, never both.
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
On Fri, 8 Mar 2019 at 11:16, Benjamin Confino <BENJAMIC(a)uk.ibm.com> wrote:
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
handler for the proxy is being called by hibernate, but there is no call
to registerLifecycleListener. Instead I see hibernate trying to use the
bean manager before it has been initialised.
Do I need to do anything extra to configure hibernate? I was under the
impression that if the object in javax.persistence.bean.manager
implemented ExtendedBeanManager everything would automatically be
configured.
Regards
Benjamin
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev