On Fri, Feb 8, 2013 at 10:44 PM, Harald Wellmann <[email protected]> wrote: > 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. >
I dont think so. The WorkManager is for any kind of work task. http://www.jcp.org/en/jsr/detail?id=237 But it seems the spec was withdrawn in 2008 http://glassfish.java.net/nonav/javaee5/api/javax/resource/spi/work/package-summary.html http://commonj.myfoo.de/jsr237-api/commonj/work/WorkManager.html > >> 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 > > -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
