Sadly, we still have a problem and I’ve no idea what to do about it. Removing the “@ProcessApplication” from the Java “implementation” class caused Camunda to ignore the deployment, even though it was successfully deployed to WildFly.
Following is source code from that file. I am not the developer, but my testing indicates that a class such as this isn’t necessary for Camunda to recognize a process. This is clearly something we are doing wrong, because the pizza-order example doesn’t have “@ProcessApplication” anywhere in the code. If you need other parts of the actual deployment, let me know and I’ll ask if I can send it (it contains proprietary code, so I would only be able to send it to a non-public, secure endpoint).
package com.att.gcs.bizops.cop.core.template.messagehandler;
import org.camunda.bpm.application.ProcessApplication;
import org.camunda.bpm.application.impl.ServletProcessApplication;
import org.camunda.bpm.engine.delegate.ExecutionListener;
@ProcessApplication(“MessageHandler”)
public class MessageHandlerApplication extends ServletProcessApplication{
public ExecutionListener getExecutionListener() {
return new ActivityLoggingExecutionListener();
}
}