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.

Deploying in Tomcat

walterjs

Hi there,

I've been running the process engine using spring and now I want to deploy this to the tomcat instance where the activiti-rest webapp is deployed. I renamed my "main" spring config file to activiti.cfg.xml and removed the original activit-cfg.jar from the activiti-rest/WEB-INF/lib dir and the activiti-explorer works perfectly.

The problem is that none of my spring beans are instantiated. Doing a remote debug, I see all the beans and I can even reference them (then they are created) during this session. But my jms listener, for instance, is not started:

    <bean class="org.springframework.jms.listener.DefaultMessageListenerContainer">
        <property name="destination" ref="topic"/>
        <property name="connectionFactory" ref="connectionFactory"/>
        <property name="messageListener" ref="connector"/>
    </bean>
‍‍‍‍‍‍‍

My standalone server consists of the following line in the main method:

new ClassPathXmlApplicationContext("applicationContext.xml")‍

I've also deployed this in my own standalone webapp in the same container (everything starts up fine using an ApplicationContextListener), but I'm not sure how to get the rest webapp to use my spring configured engine. Modifying the rest webapp web.xml sounds wrong to me.

Any help would be appreciated.

Thanks
Walter

Find more posts tagged with

Comments

frederikherema1

Walter,

Can you show how exactly you use/configure/startup your process-engine?

walterjs

I presume you want to see my spring config. Here is the relevant section:

<br>&nbsp;&nbsp;&nbsp; <bean id="processEngine" class="org.activiti.spring.ProcessEngineFactoryBean"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="processEngineConfiguration" ref="processEngineConfiguration" /><br>&nbsp;&nbsp;&nbsp; </bean><br><br>&nbsp;&nbsp;&nbsp; <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="databaseType" value="h2"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="dataSource" ref="dataSource"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="transactionManager" ref="transactionManager"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="mailServerHost" value="localhost"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="mailServerPort" value="5025"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="jpaHandleTransaction" value="true"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="jpaCloseEntityManager" value="true"/><br>&nbsp;&nbsp;&nbsp; </bean><br><br>&nbsp;&nbsp;&nbsp; <bean id="dataSource" class="org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="targetDataSource"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <bean class="org.springframework.jdbc.datasource.SimpleDriverDataSource"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="driverClass" value="org.h2.Driver"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="url" value="jdbc:h2:tcp://localhost/activiti"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="username" value="sa"/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="password" value=""/><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </bean><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </property><br>&nbsp;&nbsp;&nbsp; </bean><br><br>&nbsp;&nbsp;&nbsp; <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager"><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <property name="dataSource" ref="dataSource"/><br>&nbsp;&nbsp;&nbsp; </bean><br><br>

As I said, this all starts up fine, it is the rest of my beans (most notably the jms listener) that do not start.

Thanks
Walter

frederikherema1

Walter,

There seems to be nothing wrong with your configuration, but the way it is used is a bit different than you would expect.

Since you renamed your spring-config file to activiti.cfg.xml, this will be picked up by the rest-webapp's ContextListener. This will read this configuration (using spring), but will only use the bean 'processEngineConfiguration'.

It's indeed a bit confusing, but in the case of activiti.cfg.xml, spring is only used to wire the configuration. We take advantage of spring-bean functionalities to read configuration, since we don't want to reinvent the wheel and write our ow IOC-container. check out http://activiti.org/userguide/index.html#configurationRoot for more info in the configuration.

walterjs

Ok, thanks.

Could you please let me know the preferred way of deploying the spring beans? When I complete a task (by submitting a form) through the activiti-explorer, how would a subsequent serviceTask evaluate an expression that refers to one of the beans in my spring configuration?

Here is my process for reference:

