cancel
Showing results for 
Search instead for 
Did you mean: 

Activiti [5.17.0] Modeler : context Root change not supported

skay
Champ in-the-making
Champ in-the-making
Hi,

The new Activiti Modeler (5.17.0) is wonderful, but does not support changing activiti-explorer.war Context Root Smiley Sad

- Change the name of the application activiti-explorer.war into myactiviti-explorer.war
- Deploy into your container
- Log in / Go to Workbench / new model.
- Modeler cannot display any component/tool/image.

Indeed, context root has been hard coded into a javascript config file :

activiti-explorer.war\editor-app\app-cfg,js

var ACTIVITI = ACTIVITI || {};

ACTIVITI.CONFIG = {
   'contextRoot' : '/activiti-explorer/service',
};

Could this change to something a little more transparent ?
To clarify with a minimal change : this configuration point could be centralized to some file located in WEB-INF/classes

Best Regards
3 REPLIES 3

jbarrez
Star Contributor
Star Contributor
You have indeed to make the change in app-cfg.js.

How would you make it work from WEB-INF/classes? That is a JAVA path, not javascript. How would it know to contact the server … if it doesnt know the correct root to get the info from?

skay
Champ in-the-making
Champ in-the-making
Well, this wasn't necessary on <5.16.4
…and this is a proposal for a workaround.
By the way I still encounter an issue;
Opening the Modeler for a deployed process (nb Edit Process button) forwards to a white page with this workaround.
Back to the workspace (back browser, I can see the editable entry created.
If I select that entry it's ok and Modeler appears with the editable view of the process.
So it seems that the context configuration isn't centralized to that file.

jbarrez
Star Contributor
Star Contributor
> Well, this wasn't necessary on <5.16.4

No; because this was a version with a lot less features. Feel free to use the older version if you believe it is superior.

> …and this is a proposal for a workaround.


My point is that is isnt a workaround, as the javascript has no way of accessing the WEB-INF/classes


> Opening the Modeler for a deployed process (nb Edit Process button) forwards to a white page with this workaround.


I would need to check that, and if it is like that, then it is bugged.