AFAIK, WorkManager is only meant to be used in resource adapter/JCA
connector implementations. It should not be used by application code as
an Executor substitute.
the best is to get resources from where you need (lookup, BeanProvider from
deltaspike...) with a correct scope (not requestscoped for instance which
has no real sense in such a thread)
That's just why I suspect Camel (S)JMS is not be fully Java EE compatible.
In an MDB, CDI request scope is active by default, with well-defined
behaviour.
This won't work in a thread created by Camel or any other application
component.
Best regards,
Harald
