To be more precise: the activiti-rest webapp uses a Spring appliation context to configure itself.
The engine however, is not configured in Spring. There is an activiti.cfg.jar placed on the classpath, containing a process engine configuration for which the engine is called 'default'.
The process engine is then referenced in the Spring context using the 'default' name.
If you want to tweak the activiti-rest webapp, and you want to use Spring you'll have to
- remove the activiti.cfg.jar or any other activiti.cfg.xml on the classpath
- add your process engine configuration to the applicationcontext (webapplicationtext.xml) of the activiti-rest webapp.