topic Re: Activiti Integration with Apache Camel - Variable Pollution. in Alfresco Archive

Activiti Integration with Apache Camel - Variable Pollution.

njames — Tue, 03 Jun 2014 20:29:17 GMT

Hi,I am finding increasing problems with Camel's internal properties being (implicitly) brought into Activiti as process variables. I make extensive use of the copyVariablesFromProperties=true parameter on the Activiti Consumer URL.Unfortunately, this parameter results in a number of process variabl

Re: Activiti Integration with Apache Camel - Variable Pollution.

trademak — Wed, 04 Jun 2014 14:54:56 GMT

Hi Nick,

1. It's something in the middle probably. If you use the copyVariablesFromProperties configuration then all Camel properties will be made into variables. Is one of the other configurations not what you are looking for? Do you need one of these properties to be copied as variable? The CamelMessageHistory issue will be solved today on the Github master version.

2. We could define a pluggable way to define properties you want to ignore. Although it makes sense to ignore the Camel properties by default.

Best Regards,

Re: Activiti Integration with Apache Camel - Variable Pollution.

smirzai — Tue, 21 Oct 2014 12:25:58 GMT

Hi
For this specific problem, I have already created a jira issue and will soon implement it.
https://jira.codehaus.org/browse/ACT-2135

Re: Activiti Integration with Apache Camel - Variable Pollution.

shibaevv — Mon, 23 Nov 2015 22:50:31 GMT

I've fixed this by adding interceptor to camel context:
    <camelContext id="camelContext" xmlns="http://camel.apache.org/schema/spring">
        <intercept>
            <removeProperty propertyName="CamelMessageHistory" />
        </intercept>
    </camelContext>

Re: Activiti Integration with Apache Camel - Variable Pollution.

shibaevv — Mon, 23 Nov 2015 22:52:39 GMT