-
Bug Report
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
Not possible:
<?xml version="1.0" encoding="UTF-8"?> <process-application xmlns="http://www.camunda.org/schema/1.0/ProcessApplication" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.camunda.org/schema/1.0/ProcessApplication http://www.camunda.org/schema/1.0/ProcessApplication "> <process-engine name="engine1"> <job-acquisition>default</job-acquisition> <configuration>org.camunda.bpm.engine.impl.cfg.JtaProcessEngineConfiguration</configuration> <datasource>jdbc/ProcessEngine</datasource> <properties> <property name="history">full</property> <property name="jobExecutorDeploymentAware">true</property> <property name="producePrioritizedJobs">true</property> <property name="transactionManagerJndiName">java:appserver/TransactionManager</property> </properties> <plugins> <plugin> <class>org.camunda.spin.plugin.impl.SpinProcessEnginePlugin</class> </plugin> </plugins> </process-engine> <process-archive name="archive1"> <process-engine>engine1</process-engine> <properties> <property name="isDeleteUponUndeploy">true</property> </properties> </process-archive> </process-application>
because the Spin plugin is not reachable from the webapp (it is included in the camunda ear). Bringing it with the webapp itself may not work either, because then there are two versions of DataFormat classes both registered in the shared spin-core library.
This is the controller panel for Smart Panels app
- is related to
-
CAM-4207 Tolerate non-resolving job priority expressions
- Closed