Re: [hibernate-dev] org.hibernate.jpa.AvailableSettings.EVENT_LISTENER_PREFIX
2 very different things.
AvailableSettings.EVENT_LISTENER_PREFIX identifies Hibernate event
listeners that the user wants incorporated into the
org.hibernate.event.service.spi.EventListenerRegistry.
It does not name JPA listeners/callbacks; that is done through JPA specific
means via annotations.
So no, AvailableSettings.EVENT_LISTENER_PREFIX should not be deprecated.
In fact I am not even sure why you are asking that. So either I completely
missed your point, or you did not explain why you thought it should be
removed. I guess maybe you are blurring the distinction between the 2
concepts of callbacks?
On Mon, Jul 20, 2015 at 4:07 PM Gail Badner <gbadner(a)redhat.com> wrote:
AvailableSettings.EVENT_LISTENER_PREFIX is set to
"hibernate.ejb.event".
JpaIntegrator looks for ConfigurationService settings (which include
properties) with that prefix, then strips off that prefix to determine the
org.hibernate.event.spi.EventType.
I see that org.hibernate.event.spi.EventType has non-JPA event types. I
can see that it could be useful for an application to specify non-JPA
listeners to access Hibernate extensions. Is this what is intended?
Since JPA already defines annotations and <entity-listener> XML
descriptors to specify JPA entity listeners/callbacks, should Hibernate
continue to allow JPA entity listeners/callbacks to be specified using a
property with this prefix?
In master, the only test I see that uses a property prefixed with
"hibernate.ejb.event" is
org.hibernate.jpa.test.packaging.PackagedEntityManagerTest. Also, I don't
see any documentation for prefixing properties this way.
Should AvailableSettings.EVENT_LISTENER_PREFIX be deprecated?
Thanks,
Gail
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev