[
https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158476#comment-13158476
]
Karl Wright commented on CONNECTORS-287:
----------------------------------------
I tried to build here and failed. The reason is that the build target tries to
automatically download stuff and I am behind a firewall:
download-alfresco-ws-client:
[mkdir] Created dir: C:\wip\mcf\CONNECTORS-287\connectors\alfresco\dist\lib
[get] Getting: http://maven.alfresco.com/nexus/service/local/repositories/
releases/content/org/alfresco/alfresco-web-service-client/3.4.e/alfresco-web-ser
vice-client-3.4.e.jar
[get] To: C:\wip\mcf\CONNECTORS-287\connectors\alfresco\lib\alfresco-web-s
ervice-client-3.4.e.jar
The download-dependencies ant target exists precisely for this reason, so that
the download can be done independently of the build. Thus I think you will
need to do the following, modeled loosely on the jcifs connector:
(1) Create a directory under connectors/alfresco which is meant to contain the
stuff that will be downloaded;
(2) Make the compilation of the alfresco connector conditional on the existence
of the right jars in that directory;
(3) Hook up the download to the download-dependencies target in the alfresco
build.xml.
> An Alfresco connector would be helpful
> --------------------------------------
>
> Key: CONNECTORS-287
> URL: https://issues.apache.org/jira/browse/CONNECTORS-287
> Project: ManifoldCF
> Issue Type: New Feature
> Reporter: Piergiorgio Lucidi
> Assignee: Piergiorgio Lucidi
> Fix For: ManifoldCF 0.4
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> The idea of this connector is based on the fact that there are many Alfresco
> installations that don't yet support the CMIS protocol (2.1-2.9).
> I'm starting to think about the Alfresco Repository Connector.
> Alfresco doesn't expose any REST API to execute Lucene queries without adding
> some custom WebScripts. I would like to implement a connector that doesn't
> need to install any other custom plugin and that it can work with any
> Alfresco 2.x out of the box installation.
> The unique search service exposed by Alfresco via REST is a keyword search
> service, but it is not useful for our connector.
> I think that the right way to follow is to use the Alfresco Web Services API,
> this API is based on the SOAP protocol and we have a specific Alfresco Web
> Services Client provided by Alfresco.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
