topic configuration refactoring towards spring beans xml in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35506#M18647 <HTML><HEAD></HEAD><BODY><SPAN>Hi,</SPAN><BR /><BR /><SPAN>Now you can use activiti with and without spring.&nbsp; And that is good.</SPAN><BR /><BR /><SPAN>But we see a potential problem popping up.&nbsp; There are now 2 styles of configuration: activiti cfg xml and the spring configuration.&nbsp; Up to now there was good reason for this split up.&nbsp; As the things that we have configurable are very different (transaction/datasource stuff) in both scenarios.</SPAN><BR /><BR /><SPAN>But now we're starting to work out more configurable aspects and we realize that we'll have a ton of extra configuration items which don't need to be different.&nbsp; Like engine variable types, form types, business calendar etc.&nbsp; And the way we're going now, we'll have to work out parsing for those 2 environments separate and document that separate.&nbsp; That is a bad choice we think.</SPAN><BR /><BR /><SPAN>So I'll be trying out a new strategy.&nbsp; The reasoning is that we'll distinct between a dependency on spring for the configuration and a dependency on spring's transaction management.&nbsp; The idea is that we'll refactor the ProcessEngineBuilder to use the spring bean xml configuration parsing.&nbsp; That way of configuring would not use the spring transaction integration or the other spring integrations.</SPAN><BR /><BR /><SPAN>The advantage is that all the non-tx-related configurations would only have to be implemented once and documented once.&nbsp; And that will lead to less confusing documentation and usage of the engine.</SPAN><BR /><BR /><SPAN>The downside could be that we introduce a dependency from the activiti engine to spring-core for parsing of the configuration file.&nbsp; I'm thinking of making that parsing pluggable in case people would really object against that dependency.&nbsp; In that case, contributors could write a spring-bean-xml-parser in activiti to avoid that dependency.&nbsp; Imo, i can live with a dependency on spring core for parsing the config.</SPAN><BR /><BR /><SPAN>I want to stress that this would not create a full dependency on the spring style of doing things.&nbsp; It's just for parsing the config.</SPAN><BR /><BR /><SPAN>Does anyone see a problem with this approach?&nbsp; </SPAN><BR /><BR /><SPAN>I'll be starting to code a prototype now and hopefully later today we'll all be able to review it.</SPAN></BODY></HTML> Mon, 22 Nov 2010 10:12:57 GMT tombaeyens 2010-11-22T10:12:57Z configuration refactoring towards spring beans xml https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35506#M18647 Hi,Now you can use activiti with and without spring.&nbsp; And that is good.But we see a potential problem popping up.&nbsp; There are now 2 styles of configuration: activiti cfg xml and the spring configuration.&nbsp; Up to now there was good reason for this split up.&nbsp; As the things that we have configurable are Mon, 22 Nov 2010 10:12:57 GMT https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35506#M18647 tombaeyens 2010-11-22T10:12:57Z Re: configuration refactoring towards spring beans xml https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35507#M18648 <HTML><HEAD></HEAD><BODY><SPAN>it's not going to be trivial refactoring the and synchronizing the spring beans xml for the standalone case, programmatic case and the spring case.</SPAN><BR /><BR /><SPAN>especially i think in order to simplify the spring bean xml, this could impact the ProcessEngineBuilder api.&nbsp; ideally i would like the api classes to be used in the spring bean configuration.&nbsp; </SPAN><BR /><BR /><SPAN>i think it's going to be too tight to try and squeeze these research and refactorings before ga release.</SPAN><BR /><BR /><SPAN>but we can get around it by moving the ProcessEngineBuilder to the internal impl apis.&nbsp; and promote ProcessEngines as the only way you can use the API now.</SPAN></BODY></HTML> Mon, 22 Nov 2010 14:41:38 GMT https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35507#M18648 tombaeyens 2010-11-22T14:41:38Z