There is our final implementation (see attached document). Definition of the strategy into the Spring context:
<bean id="wasExecutorServiceStrategy" class="threadmanager.WasExecutorServiceStrategy"> <property name="executor"> <bean class="org.springframework.jndi.JndiObjectFactoryBean"> <property name="jndiName" value="java:comp/env/wm/wasWorkManager" /> <property name="resourceRef" value="true" /> </bean> </property> </bean> The local JNDI resource "wm/wasWorkManager" should be declared into the web.xml file The object from JNDI should be a commonj.work.WorkManager provided by Websphere Our executor service strategy extends the DefaultExecutorServiceStrategy and replace each call to the Camel ExecutorServiceHelper by calls to our own WasExecutorServiceHelper. This helper generate Camel threads wrapped into a custom thread delegating its work to the Websphere WorkManager. In conclusion, all the Camel threads are delegated to the Websphere WorkManager and so it is possible to acceed to the JNDI context from the threads! http://camel.465427.n5.nabble.com/file/n2261530/src.zip src.zip -- View this message in context: http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p2261530.html Sent from the Camel - Users mailing list archive at Nabble.com.
