backupper | MODX backup script to backup database | Continuous Backup library

There really is not much involved in setting up bean injection with Spring Framework 5.1 and Envers. The listener implementation does not require being annotated by @Service nor @Component because these classes are actually constructed by Hibernate and then the ManagedBeanRegistry is responsible for coordinating with whatever DI framework is being used to inject/wire dependencies.

If your MyService is not being injected into the revision listener then there are few things to check:

1. Verify that you're using Spring Framework 5.1 or later.
   While other spring components may use differing version schemes, its important to make sure that the underlying Spring Framework version is indeed 5.1+.
2. Is the RevisionListener configured correctly?
   I typically configure this by adding a @RevisionEntity annotated class with the @Entity annotation and then specify the listener in the @RevisionEntity annotation's value attribute. If you'd rather, you should be able to use org.hibernate.envers.revision_listener to specifying the fully qualified class name of the listener class otherwise.
3. Is your MyService injectable in any other spring bean?
   Perhaps the issue here is that Spring simply isn't constructing your MyService bean in the first place, which would lead to the dependency injection not supplying an implementation during bean injection of the revision listener.

I have created a small demo here that you can reference. I will look into publishing a blog post about this on the Hibernate blog later in the month.

UPDATE

Just looking at the Spring Framework source briefly, I believe the issue is that you're manually creating a LocalContainerEntityManagerFactoryBean, which when the bean factory gets injected, does not actually create the necessary Hibernate configuration for dependency injection to happen.

What I think you may need to do is manually set this yourself: