feel free to take a look at the source
https://github.com/pax95/camel-commonj
/preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p5505751.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thanks,
> Adi
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p5501345.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
.
Any clarification on this is greatly appreciated.
Thanks,
Adi
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p5501345.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Also note that the same scheme exists for spring OOTB where the TaskExecutor
is the abstraction on top of all of these.
2011/5/6 Claus Ibsen
> On Fri, May 6, 2011 at 4:54 PM, Tarun Ramakrishna
> wrote:
> > Actually this could have been simply solved if camel core and all
> > camel components de
On Fri, May 6, 2011 at 4:54 PM, Tarun Ramakrishna wrote:
> Actually this could have been simply solved if camel core and all
> camel components delegated their threading needs to a
> java.util.concurrent.ThreadFactory. Then one could have centralized
> thread management. Unfortunately even if Came
Actually this could have been simply solved if camel core and all
camel components delegated their threading needs to a
java.util.concurrent.ThreadFactory. Then one could have centralized
thread management. Unfortunately even if Camel is well behaved many of
its components are not and even associat
?
Should I create a ticket ?
/Preben
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p4375711.html
Sent from the Camel - Users mailing list archive at Nabble.com.
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-serv
e threads managed by WebSphere.
> Thanks
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p2261485.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
Apac
OK... so there was a mistake into my implementation of the strategy...
Now, my executorStrategyService works great with websphere
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-RE-Usage-of-server-managed-thread-of-Websphere-tp2259287p2261485.html
Sent from the
Hi
Since you extend existing Camel code, then some logic of Camels is
still being in use.
Camel uses a naming pattern to apply thread names.
You can set a thread name which implies WebSphere for example
See the setThreadNamePattern method
On Fri, Jul 30, 2010 at 10:18 AM, chaillon wrote:
>
>
11 matches
Mail list logo