ProcessEngineConfiguration requiring Spring by default?

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

egore911

From what I understood the ProcessEngineConfiguration seems to require Spring for its configuration starting with Activiti 5.0. Is that really necessary to wire a Spring that deep into the engine? Or are there other possibilities to run Activiti without Spring?

Thanks in advance,
Chris

frederikherema1

The engine is indeed using 'spring-beans' dependency for it's configuration. This way we don't have to keep 3 ways of configuration in sync (spring-context, activiti.cfg.xml and programmatic with old ProcessEngineBuilder).

On top of that, this change makes future pluggability extensions of the engine much easier and cleaner. We don't want to write our own DI-container.

To answer your last question: since spring-beans is used in ProcessEngineConfiguration, there is no way of not using spring. But not because spring is used for OUR configuration, that you should use spring to wire your application or get hold of the ProcessEngine, it's still embeddable in non-spring envs.