nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Camel Routes Reusability

dasilvai

Is it possible to implement a Camel route (using the Activiti-Camel module) that is not directly connected to a specific service task ID and a Process ID?

Let's say I have a Camel route that needs to be re-used across many different processes and many different service task IDs within each process. Is there any way I could accomplish that?

Many thanks in advance

Find more posts tagged with

Comments

smirzai

hi
As of now it is not possible, but it seems a valid point to me.
Maybe we can add a patemeter route, and when this parameter is set, activiti tries to find the mentioned route instead of the usual name convension way of finding it.

dasilvai

Thanks smirzai, that would be a great feature, since many of the Camel routes might need to be re-used in other process definitions.

We ended up creating a generic service task that can be re-used across multiple processes definitions in combination with RabbitMQ topic exchanges/routing keys. The service task simply connects to a RabbitMQ exchange and sends it a payload consisting of form variables and process instance ID. After the service task is called, we have a "Receive Task" step defined in our flow, which gets completed using a micro-service/micro-ESB we host somewhere else, which listens to a RabbitMQ exchange and sends a "signal" back to an Activiti process instance receive task (via Activiti REST API) whenever we have a new message published in a specific exchange.

Anyway, thanks once again for your help