EventListenerConfigurator uses Ejb3Configuration but could use AnnotationConfiguration instead

Not exactly true as we do change the contextual class loader in some of these method calls.
But more importantly, why do you want to pass an AnnotationConfiguration instead of an Ejb3Configuration?

The idea is to make it easier for users to set up the callback listeners when using core+annotations (sans entitymanager)

I am not super comfortable with exposing EventListenerConfigurator as a public API.

It does several things:

• add the JPA style callbacks

• change the semantics of flush and persist to accommodate JPA

• add JACC support

I imagine the users only want JPA style callbacks and hence are using annotations already.

If that's the case, we need to prototype a way to push it back the callback listener configuration to annotations (instead of entitymanager).

This issue is currently scheduled for 3.5.x, but not 3.6. Should this issue be fixed in 3.6 as well (or instead)? If so, please correct the fix version(s).

Thanks,
Gail

Bulk closing rejected tickets in "resolved" state.