[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147597#comment-13147597 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I have created two new Maven modules: - Alfresco Connector - Integration Tests for Alfresco Connectors (under tests/) I started to import all the dependencies and now I have to check potential conflicts with the current ManifoldCF libraries. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147635#comment-13147635 ] Karl Wright commented on CONNECTORS-287: Rather than checking in directly to trunk, could you first create a branch (branches/CONNECTORS-287) so that the rest of us can review your new connector and the new libraries you are including for it to work with? Otherwise it's going to be hard for you to test everything since you probably don't have a complete environment. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[
https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13147666#comment-13147666
]
Piergiorgio Lucidi commented on CONNECTORS-287:
---
{quote}
Rather than checking in directly to trunk, could you first create a branch
(branches/CONNECTORS-287) so that the rest of us can review your new connector
and the new libraries you are including for it to work with? Otherwise it's
going to be hard for you to test everything since you probably don't have a
complete environment.
{quote}
No problem, during these days I will create a new branch dedicated to this
issue ;)
> 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
> 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148413#comment-13148413 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I created the dedicated branch: [https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-287/] I will post a comment for every update on the development of this new feature. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148524#comment-13148524 ] Karl Wright commented on CONNECTORS-287: Looking forward to seeing how it evolves. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13152874#comment-13152874 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- A first implementation is finished and it is compatible with Alfresco 2.x,3.x and 4.x. I would like to check compatibility with Alfresco 1.x and I have to finish the integration tests module. Now I can create and start with Jetty any Alfresco version from 3.x. directly configuring Maven. This night I hope to finish the integration test implementation to customize the Jetty runner. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153154#comment-13153154 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- The first version of the Alfresco Connector now is committed. I have to finish the following tasks: * solve an issue about packaging the Alfresco war using its own Maven module (now the Alfresco war module is not directly used by the Alfresco Test module) * fix the execution of the integration test adding memory settings from Maven: I tested executing the IT by Java directly from Eclipse and adding memory settings from the IDE * add a new library to the project the H2 database support for Alfresco * update the documentation about how to build and deploy to add a couple of new libraries to manually add in the Maven repo I hope the next week to solve all these issues. Anyway the connector should work on all the versions of Alfresco and now supports only the Lucene Query as the unique job parameter. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154539#comment-13154539 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Committed a new version of the integration test module with the following updates: - added some libraries: h2-support and jetty-naming - Maven build fixed: now the integration tests for the Alfresco Connector works correctly - the alfresco-war module now correctly works and it is called before running integration test > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155021#comment-13155021 ] Karl Wright commented on CONNECTORS-287: To be clear, have a look at the LICENSE.txt file for an idea of the information we need for code that we redistribute. Only certain licenses can be redistributed, according to Apache policy. Those are: - Apache licensed - Berkeley license - MIT license - Eclipse license Licenses we CAN'T redistribute include: - LGPL - GPL Anything not mentioned here requires a ruling from Apache Legal, OR you need to find it in another Apache project and ask why they think it is redistributable. For example, I got a ruling for the JSON license, which is a derivative of the Berkeley license. Hope this helps. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156054#comment-13156054 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Here some updates: - fixed the Alfresco Connector: now can extract binaries from custom content models - fixed the integration test implementation: now the execution works - now integration tests can be executed correctly I have to finish the following tasks: * check / ask licenses for all the new dependencies of the Alfresco Web Services API (that are included in the Alfresco SDK) * check / ask for the h2-support license * update the site documentation about Maven install for dependencies * create the site documentation for the new connector > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156067#comment-13156067 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Here all the details about licenses of the required dependencies to embed the Alfresco Connector using the Alfresco Web Services Client: * axis-1.4 - Apache * commons-discovery-0.2 - Apache * commons-logging-1.1.1 - Apache * jaxrpc - CDDL * mail - CDDL * opensaml - Apache * wsdl4j - CPL 1.0 * wss4j - Apache * xalan - Apache * xercesImpl - Apache * xmlsec - Apache > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156621#comment-13156621 ] Tommaso Teofili commented on CONNECTORS-287: according to [1] software under : - CDDL may be included in binary form within an Apache product if the inclusion is appropriately labeled - CPL 1.0 may be included in binary form within an Apache product if the inclusion is appropriately labeled - Apache is obviously ok so I think we're ok with regards to Alfresco WebServices Client as long as we highlight the CDDL and CPL pieces in the NOTICE file. [1] : http://apache.org/legal/resolved.html > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156754#comment-13156754 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Carlo Sciolla has released the h2-support-1.1.jar under MIT/X11 license [1] This dependency is available on Clojars [2] and we can add a standard Maven dependency without manually installation. I would like to thank Carlo for his support that was very important to create integration tests for this connector :) For the Alfresco Web Service Client (alfresco-web-service-client-x.x.jar) we have a problem because it is released under LGPL3 as mentioned in the Alfresco wiki [3] and in the license.txt file in the Alfresco SDK distribution. I think this means that we have to say to users to download separately this artifact. Or could we create a script that automatically can download it from remote repositories? I mean, in the same way integration tests do to create the alfresco.war using Maven. [1] https://github.com/skuro/alfresco-h2-support [2] https://clojars.org/it.sk.alfresco/h2-support [3] http://wiki.alfresco.com/wiki/Open_Source_Licensing > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13157936#comment-13157936 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Added the connector documentation and updated the included connectors page. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158308#comment-13158308 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Taking a look at the paragraph "We license our product under other licenses upon request.", probably we could ask to release the Alfresco Web Service Client under a different license [1]. [1] http://wiki.alfresco.com/wiki/Open_Source_Licensing#We_license_our_product_under_other_licenses_upon_request. I'll try to ask them about this. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158317#comment-13158317 ] Karl Wright commented on CONNECTORS-287: If there is a download required, it's not the end of the world - we already have infrastructure for doing that in both the maven and ant builds. Is it in the maven repository? > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158320#comment-13158320 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Yesterday night I found only a version of this artifact that was uploaded in the official Alfresco Maven repo, I think yesterday. But it is the stub client for Alfresco 3.4.e. This artifact is available only for this version. I could try to use this Alfresco version for integration tests and if it is ok we could solve this last issue. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158359#comment-13158359 ] Karl Wright commented on CONNECTORS-287: Worth a try! Hope it works... > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158360#comment-13158360 ] Karl Wright commented on CONNECTORS-287: Alternatively, if you have a download URL that's not in the maven repository for the right web-service client, we can use that url in the download-dependencies phase of the ant build, and modify the mvn-bootstrap scripts to push it into maven's local repository. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158377#comment-13158377 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I tested the dependency available on the Alfresco Maven repo and integration tests works correctly. So I think that we have solved this last issue. I'm committing the latest changes. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158407#comment-13158407 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Solved and committed the correct configuration, I think that now we can say that there is an Alfresco Connector for ManifoldCF :D I updated poms and Ant scripts to enable the automatic download of the Alfresco dependency from the Alfresco Maven repo. > 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 > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158416#comment-13158416 ] Karl Wright commented on CONNECTORS-287: Don't forget to update mvn-bootstrap.sh and mvn-bootstrap.bat too. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158431#comment-13158431 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I don't think that I have to update that scripts, all the other dependencies will be downloaded from Maven repositories. Please could you try to build the project from this branch? > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158459#comment-13158459 ] Karl Wright commented on CONNECTORS-287: Yes, will try shortly. Was there any resolution to the need for an Alfresco authority? Or has that not yet been addressed? > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158493#comment-13158493 ] Karl Wright commented on CONNECTORS-287: r1207279 makes the above changes > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158595#comment-13158595 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Ok, thank you! But now I don't see the alfresco-web-service dependency inside the connector-lib of the example application. Is it right? Before I tested the script and the library was correctly copied in the connector-lib folder. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158596#comment-13158596 ] Karl Wright commented on CONNECTORS-287: I changed the ant build to copy it to the alfresco/dist/lib directory, along with all the jars in alfresco/lib. So I believe it is correct - but I won't have a chance to be certain until I am outside the firewall. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158694#comment-13158694 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I updated Ant scripts dedicated to the example application: now the alfresco-web-service dependency is correctly copied in the connector-lib folder. I think that now we have solved all the issues. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158868#comment-13158868 ] Karl Wright commented on CONNECTORS-287: I built it and tried to run, w/o a repository to connect to, and got this: org.alfresco.webservice.util.WebServiceException: Error creating authentication service: java.net.MalformedURLException: no protocol: balh/AuthenticationService at org.alfresco.webservice.util.WebServiceFactory.getAuthenticationServi ce(WebServiceFactory.java:167) at org.alfresco.webservice.util.AuthenticationUtils.startSession(Authent icationUtils.java:73) at org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryC onnector.getSession(AlfrescoRepositoryConnector.java:147) at org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryC onnector.checkConnection(AlfrescoRepositoryConnector.java:179) at org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryC onnector.check(AlfrescoRepositoryConnector.java:115) at org.apache.jsp.viewconnection_jsp._jspService(viewconnection_jsp.java :326) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper .java:377) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:3 13) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511 ) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:4 01) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.jav a:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:1 82) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:7 66) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:450) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:327) at org.mortbay.jetty.servlet.Dispatcher.forward(Dispatcher.java:126) at org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.j ava:706) at org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.jav a:677) This caused a blank screen to come back from the view connection page. So I recommend the following: (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. This will guarantee that the URL you construct will be valid. (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. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158880#comment-13158880 ] Karl Wright commented on CONNECTORS-287: I also included a placeholder README.txt file in the download directory. This is necessary for two reasons: (1) to insure that when the directory is zipped it doesn't just disappear, and (2) to tell the user how to get the appropriate missing jars. The file I put there should be completed before we merge. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[
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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159380#comment-13159380 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I solved the second issue: I added the exception handling for the WebServiceException thrown by the Afresco Web Services API. Tomorrow I hope to spend some time on the improvement of the configuration form as you suggested. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160224#comment-13160224 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I also solved the first point: fixed the configuration for the Alfresco Repository Connector. I added protocol, server, port, and path instead of a free-form URL for the endpoint. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160263#comment-13160263 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I think that now integration tests are broken, because I changed the configuration parameters of the connector. Tomorrow I hope to solve this last issue on integration tests. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160876#comment-13160876 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- I solved all the issues about integration tests, I think that now this first version of the connector could be considered completed. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161566#comment-13161566 ] Karl Wright commented on CONNECTORS-287: I just tried the new connector, built with ant. It does not have a tab for the connector-specific configuration anymore, but instead just displays the alfresco configuration data as a suffix for all of the other tabs. I don't think this is a good idea. Can you fix this? Second comment... If a port or path is left blank, then the connector should use standard alfresco default values for these, or better yet, just start with the defaults filled in so people know what is typically used. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161623#comment-13161623 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Os, I'll try to reproduce these issues and I hope to solve all this night. I think that there are issues because probably I have to reset my ManifoldCF installation. I will work on a clean installation to re-check the connector. Anyway I had planned to test it tonight in a clean way. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[
https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162114#comment-13162114
]
Piergiorgio Lucidi commented on CONNECTORS-287:
---
{quote}
I just tried the new connector, built with ant. It does not have a tab for the
connector-specific configuration anymore, but instead just displays the
alfresco configuration data as a suffix for all of the other tabs. I don't
think this is a good idea. Can you fix this?
{quote}
I just tried to replicate this issue but without any result, could you please
guide me on this?
{quote}
Second comment... If a port or path is left blank, then the connector should
use standard alfresco default values for these, or better yet, just start with
the defaults filled in so people know what is typically used.
{quote}
Done with the latest commit :)
> 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162152#comment-13162152 ] Karl Wright commented on CONNECTORS-287: Hmm. I wonder if you are missing a file or resource in the commit or in the ant build? It is pretty obvious here! I'm going to do a fresh checkout and build and then if it still happens for me I'll attach a screen shot. > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162155#comment-13162155 ] Karl Wright commented on CONNECTORS-287: Attaching a screen shot... Note: (1) There is no specific tab for Alfresco-related configuration information, and (2) ALL tabs have the Alfresco-related configuration information. (Screen shot is of the "Type" tab, but all of them have it). > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162390#comment-13162390 ] Piergiorgio Lucidi commented on CONNECTORS-287: --- Solved, now there is specific "Server" tab for Alfresco-related configuration. > 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 > > Attachments: Typetab.png > > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162493#comment-13162493 ] Karl Wright commented on CONNECTORS-287: Looks good. Any objection if I go ahead and try to merge the branch into trunk? > 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 > > Attachments: Typetab.png > > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162707#comment-13162707 ] Karl Wright commented on CONNECTORS-287: I did a trial merge, and the LICENSE/NOTICE/README files are still not updated in the branch. They need to cover the following: Alib\h2-support-1.1.jar Alib\mail.jar Alib\wss4j-1.5.4-patched.jar Alib\jetty-plus-6.1.26.jar Alib\opensaml-1.0.1.jar Alib\h2-1.3.158.jar Alib\xmlsec-1.4.1.jar Alib\jetty-naming-6.1.26.jar The necessary license research has been done but the files need to be updated accordingly. I'll tackle this in the merge branch sometime this evening. Other than that everything looks good for a merge commit. Any objection if I handle that? > 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 > > Attachments: Typetab.png > > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[
https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162713#comment-13162713
]
Piergiorgio Lucidi commented on CONNECTORS-287:
---
{quote}
Other than that everything looks good for a merge commit. Any objection if I
handle that?
{quote}
No, thank you very much for handling this last task! :)
> 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
>
> Attachments: Typetab.png
>
> 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162727#comment-13162727 ] Karl Wright commented on CONNECTORS-287: License work pretty much done. Only thing I'd like to know is where you downloaded mail.jar from (so I can provide a URL accordingly) > 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 > > Attachments: Typetab.png > > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162728#comment-13162728 ] Karl Wright commented on CONNECTORS-287: Merged into trunk, r1210414 > 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 > > Attachments: Typetab.png > > 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
[jira] [Commented] (CONNECTORS-287) An Alfresco connector would be helpful
[
https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162729#comment-13162729
]
Piergiorgio Lucidi commented on CONNECTORS-287:
---
{quote}
License work pretty much done. Only thing I'd like to know is where you
downloaded mail.jar from (so I can provide a URL accordingly)
{quote}
In the Alfresco SDK is mentioned that the specific dependency mail.jar should
be taken from the following page:
http://glassfish.java.net/javaee5/mail/
> 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
>
> Attachments: Typetab.png
>
> 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
