<?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 Integrating REST interface / explore into an existing webapp in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112330#M79021</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello everybody,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am struggling integrating the Activiti REST interface into an existing web application since the REST interface is already an .war-artifact itself. For this reason I would like to propose to change the way the REST interface is build in the following way.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What about creating a .jar with the actual API and servlet classes and then creating a web-app (.jar) which references the .jar with the actual API classes. The .war would then contain the rest-api.jar plus the configuration files / examples. In my opinion this would ease the integration and usage of the REST interface since you could use the "rest-api.jar" in your own web application.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Any opinions on this?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;EDIT: The same goes for the explorer. Anyway, I managed to pack a jar for the explorer and to add it to the dependencies of my webapp. The problem I am facing now however is that I cannot convince the explorer to use my process engine instance which has been created by a Spring configuration file already because it is in the contextConfigLocation. The explorer always tries to get the default Process Engine by using the ProcessEngines-class. This fails due to my process engine not beeing the static list of Process Engines which this class maintains and due to the property "initialized" being set to false. This makes the ProcessEngines-class try to create a new default process engine which fails due to a missing dataSource.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Cheers&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Sebastian&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 25 Feb 2012 08:27:59 GMT</pubDate>
    <dc:creator>sebastian_s</dc:creator>
    <dc:date>2012-02-25T08:27:59Z</dc:date>
    <item>
      <title>Integrating REST interface / explore into an existing webapp</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112330#M79021</link>
      <description>Hello everybody,I am struggling integrating the Activiti REST interface into an existing web application since the REST interface is already an .war-artifact itself. For this reason I would like to propose to change the way the REST interface is build in the following way.What about creating a .jar</description>
      <pubDate>Sat, 25 Feb 2012 08:27:59 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112330#M79021</guid>
      <dc:creator>sebastian_s</dc:creator>
      <dc:date>2012-02-25T08:27:59Z</dc:date>
    </item>
    <item>
      <title>Re: Integrating REST interface / explore into an existing webapp</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112331#M79022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The Activiti Explorer and REST apps can be used as-is or you can choose the customise them.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;When you choose for customisation your proposal of providing JARs with the classes is not a bad idea.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The resource files should not be part if this JAR I think, to prevent the problem you describe.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Best regards,&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 26 Feb 2012 10:50:34 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112331#M79022</guid>
      <dc:creator>trademak</dc:creator>
      <dc:date>2012-02-26T10:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: Integrating REST interface / explore into an existing webapp</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112332#M79023</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello Tijs,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;thanks for getting back on this. The second which should be taken into account that the process engine instance being used by the explorer should be configurable and should not depend on the ProcessEngines-classes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Sebastian&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 26 Feb 2012 13:07:28 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112332#M79023</guid>
      <dc:creator>sebastian_s</dc:creator>
      <dc:date>2012-02-26T13:07:28Z</dc:date>
    </item>
    <item>
      <title>Re: Integrating REST interface / explore into an existing webapp</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112333#M79024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I created a JIRA issue to document this improvement proposal: &lt;/SPAN&gt;&lt;A href="http://jira.codehaus.org/browse/ACT-1112" rel="nofollow noopener noreferrer"&gt;http://jira.codehaus.org/browse/ACT-1112&lt;/A&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 26 Feb 2012 13:23:45 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112333#M79024</guid>
      <dc:creator>sebastian_s</dc:creator>
      <dc:date>2012-02-26T13:23:45Z</dc:date>
    </item>
    <item>
      <title>Re: Integrating REST interface / explore into an existing webapp</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112334#M79025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is the ticket closed , &amp;nbsp;because i have a similar problem . please help me by suggesting the Process to do it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Aug 2017 04:40:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112334#M79025</guid>
      <dc:creator>akshayburjwal</dc:creator>
      <dc:date>2017-08-16T04:40:07Z</dc:date>
    </item>
    <item>
      <title>Re: Integrating REST interface / explore into an existing webapp</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112335#M79026</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;B&gt;Akshay Burjwal&lt;/B&gt;‌ - Could you post a new question with the issue you are having? This post is quite old and some of the info may be out of date.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Aug 2017 13:32:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/integrating-rest-interface-explore-into-an-existing-webapp/m-p/112335#M79026</guid>
      <dc:creator>kgastaldo</dc:creator>
      <dc:date>2017-08-17T13:32:22Z</dc:date>
    </item>
  </channel>
</rss>

