activiti engine configuration question

[jeff1]

hi, all
    today I run a testcase and find that the activiti engine is built with the resource 'activiti.properties', besides inside the engine-module, I can still find the jbpm4-like(something like wire, binding…) config-file such as 'activiti.cfg.defaults.xml' etc., but the relevant code of wire/binding/descriptor are no longer found.
    I am confused. are the jbpm4-like config files still useful or are they suppose to be deprecated and why?
   
any response would be great appreciated.

[jbarrez]

Hi Jeff,

Indeed the current way to go is with the properties file.
Tom is currently refactoring a lot in the pvm, and I'm sure he will remove the old config files.

The idea for this move it to make it easier for using Activiti within real application that use for example a dependency injection container,
where the container will not need the properties to configure the engine.

[jeff1]

thanks for your response, Joram
did you mean that depending on the different application environments, activiti would set up the engine in different ways with different configuration? e.g. using spring? jbossmc? or guice?

[jbarrez]

Yes, exactly. For example in Spring, the engine would simply be configured as a bean, setting the various properties in the typical Spring way. This also means that you can inject a Springified datasource, transactionManager, etc.