topic Re: JBoss 7 EAP compatibility for Activiti v5.11 - 5.19? in Alfresco Archive

JBoss 7 EAP compatibility for Activiti v5.11 - 5.19?

ag91375 — Fri, 16 Dec 2016 22:11:33 GMT

We are doing the analysis on migrating Activiti 5.11 from WebLogic 12.1.2 to JBoss 7 EAPWould anyone be able to confirm if Activiti versions v5.11 - 5.19 are compatible with JBoss 7 EAP?

Re: JBoss 7 EAP compatibility for Activiti v5.11 - 5.19?

gdharley — Mon, 19 Dec 2016 16:51:40 GMT

Based on the details on JBoss here: https://access.redhat.com/articles/113373
I believe the important specs for Activiti are the supported version of Java and the servlet spec.

You are asking about versions 5.11 through 5.19 and to be honest, Activiti switched from using Restlet based Rest services to Spring MVC (this was around 5.16...I know because it broke a number of our features).

However, either way, JBoss 7 supports all of the necessary specs.
It may not be a seamless move, meaning, you may need to recode some of your custom features, but the engine itself will work fine.

Hope this helps,
Greg

‌

Re: JBoss 7 EAP compatibility for Activiti v5.11 - 5.19?

ag91375 — Mon, 19 Dec 2016 21:01:29 GMT

Thank you for your reply. We are not using the Activiti REST web services, so we should be sine regarding that.

JBoss offers a tool called Widup which analyzes application artifacts (such as Java code, JSPs and XML) and produces an HTML report highlighting areas that require changes.

http://windup.jboss.org/

Our application uses the the following libraries, which we analyzed with Windup, which mentioned a few potential issues with activiti-cxf and activiti-engine but none with activiti-spring

activiti-cxf-5.11.jar
activiti-engine-5.11.jar
activiti-spring-5.11.jar

For activiti-cxf-5.11.jar:

One issue was found for: org.activiti.engine.impl.webservice.CxfWSDLImporter, which has an IBM proprietary type (com.ibm.wsdl.extensions.schema.SchemaImpl.getElement())

For activiti-engine-5.11.jar:

One issue categorized as trivial was found for: org.activiti.engine.impl.cfg.ProcessEngineConfigurationImpl, which lookups an object using a JNDI String.

A couple other issues listed as "optional" were listed

1.) Dynamically loaded classes within application. During the migration, multiple classes that are provided on classpath by a different server may not be present anymore.

org.activiti.engine.impl.bpmn.parser.BpmnParse
org.activiti.engine.impl.util.ReflectUtil
org.activiti.engine.impl.db.DbSchemaExport
org.activiti.engine.impl.juel.ExpressionFactoryImpl

2.) Type reference for java.sql.DriverManager

org.activiti.engine.impl.db.DbSchemaExport

3.) No issues found for activiti-spring-5.11.jar

I was not able to attach the respective .zip file reports to this post, but took screenshots which I was able to upload