Hi Jothi,
> Could anyone please let me know of a
> practical example where the direct component would be a good fit?
As a addition to what Willem wrote I would mention "abstraction".
If you work on big Camel project spread across independent development
teams, you can define contracts between routes with "direct" and
"seda".
For example you, as tech lead of the transformation module team, could
define the following route...
from("direct:transform").to(...some complex transformation routing
goes here...).to("seda:transformed");
...and say to the tech lead of the team consuming your transformation
route - "If you want your message to be transformed, send it to the
direct:transform endpoint. Results can be picked from the
seda:transformed queue.".
This approach is a life saver in the case of the geographically spread
teams with different timezones working on the same deployable artifact
:) .
Best regards.
--
Henryk Konsek
http://henryk-konsek.blogspot.com