<br><?xml version="1.0" encoding="UTF-8"?><br><definitions xmlns="<a href="http://www.omg.org/spec/BPMN/20100524/MODEL" rel="nofollow noopener noreferrer">http://www.omg.org/spec/BPMN/20100524/MODEL</a>"<br> xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance" rel="nofollow noopener noreferrer">http://www.w3.org/2001/XMLSchema-instance</a>" xmlns:activiti="<a href="http://activiti.org/bpmn" rel="nofollow noopener noreferrer">http://activiti.org/bpmn</a>"<br> typeLanguage="<a href="http://www.w3.org/2001/XMLSchema" rel="nofollow noopener noreferrer">http://www.w3.org/2001/XMLSchema</a>" expressionLanguage="<a href="http://www.w3.org/1999/XPath" rel="nofollow noopener noreferrer">http://www.w3.org/1999/XPath</a>"<br> targetNamespace="<a href="http://www.activiti.org/test" rel="nofollow noopener noreferrer">http://www.activiti.org/test</a>"><br> <process id="ModelTest" name="ModelTest"><br>&nbsp; <startEvent id="startevent1" name="Start"></startEvent><br>&nbsp; <userTask id="usertask1" name="Review"<br>&nbsp;&nbsp; activiti:candidateGroups="accountancy" activiti:formKey="approval.form"></userTask><br>&nbsp; <userTask id="usertask2" name="Approve"<br>&nbsp;&nbsp; activiti:candidateGroups="manager" activiti:formKey="approval.form"></userTask><br>&nbsp; <sequenceFlow id="flow1" name="" sourceRef="startevent1"<br>&nbsp;&nbsp; targetRef="usertask1"></sequenceFlow><br>&nbsp; <exclusiveGateway id="exclusivegateway1" name="Exclusive Gateway"></exclusiveGateway><br>&nbsp; <sequenceFlow id="flow2" name="" sourceRef="usertask1"<br>&nbsp;&nbsp; targetRef="exclusivegateway1"></sequenceFlow><br>&nbsp; <sequenceFlow id="flow4" name="" sourceRef="exclusivegateway1"<br>&nbsp;&nbsp; targetRef="endevent1"><br>&nbsp;&nbsp; <conditionExpression xsi:type="tFormalExpression"><![CDATA[${!approved}]]></conditionExpression><br>&nbsp; </sequenceFlow><br>&nbsp; <exclusiveGateway id="exclusivegateway2" name="Exclusive Gateway"></exclusiveGateway><br>&nbsp; <sequenceFlow id="flow5" name="" sourceRef="usertask2"<br>&nbsp;&nbsp; targetRef="exclusivegateway2"></sequenceFlow><br>&nbsp; <sequenceFlow id="flow7" name="" sourceRef="exclusivegateway1"<br>&nbsp;&nbsp; targetRef="usertask2"><br>&nbsp;&nbsp; <conditionExpression xsi:type="tFormalExpression"><![CDATA[${approved}]]></conditionExpression><br>&nbsp; </sequenceFlow><br>&nbsp; <sequenceFlow id="flow8" name="" sourceRef="exclusivegateway2"<br>&nbsp;&nbsp; targetRef="endevent1"><br>&nbsp;&nbsp; <conditionExpression xsi:type="tFormalExpression"><![CDATA[${!approved}]]></conditionExpression><br>&nbsp; </sequenceFlow><br>&nbsp; <serviceTask id="servicetask1" name="Retry"<br>&nbsp;&nbsp; activiti:expression="#{myBean.invoke()}"></serviceTask><br>&nbsp; <sequenceFlow id="flow9" name="" sourceRef="exclusivegateway2"<br>&nbsp;&nbsp; targetRef="servicetask1"></sequenceFlow><br>&nbsp; <sequenceFlow id="flow10" name="" sourceRef="servicetask1"<br>&nbsp;&nbsp; targetRef="endevent1"></sequenceFlow><br>&nbsp; <endEvent id="endevent1" name="End"></endEvent><br> </process><br></definitions><br>

walterjs

Ok, I've got this to work by changing org.activiti.engine.ProcessEngineConfiguration.

<br>&nbsp; protected static ProcessEngineConfiguration parseProcessEngineConfiguration(Resource springResource, String beanName) {<br>&nbsp;&nbsp;&nbsp; DefaultListableBeanFactory beanFactory = new DefaultListableBeanFactory();<br>&nbsp;&nbsp;&nbsp; XmlBeanDefinitionReader xmlBeanDefinitionReader = new XmlBeanDefinitionReader(beanFactory);<br>&nbsp;&nbsp;&nbsp; xmlBeanDefinitionReader.setValidationMode(XmlBeanDefinitionReader.VALIDATION_XSD);<br>&nbsp;&nbsp;&nbsp; xmlBeanDefinitionReader.loadBeanDefinitions(springResource);<br>&nbsp;&nbsp;&nbsp; GenericApplicationContext ctx = new GenericApplicationContext(beanFactory); // <&ndash; new<br>&nbsp;&nbsp;&nbsp; ctx.refresh(); // <&ndash; new<br>&nbsp;&nbsp;&nbsp; return (ProcessEngineConfiguration) ctx.getBean(beanName);<br>&nbsp; }<br>

I added the two lines to be able to refresh the context.

Now my deployed processes can access spring variables in expressions when running from inside the tomcat container.

Please let me know if this was the original intention or if I'm just not deploying this as you would recommend.

Thanks
Walter

walterjs

Changing the subject to hopefully get a response

tombaeyens

Walter,

Can you explain how refreshing the context is related to the visibility of beans in expressions? I didn't get that part.

walterjs

Thanks for your reply Tom,

I'm not sure why this is happening, but without those lines of code I added (refreshing the context), my process fails when it tries to execute the expression referencing my spring configured bean. In addition to that, any of the beans that should be started up automatically, don't (for example my JMS listener).

Is this the way to deploy my spring context to be used by activiti-explorer? Should I rename my spring context to activiti.cfg.xml and replace the activiti-cfg.jar in the rest webapp lib directory with my own set of jars and dependencies?

Thanks
Walter