Once you have Camunda running within an application server, in my context I use JBoss/WildFly, new projects and/or updates will trigger Camunda to update its repository.
For example:
- Startup your application server hosting Camunda. This is the complete platform downloaded from Camunda (though you can also build this yourself).
example on Linux: ./bin/standalone.sh <<< from the WildFly directory
1a) Add an “admin” user for Wildfly/JBoss.
example: ./bin/add-user.sh <<< it will ask a series of questions (let me know if you have any questions with this: for development… i keep it very simple)
-
Add and configure JBoss Tools (eclipse plugin) within Eclipse. I use Eclipse neon. Make sure you match the ports to your running server.
-
Add the server to the Eclipse “servers” view. Make sure you set to “Server lifecycle is externally managed” - this helps speed server resets and deployments up. For development, I may “halt” the server and I don’t want to wait for Eclipse - I go directly to the server and send a “kill” signal if it’s not responding (note: I use a Linux and Win7 combination)
-
From the eclipse “servers” view, “add” your Camunda project and deploy. If anything changes in your camunda project, you can set the eclipse “server” adapter to automatically publish if anything changes in your eclipse project. This is an excellent feature! It helps me keep an eye on potential model issues.
NOTE: This approach also works with Tomcat. But, once you become familiar with Java’s CDI… you’ll get hooked on Camunda’s “camunda-archetype-ejb-war” archetype.