<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: configuration refactoring towards spring beans xml in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35507#M18648</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;especially i think in order to simplify the spring bean xml, this could impact the ProcessEngineBuilder api.&amp;nbsp; ideally i would like the api classes to be used in the spring bean configuration.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;i think it's going to be too tight to try and squeeze these research and refactorings before ga release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;but we can get around it by moving the ProcessEngineBuilder to the internal impl apis.&amp;nbsp; and promote ProcessEngines as the only way you can use the API now.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 22 Nov 2010 14:41:38 GMT</pubDate>
    <dc:creator>tombaeyens</dc:creator>
    <dc:date>2010-11-22T14:41:38Z</dc:date>
    <item>
      <title>configuration refactoring towards spring beans xml</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35506#M18647</link>
      <description>Hi,Now you can use activiti with and without spring.&amp;nbsp; And that is good.But we see a potential problem popping up.&amp;nbsp; There are now 2 styles of configuration: activiti cfg xml and the spring configuration.&amp;nbsp; Up to now there was good reason for this split up.&amp;nbsp; As the things that we have configurable are</description>
      <pubDate>Mon, 22 Nov 2010 10:12:57 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35506#M18647</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2010-11-22T10:12:57Z</dc:date>
    </item>
    <item>
      <title>Re: configuration refactoring towards spring beans xml</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35507#M18648</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;especially i think in order to simplify the spring bean xml, this could impact the ProcessEngineBuilder api.&amp;nbsp; ideally i would like the api classes to be used in the spring bean configuration.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;i think it's going to be too tight to try and squeeze these research and refactorings before ga release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;but we can get around it by moving the ProcessEngineBuilder to the internal impl apis.&amp;nbsp; and promote ProcessEngines as the only way you can use the API now.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Nov 2010 14:41:38 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/configuration-refactoring-towards-spring-beans-xml/m-p/35507#M18648</guid>
      <dc:creator>tombaeyens</dc:creator>
      <dc:date>2010-11-22T14:41:38Z</dc:date>
    </item>
  </channel>
</rss>

