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 stack
Yes, I'll keep the deprecated one and will run tests as appropriate.
5.3/5.4 are already "tainted" anyway: there are some versions that won't
work with application servers using the new interface. So application
servers are unlikely to switch to the new interface until they stop
supporting 5.3/5.4
Just be careful. We kept the deprecated one as WildFly "needs it"
On Fri, Mar 8, 2019 at 10:55 AM Yoann Rodiere wrote:
> From your stack trace, it seems that the object you pass to Hibernate ORM
> is not correctly detected as implementing the ExtendedBeanManager.
>
> And actually I just checked
From your stack trace, it seems that the object you pass to Hibernate ORM
is not correctly detected as implementing the ExtendedBeanManager.
And actually I just checked, and there seems to be a bug: we require the
object to implement the deprecated
org.hibernate.jpa.event.spi.jpa.ExtendedBeanManag
Hello Yoann
Indeed I have tried that as an experiment, I got the following error when
I did:
Caused by: java.lang.ClassCastException: Cannot cast class
com.sun.proxy.$Proxy22 to interface
javax.enterprise.inject.spi.BeanManager
at java.lang.Class.cast(Class.java:2623)
at
org.h
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
