[
https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159165#comment-13159165
]
Piergiorgio Lucidi commented on CONNECTORS-287:
-----------------------------------------------
{quote}
(1) Since it seems like you need to enter a URL for the "endpoint" field, you
might want to consider requesting a protocol, server, port, and path instead of
a free-form URL. Pick the protocol from a drop-down, and use javascript to
check that the server has no "/" characters and the port is either blank or a
number. This will guarantee that the URL you construct will be valid.
{quote}
Ok I can work on this improvement during this week.
{quote}
(2) You should be catching any exceptions thrown by the API methods. I'm not
quite sure how you are getting something thrown that is not being caught,
unless the exception thrown is derived from RuntimeException or Error. In any
case you will need to figure out how to correctly catch and handle whatever
exceptions can be thrown by the API, and convert or wrap these in ManifoldCF
exceptions.
{quote}
Ok I will check about this issue and I will try to solve it quickly.
Thank you for your feedback :)
> 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
