Steps to reproduce
Please see the engine integration test.

1) Create an EAR accordingly:

 test-application.ear
       |-- pa.jar
           |-- AnnotatedEjbPa.class
           |-- process.bpmn
           |-- deployment-descriptor-with-custom-filename.xml
           |-- META-INF/beans.xml

The class AnnotatedEjbPa extends EjbProcessApplication and has an @ProcessApplication annotation which specifies the path of the deployment descriptor via the deploymentDescriptors attribute.

2) Deploy the EAR to WLS

Expected behavior
The process.bpmn is deployed to the engine as the deployment descriptor is specified via @ProcessApplication

Observed behavior
The process.bpmn is not deployed to the engine

Hint

• WLS generates and uses a subclass of AnnotatedEjbPa
• The engine tries to find the @ProcessApplication annotation on the subclass which cannot be found as it is set on the superclass
• Please see the following code line: https://github.com/camunda/camunda-bpm-platform/blob/master/engine/src/main/java/org/camunda/bpm/container/impl/deployment/ParseProcessesXmlStep.java#L117