Support for Camel tasks in Alfresco 4.x

arnoldschrijve1 — Thu, 28 Mar 2013 16:37:50 GMT

I am trying to define a workflow with some Camel Tasks in Alfresco (EE 4.1.1.3) and I am running into trouble.For the Camel integration I followed the instructions in the 'Activiti in Action' book, added activiti-camel Maven reference, added a camelContext to the bean definitions of my AMP module, a

Re: Support for Camel tasks in Alfresco 4.x

arnoldschrijve1 — Tue, 09 Apr 2013 16:28:33 GMT

For those of you who bounce against the same problem: I solved the issue by not using Spring to create the CamelContext. Instead I created a CamelContextFactory class that instantiates the context and wire that up as a bean. Below is a simplified example that demonstrates this. You'll probably want a more flexible means of loading the routes.

[java]

package com.yourcompany.activiti.camel;

import org.activiti.camel.ActivitiComponent;
import org.apache.camel.CamelContext;
import org.apache.camel.LoggingLevel;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.impl.DefaultCamelContext;

public class CamelContextFactory {

    private CamelContext camelContext;

    public CamelContext getCamelContext() throws Exception {
        if (camelContext == null) {
            camelContext = new DefaultCamelContext();

            try {
                camelContext.addComponent("activiti", new ActivitiComponent(camelContext));

                // Add the camel routes
                camelContext.addRoutes(new RouteBuilder(camelContext) {

                    @Override
                    public void configure() throws Exception {

                        from("activiti://CamelTest:camelTask1")
                            .setBody().properties()
                            .to("mock:result");
                    }
                });

                camelContext.start();
            } catch (Exception e) {
                // TODO: Do something with the exception.
                throw e;
            }
        }

        return camelContext;
    }
}

[/java]

In the context-file in your AMP (or in extensions directory if you use that):



<beans xmlns="http://www.springframework.org/schema/beans" 
       xmlns:camel="http://camel.apache.org/schema/spring"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
       xsi:schemaLocation="http://www.springframework.org/schema/beans 
                               http://www.springframework.org/schema/beans/spring-beans.xsd
                           http://camel.apache.org/schema/spring
                               http://camel.apache.org/schema/spring/camel-spring-2.5.0.xsd">

    <!– Creating a Camel context like this results in an error in Alfresco (in EE 4.1.1.3 at least).   
    <camelContext id="camelProcess" xmlns="http://camel.apache.org/schema/spring">
        <packageScan>
            <package>com.yourcompany.activiti.camel</package>
        </packageScan>
    </camelContext –>
    
    <bean id="camelContextFactory" class="com.yourcompany.activiti.camel.CamelContextFactory" />
    
    <bean id="camelContext" factory-bean="camelContextFactory" factory-method="getCamelContext" />

    <!– Extend CamelBehavior. Need to pass the Activiti bean registry. –>
    <bean id="camel" class="com.yourcompany.activiti.camel.CamelActivityBehaviour">
        <constructor-arg index="0">
            <value>camelTaskHandler</value>
        </constructor-arg>
        <constructor-arg index="1">
            <list>
                <bean class="org.activiti.camel.SimpleContextProvider">
                    <constructor-arg index="0" value="CamelTest" />
                    <constructor-arg index="1" ref="camelContext" />
                </bean>
            </list>
        </constructor-arg>
        <property name="beanRegistry" ref="activitiBeanRegistry" />
    </bean>
</beans>

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

As you can see we also need an extension of the CamelBehaviour in the activiti-camel jar. The Activiti engine in Alfresco uses a separate bean registry to which the camel bean must be added in order to make it available to the delegateExpresion in the camel serviceTask. The name to use in the expression is passed as well ('camelTaskHandler').

[java]

package com.yourcompany.activiti.camel;

import java.util.Collection;
import java.util.Map;

import org.activiti.camel.CamelBehaviour;
import org.activiti.camel.ContextProvider;

public class CamelActivityBehaviour extends CamelBehaviour {

    private String delegateExpressionBeanName;

    public CamelActivityBehaviour(String delegateExpressionName, Collection<ContextProvider> camelContext) {
        super(camelContext);
        this.delegateExpressionBeanName = delegateExpressionName;
    }

    /**
     * Register the CamelActivityBehaviour instance in the Activiti bean registry.
     */
    public void setBeanRegistry(Map<Object, Object> beanRegistry)
    {
        beanRegistry.put(getDelegateExpressionBeanName(), this);
    }

    protected String getDelegateExpressionBeanName()
    {
        return delegateExpressionBeanName;
    }
}

[/java]

Finally the workflow definition to test it all out:



    <process id="CamelTest" name="Camel Test: A Camel task in an Alfresco workflow">

        <startEvent id="start" />

        <sequenceFlow id="startup" sourceRef="start" targetRef="camelTask1"/>

        <serviceTask id="camelTask1" activiti:delegateExpression="${camelTaskHandler}" />

        <sequenceFlow id='flowToEnd' sourceRef='camelTask1' targetRef='end' />

        <endEvent id="end" />

    </process>

‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Hope this may have been helpful for you!

topic Re: Support for Camel tasks in Alfresco 4.x in Alfresco Archive

Support for Camel tasks in Alfresco 4.x

Re: Support for Camel tasks in Alfresco 4.x