openpj / activiti-sdk Goto Github PK

We have to find a way to prevent the packaging process of the Activiti Admin for both the WAR and the Docker container.
Typically you need to build the Activiti Admin just for the first time and then we can consider the same build valid for any new Docker run.

We need to add the section for configuring the pluginGroups for io.fabric8 in the settings.xml

In the Docker configuration there is a wrong setting for aps-contentstore-volume that should be updated with activiti-contentstore-volume

Currently we have the Activiti webapps including very old libraries, it would be great to update them in order to fix all the vulnerabilities.

It would be great to add a task listener example implementation

It seems that tomcat8-jdk11-openjdk container was updated and now we need to update the jackson libraries included in the activiti-rest.war

If we need to declare Spring annotations for implementing Java delegates that we want to use as delegate expressions, we don't have the availability of the Spring Context classes in the classpath.

We need a file appender for Log4j, currently the Activiti Engine is not logging into the standard output.

We should add a new Maven module for generating the Swagger client using the Open API specs provided by the activiti-rest.war

We need to share the default Java packages enabled in Spring for the ComponentScan.
In this way any developer can put his own Spring Beans annotated with @service or @component without declaring a configuration class.

For the current version of Activiti currently included in the bundle we have the following default extensions points:

• org.activiti.app.extension.conf: custom configuration classes for Activiti App
• org.activiti.app.extension.bean: custom Spring beans (delegates etc.) for Activiti App
• org.activiti.rest.conf: custom Spring beans (delegates etc.) for Activiti Rest
• classpath:activiti-custom-context.xml: custom Spring context for Activiti Rest

We need to expose a port for remote debugging purpose