<?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 Creating application based on Activiti in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/creating-application-based-on-activiti/m-p/169147#M122556</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I want to create a WEB based application which uses Activiti. The Activiti has a great API for persistence (DbSqlSession, CommandContext, etc.) and the workflow is needed for almost every function in my application (for 4-eyes principle and for other flows). Therefore I plan that every main function would be as a service (AccountService, LeadService, OpportunityService etc.) based on e.g. the IdentityService.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; In this case all events will go through the Activiti Engine and in addition there wouldn’t be necessary two independent persistent layers to handle the SQL statements.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;What is your opinion? Is this solution efficient (might be any performance issue)? Or the standalone application is the better approach (which only communicates with the Activiti via API).&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you for your suggestion in advance!&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Jan 2014 10:38:50 GMT</pubDate>
    <dc:creator>galaxoft</dc:creator>
    <dc:date>2014-01-06T10:38:50Z</dc:date>
    <item>
      <title>Creating application based on Activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/creating-application-based-on-activiti/m-p/169147#M122556</link>
      <description>Hello,I want to create a WEB based application which uses Activiti. The Activiti has a great API for persistence (DbSqlSession, CommandContext, etc.) and the workflow is needed for almost every function in my application (for 4-eyes principle and for other flows). Therefore I plan that every main fu</description>
      <pubDate>Mon, 06 Jan 2014 10:38:50 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/creating-application-based-on-activiti/m-p/169147#M122556</guid>
      <dc:creator>galaxoft</dc:creator>
      <dc:date>2014-01-06T10:38:50Z</dc:date>
    </item>
    <item>
      <title>Re: Creating application based on Activiti</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/creating-application-based-on-activiti/m-p/169148#M122557</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I think it's easier to keep it separated, and only use the Activiti to do what it can do best: driving processes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Typically, i always sugget to keep your entities in it's own services and data storage, and reference them in the process.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Jan 2014 12:30:21 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/creating-application-based-on-activiti/m-p/169148#M122557</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2014-01-06T12:30:21Z</dc:date>
    </item>
  </channel>
</rss>

