camunda / camunda-bpm-platform

Flexible framework for workflow and decision automation with BPMN and DMN. Integration with Quarkus, Spring, Spring Boot, CDI.
https://camunda.com/
Apache License 2.0
4.11k stars 1.55k forks source link

resourceRootPath does not work in spring boot app #2454

Open ThorbenLindhauer opened 4 years ago

ThorbenLindhauer commented 4 years ago

This issue was imported from JIRA:

Field Value
JIRA Link CAM-12154
Reporter @garima-camunda
Has restricted visibility comments true

Steps to reproduce

* Build the application 
* Started the application via java -jar <name-of-jar>
* Went to Cockpit->Deployments. I do not not see foo.bpmn in the deployments page
* During application start up, noticed following in the log. 

2020-07-07 15:17:05.613 INFO 2024 --- < main> org.camunda.bpm.container : ENGINE-08024 Found processes.xml file at jar:file:/Users/garima.yadav/eclipse-workspace/sampleproject3/target/sampleproject3.jar!/META-INF/processes.xml 2020-07-07 15:17:05.702 INFO 2024 --- < main> org.camunda.bpm.container : ENGINE-08021 Not creating a deployment for process archive 'camundaApplication': no resources provided. 2020-07-07 15:17:05.707 INFO 2024 --- < main> org.camunda.bpm.container : ENGINE-08050 Process application camundaApplication successfully deployed


* The log statement "Not creating a deployment for process archive 'camundaApplication': no resources provided" tells us that engine actually did not deploy the resources. 

**Actual Behaviour**
The BPMN processes placed in "bpmn" folder does not get deployed

**Expected Behaviour**
The BPMN processes placed in "bpmn" folder should get deployed

**Links:**
* is related to https://jira.camunda.com/browse/SUPPORT-14152
* is related to https://jira.camunda.com/browse/SUPPORT-8106
ThorbenLindhauer commented 4 years ago

This comment was imported from JIRA and written by user @yanavasileva


Doc of resourceRootPath: https://docs.camunda.org/manual/7.13/reference/deployment-descriptors/tags/process-archive/

local to the root of the classpath. By default or if the prefix classpath: is used, the path is interpreted as relative to the root of the classloader. Example: path/to/my/processes or classpath:path/to/my/processes) Doc of spring boot PA: https://docs.camunda.org/manual/7.13/user-guide/spring-boot-integration/process-applications/

Workarounds:

Root cause: Repackaging during the build, details will follow.