-
Feature Request
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
- replaces SpringProcessEngineConfgiuration auto-deployment mechanism
- supports the currently exposed application properties
- resource scanning: classpath resources get environment-independent names
- the deployment should be made before any other @PostConstruct callbacks are made for custom beans (those might already reference the deployed resources, e.g. start a process instance)
- @EnableProcessApplication works just as before
This is the controller panel for Smart Panels app
- is depended on by
-
CAM-9906 Expose more deployment properties in non-process-application setup
- Open
-
CAM-9452 Testing Spring Boot Applications: Support application context caching
- Closed
-
CAM-9903 I can use embedded forms with a non-process-application deployment
- Closed
-
CAM-9904 Register engine as MBean in non-process-application scenario
- Closed
-
CAM-9905 I can make multiple deployments in non-process-application setup
- Closed
-
CAM-9907 I can programmatically add resources to a deployment
- Closed
-
CAM-9909 I can read a migration guide if I use process application deployments
- Closed
-
CAM-9908 Deprecate process-application-style deployment
- Closed
- is related to
-
CAM-8109 Replace processes.xml with ApplicationProperty
- Closed
-
CAM-10623 Spring Boot application property is removed
- Closed
- links to