[CAM-7905] Document limitations for deployments by the REST API in JBoss/Wildfly environment Created: 06/Jun/17  Updated: 17/Nov/17  Resolved: 27/Oct/17

Status: Closed
Project: camunda BPM
Component/s: documentation
Affects Version/s: None
Fix Version/s: 7.8.0, 7.8.0-alpha6

Type: Task Priority: L3 - Default
Reporter: Sebastian Menski Assignee: Yana Vasileva
Resolution: Fixed Votes: 0
Labels: SUPPORT
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: 0 minutes

Issue Links:
Related

 Description   

If a process is deployed using the REST API in a JBoss/Wildfly environment it is not possible to use Spin in scripts. As there is no module dependency of spin defined in the engine module. It may be possible that the same is true for connect.



 Comments   
Comment by Thorben Lindhauer [ 07/Jun/17 ]

Is this related to CAM-7579? I.e. should those cases be handled consistently?

Comment by Sebastian Menski [ 07/Jun/17 ]

CAM-7579 is about accessing SpinPlugin classes inside a process application. This ticket describes that a user cannot access the spin classes (not spin plugin) inside the engine it self, without a process engine. For example a process which is deployed using the REST API and executed by the job executor. Fun fact in the later case the SpinPlugin classes should be accessible at the moment. Also this ticket is about documenting the limitations, the other about removing them.

So if we want to remove these limitation, rather then documenting them, we probably should align what is possible in the engine and in a process application.

Generated at Sat May 25 21:34:14 CEST 2019 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.