M2eclipse updating maven dependencies

After downloading the Activiti UI WAR file from the Activiti website, follow these steps to get the demo setup running with default settings.You’ll need a working Java runtime and Apache Tomcat installation (actually, any web container would work since we only rely on the servlet capability. Note that the Activiti UI app demo setup is a way of showing the capabilities and functionality of Activiti as easily and as fast as possible.The instructions below will work for Tomcat, but for other container applications, please refer to the documentation for your container app.If using Tomcat, the JNDI resource is configured within $CATALINA_BASE/conf/[enginename]/[hostname]/[warname](for the Activiti UI this will usually be $CATALINA_BASE/conf/Catalina/localhost/activiti-app.xml).Note that the configuration XML is in fact a Spring configuration.

The following chapters will help you to get familiar with how to use Activiti programmatically in your environment: file on the classpath and construct an engine based on the configuration in that file.The default context is copied from the Activiti war file when the application is first deployed, so if it already exists, you will need to replace it.To change the JNDI resource so that the application connects to My SQL instead of H2, for example, change the file to the following: However, often only database administrators can execute DDL statements on a database.This isn’t always ideal because it requires users to either modify the db.properties in the Activiti source and recompile the war file, or explode the war and modify the db.properties on every deployment.By using JNDI (Java Naming and Directory Interface) to obtain the database connection, the connection is fully managed by the Servlet Container and the configuration can be managed outside the war deployment.