the job executor descriptor seems like a wrong hack to me. what was the motivation to start thinking of this solution ?
maybe i can help come up with a better way to do it.
The motivation was the auto-start attribute for the jobExecutor. If the user don't want to manually start it, he expects it to be stopped automatically.
In order to do so, I added a listener on the environmentFactory (as for HibernateSessionFactory) to stop the jobExecutor when the application context is closed.