Hi Gerald,
Maybe more direct-vm (sync, whereas VM is like SEDA, so async).
Most of the time, I have the "exposing" REST API in one route that
target a "impl" route using direct-vm (where I have my processor, etc).
I split both in separate bundle. The good thing about that is that I can
change the
Dear community,
I wonder whether the VM component will be a good practice to define functional
consumer endpoints for a REST definition in another Camel Context? Background
.. I‘d like to decouple an API implementation from the API definition.
Any hints are welcome.
Sent by my mobile device
-