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 Contexts and Process Versions

mlueck

HI,

we need to deploy versions of process definitions and make them call Camel Routes of a specific Camel Context that fits the version of that process definition.

So if we deploy another version of that process we would like to also deploy another Camel Context. Instances of that new process definition should only use that new camel Context. Old process Instances should only call the old Camel Context.

I had a look at Apache Service Mix but it seems that this is not yet possible. Am i right or did i overlook something?

Regards,
Michael

Find more posts tagged with

Comments

trademak

Hi Michael,

I think you are right, there's no out-of-the-box solution in place for it. Instead you could use different queue names to make sure the right Camel routes are called maybe.

Best regards,

mlueck

Hi,

thanks for your Reply.

I'm working on an change to the modules activiti-osgi, activiti-camel and the default service-mix default config.

It will make the camel routes call a specific version of processes and also enable the CamelBehaviour to fetch the right CamelContext for that version of the process. I'll send a PullRequest on gibthub as soon as it's finished so you guys can have a look and decide whether you'd like to add it or not.

I'd appreciate it if you will pull it because we can later update to that activiti version and use it of-the-shelf instead of maintaining our own copy/adjustments.

Regards,
Michael