e Exchange into your beans you are still coupling to
the framework. These DTOs can be held, persisted or trashed independent of
any Camel concerns. To Camel they are just the "body" carried along by the
exchange.
--
View this message in context:
http://camel.465427.n5.nabble.com/Ev
m with a little more information on why this is
a bad design. Can I tell them that Camel is managing the threads, and it's
not a good idea to rely on one particular thread being used throughout the
lifespan of a single synchronous route?
--
View this message in context:
http://camel.46542
makes what we intended impossible?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/EventNotifierSupport-and-Threads-tp5780279.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
.
Is what we're doing just plain wrong? Is Camel managing threads in a way
that makes what we intended impossible?
--
View this message in context:
http://camel.465427.n5.nabble.com/EventNotifierSupport-and-Threads-tp5780279.html
Sent from the Camel - Users mailing list archive at Nabble.com.
