<?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: Feedback request for Activiti/Spring/Alfresco/PHP solution. in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/feedback-request-for-activiti-spring-alfresco-php-solution/m-p/196977#M150107</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1. Form keys are imho a better approach, as they totally decouple your forms. Since you have a custom REST layer, it's a matter of handling these forms there.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Yes. Altough exposing the Java api of activigti through your own rest api isn't hard at all.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3. OpenCmis is the easiest way here.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Jun 2014 14:18:59 GMT</pubDate>
    <dc:creator>jbarrez</dc:creator>
    <dc:date>2014-06-27T14:18:59Z</dc:date>
    <item>
      <title>Feedback request for Activiti/Spring/Alfresco/PHP solution.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/feedback-request-for-activiti-spring-alfresco-php-solution/m-p/196976#M150106</link>
      <description>Hi there,We are designing a new workflows based application that will comprise Activiti, Spring and PHP, this way: &amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - backend -&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - frontend -&amp;nbsp;&amp;nbsp; [ Workflows Service ]&amp;nbsp; ——- REST/JSON ——- [ Workflows Portal ]&amp;nbsp;&amp;nbsp;&amp;nbsp; (spring + activiti)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;</description>
      <pubDate>Mon, 23 Jun 2014 04:49:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/feedback-request-for-activiti-spring-alfresco-php-solution/m-p/196976#M150106</guid>
      <dc:creator>jonvargas</dc:creator>
      <dc:date>2014-06-23T04:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: Feedback request for Activiti/Spring/Alfresco/PHP solution.</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/feedback-request-for-activiti-spring-alfresco-php-solution/m-p/196977#M150107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;1. Form keys are imho a better approach, as they totally decouple your forms. Since you have a custom REST layer, it's a matter of handling these forms there.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;2. Yes. Altough exposing the Java api of activigti through your own rest api isn't hard at all.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;3. OpenCmis is the easiest way here.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Jun 2014 14:18:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/feedback-request-for-activiti-spring-alfresco-php-solution/m-p/196977#M150107</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2014-06-27T14:18:59Z</dc:date>
    </item>
  </channel>
</rss>

