topic Re: Calling spring bean from alfresco activiti process in Alfresco Archive

Calling spring bean from alfresco activiti process

younis15 — Wed, 26 Oct 2011 08:36:04 GMT

Within alfresco activiti, could I call a spring bean using the servicetask like :<serviceTask id="assignApplicationId" name="Assign Application Id" activiti:expression="${sequenceUtil.getOutboundId(task.id)}" activiti:resultVariable="OutboundWF_ApplicationNumber"/>however, in my custom con

Re: Calling spring bean from alfresco activiti process

younis15 — Wed, 26 Oct 2011 13:36:40 GMT

I got it

I have to override the activitiProcessEngineConfiguration bean to include my custom bean within beans property


<!– –>
<!– Activiti Process Engine –>
<!– –>
<bean id="activitiProcessEngineConfiguration"
    class="org.alfresco.repo.workflow.activiti.AlfrescoProcessEngineConfiguration">
    <property name="dataSource" ref="wrappedDataSource" />
    <property name="transactionManager" ref="transactionManager" />
    <property name="databaseSchemaUpdate" value="${db.schema.update}" />
    <property name="history" value="full" />
    <property name="jobExecutorActivate" value="true" />

<!– Limit the visible beans in expressions –>


<property name="beans">
    <map>
        <entry key="services" value-ref="ServiceRegistry" />
        <entry key="sequenceUtil" value-ref="sequenceUtil" />
    </map>    
</property>

    <property name="customTypes">
        <list>
            <ref bean="activitiScriptNodeType" />
            <ref bean="activitiScriptNodeListType" />
        </list>
    </property>
    <property name="customPreBPMNParseListeners">
        <list>
            <ref bean="activitiParseListener" />
        </list>
    </property>
</bean>
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: Calling spring bean from alfresco activiti process

amandaluniz_z — Thu, 12 Jan 2012 12:08:45 GMT

Hello,

Have the same problem. Following Nick Smith's slides, it should be enough extending the BaseJavaDelegate, but it's not…. still facing the same issue. Hope the Alfresco 4 release (not the beta one) solves this problem….

http://www.alfresco.com/resources/devcon2011/sandiego/BPM-3_AdvancedWorkflowDeeperDive_Smith.pdf