[ https://issues.apache.org/jira/browse/CONNECTORS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Piergiorgio Lucidi updated CONNECTORS-602: ------------------------------------------ Fix Version/s: (was: ManifoldCF 1.3) ManifoldCF next > Add a new Alfresco WebScript API Repository Connector > ----------------------------------------------------- > > Key: CONNECTORS-602 > URL: https://issues.apache.org/jira/browse/CONNECTORS-602 > Project: ManifoldCF > Issue Type: New Feature > Components: Alfresco connector > Affects Versions: ManifoldCF 1.0.1 > Reporter: Piergiorgio Lucidi > Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF next > > Original Estimate: 120h > Remaining Estimate: 120h > > Taking a look at the Alfresco roadmap, it seems that during the next 18 > months the CML SOAP API will not be supported anymore: > [http://wiki.alfresco.com/wiki/Product_Roadmap#End-of-life_3] > The history of this connector is not happy, during the first step I asked to > some Alfresco guys about the life of the SOAP API and I was assured that it > would not be finished. > Anyway this is not the best API exposed by Alfresco, for many reasons > developers should use the REST API as their first choice. > The SOAP API was the only one API that allows to invoke Lucene queries > without implementing new customizations/extensions on Alfresco. > Now we have an official confirmation that the life of this SOAP API ends > during the end of this year and the begin of the next one. > My idea is to do a brainstorming with some Alfresco guys to understand > together which APIs we should use to reimplement the connector. > I would like to use the current HTTP services without installing nothing on > the Alfresco side. But I have to check with them if this solution is feasible. > I hope to have good news soon. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira