from:"Piergiorgio Lucidi"

A warm welcome from Rome :)

Cheers,
Piergiorgio


2014-06-03 19:25 GMT+02:00 Karl Wright daddy...@gmail.com:

 The Project Management Committee (PMC) for Apache ManifoldCFhas asked
 Muhammed Olgun to become a committer and we are pleased to announce
 that they have accepted.

 Muhammed has contributed in part to discussions in the past, as well
 as furnished our new GridFS connector.
 We look forward to working with Muhammed on future projects.  Please
 join me in wishing him welcome!

 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

OpenSearchServer Output Connector questions

Hi guys,

one of our customers is trying to use ManifoldCF in different ways and they
are trying to use the OpenSearchServer connector without success.

They are using a newer version of OpenSearchServer (1.5.x) so probably our
connector can't work with this version.

Looking at the code it seems that this connector only supports the
ingestion of binaries without considering metadata and properties, is it
right?

And if yes, why we don't support metadata?

Please let me know.
Thank you.

Cheers,
Piergiorgio

-- 
Piergiorgio Lucidi
Open Source ECM Specialist
http://www.open4dev.com

[jira] [Created] (CONNECTORS-949) Upgrade OpenCMIS to the latest 0.11.0 version

2014-06-05 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-949:
-

 Summary: Upgrade OpenCMIS to the latest 0.11.0 version
 Key: CONNECTORS-949
 URL: https://issues.apache.org/jira/browse/CONNECTORS-949
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF next


We have to upgrade the CMIS Connector to the latest version of OpenCMIS to 
include all the new improvements from 0.11.0 version:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310936version=12325877

That includes all the issues solved in 0.10.0.





--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CONNECTORS-950) CMIS Connector should ingest only the properties specified in the select clause

2014-06-05 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-950:
-

 Summary: CMIS Connector should ingest only the properties 
specified in the select clause
 Key: CONNECTORS-950
 URL: https://issues.apache.org/jira/browse/CONNECTORS-950
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF next


Actually when we try to ingest contents using the following query:
{code}
select cmis:objectId, cmis:name from cmis:document
{code}

ManifoldCF will create indexes for all the contents including all the metadata 
without considering what we have specified in the select clause.

Probably a better behavior should be based on considering only the properties 
specified in the select clause.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CONNECTORS-949) Upgrade OpenCMIS to the latest 0.11.0 version

2014-06-05 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018614#comment-14018614
 ] 

Piergiorgio Lucidi commented on CONNECTORS-949:
---

No problem for this, we can schedule it for 1.7.

 Upgrade OpenCMIS to the latest 0.11.0 version
 -

 Key: CONNECTORS-949
 URL: https://issues.apache.org/jira/browse/CONNECTORS-949
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.7

   Original Estimate: 24h
  Remaining Estimate: 24h

 We have to upgrade the CMIS Connector to the latest version of OpenCMIS to 
 include all the new improvements from 0.11.0 version:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310936version=12325877
 That includes all the issues solved in 0.10.0.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CONNECTORS-949) Upgrade OpenCMIS to the latest 0.11.0 version

2014-06-05 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-949:
--

Fix Version/s: (was: ManifoldCF next)
   ManifoldCF 1.7

 Upgrade OpenCMIS to the latest 0.11.0 version
 -

 Key: CONNECTORS-949
 URL: https://issues.apache.org/jira/browse/CONNECTORS-949
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.7

   Original Estimate: 24h
  Remaining Estimate: 24h

 We have to upgrade the CMIS Connector to the latest version of OpenCMIS to 
 include all the new improvements from 0.11.0 version:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310936version=12325877
 That includes all the issues solved in 0.10.0.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (CONNECTORS-948) CMIS Connector returns couldn't encrypt null when the query doesn't include cmis:objectId

2014-06-05 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-948.
---

Resolution: Fixed

r1600598.

 CMIS Connector returns couldn't encrypt null when the query doesn't include 
 cmis:objectId
 -

 Key: CONNECTORS-948
 URL: https://issues.apache.org/jira/browse/CONNECTORS-948
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Priority: Minor
   Original Estimate: 24h
  Remaining Estimate: 24h

 Manifold needs to know the objectId of a content to create a reference for it.
 This means that executing the following query there is no problem:
 {code}
 select * from cmis:document
 {code}
 But trying to execute a similar query:
 {code}
 select cmis:name from cmis:document
 {code}
 Manifold returns an error from OpenCMIS that is the following:
 {code}
 couldn't encrypt: null
 {code}
 This because the cmis:objectId is not added in the select clause and it is 
 needed to create a reference for this content inside the Manifold database.
 The workaround is to add the objectId in the query in the following way as 
 the standard CMIS needs:
 {code}
 select cmis:objectId, cmis:name from cmis:document 
 {code}
 The involved code is the following from the CMISRepositoryConnector:
 {code}
 ItemIterableQueryResult results = session.query(cmisQuery, 
 false).getPage(10);
   for (QueryResult result : results) {
 String id = result.getPropertyValueById(PropertyIds.OBJECT_ID);
 activities.addSeedDocument(id);
   }
 {code}
 Should we solve this issue adding the cmis:objectId parameter if doesn't 
 exist in the select clause of the query?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (CONNECTORS-948) CMIS Connector returns couldn't encrypt null when the query doesn't include cmis:objectId

2014-06-05 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-948:
--

Fix Version/s: ManifoldCF next

 CMIS Connector returns couldn't encrypt null when the query doesn't include 
 cmis:objectId
 -

 Key: CONNECTORS-948
 URL: https://issues.apache.org/jira/browse/CONNECTORS-948
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Priority: Minor
 Fix For: ManifoldCF next

   Original Estimate: 24h
  Remaining Estimate: 24h

 Manifold needs to know the objectId of a content to create a reference for it.
 This means that executing the following query there is no problem:
 {code}
 select * from cmis:document
 {code}
 But trying to execute a similar query:
 {code}
 select cmis:name from cmis:document
 {code}
 Manifold returns an error from OpenCMIS that is the following:
 {code}
 couldn't encrypt: null
 {code}
 This because the cmis:objectId is not added in the select clause and it is 
 needed to create a reference for this content inside the Manifold database.
 The workaround is to add the objectId in the query in the following way as 
 the standard CMIS needs:
 {code}
 select cmis:objectId, cmis:name from cmis:document 
 {code}
 The involved code is the following from the CMISRepositoryConnector:
 {code}
 ItemIterableQueryResult results = session.query(cmisQuery, 
 false).getPage(10);
   for (QueryResult result : results) {
 String id = result.getPropertyValueById(PropertyIds.OBJECT_ID);
 activities.addSeedDocument(id);
   }
 {code}
 Should we solve this issue adding the cmis:objectId parameter if doesn't 
 exist in the select clause of the query?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: OpenSearchServer Output Connector questions

Hi Emmanuel,

thank you for your message and I'll wait news by you.

Anyway do you think that it's possible to add the support for metadata on
this connector?
I mean, do you think that you can implement the ingestion of metadata?

Thank you.

Piergiorgio


2014-06-05 10:58 GMT+02:00 Emmanuel Keller ekel...@open-search-server.com:

 Hi Piergiorgio,

 Thank you for the alert.

 The legacy API are still available in 1.5.x, but it is possible that some
 minor changes break the compatibility.

 I can check later today, if this timing is okay for you.

 Emmanuel.


 On 05 Jun 2014, at 10:31, Piergiorgio Lucidi piergior...@apache.org
 wrote:

  Hi guys,
 
  one of our customers is trying to use ManifoldCF in different ways and
 they
  are trying to use the OpenSearchServer connector without success.
 
  They are using a newer version of OpenSearchServer (1.5.x) so probably
 our
  connector can't work with this version.
 
  Looking at the code it seems that this connector only supports the
  ingestion of binaries without considering metadata and properties, is it
  right?
 
  And if yes, why we don't support metadata?
 
  Please let me know.
  Thank you.
 
  Cheers,
  Piergiorgio
 
  --
  Piergiorgio Lucidi
  Open Source ECM Specialist
  http://www.open4dev.com

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Solr Output Connector - Questions

Hi guys,

I'm wondering if it is possible to disable the URL encoding on fields on
this connector.

Trying to create indexes from a repository that have the name of the field
with a URI similar to the following:

{http://www.alfresco.org/model/system}store_identifier


But the field is stored in Solr in this way:

http_3a_2f_2fwww_alfresco_org_2fmodel_2fsystem_2f1_0_7dstore_identifier


That is bad, our customer needs to create a copyField to solve this issue.

Is there a reason why we continue to use the URL encoding?

I saw in the code that it seems to be an issue related to SolrJ, but do you
think that we can find a workaround for this?

Thank you.

Cheers,
Piergiorgio
-- 
Piergiorgio Lucidi
Open Source ECM Specialist
http://www.open4dev.com

[jira] [Created] (CONNECTORS-956) Field names are URL encoded

2014-06-05 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-956:
-

 Summary: Field names are URL encoded
 Key: CONNECTORS-956
 URL: https://issues.apache.org/jira/browse/CONNECTORS-956
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi


The field names provided by some repositories such as Alfresco are based on an 
URI similar to:
{code}
{http://www.alfresco.org/model/system}store_identifier
{code}

But in Solr we found the following field name:
{code}
http_3a_2f_2fwww_alfresco_org_2fmodel_2fsystem_2f1_0_7dstore_identifier
{code}

The code involved in the Solr connector is the following:

{code}
protected static String preEncode(String fieldName)
  {
  return URLEncoder.encode(fieldName);
  }
{code}

Probably we should try to solve it removing the preEncode invocation.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Solr Output Connector - Questions

I have created the ticket to track this:

https://issues.apache.org/jira/browse/CONNECTORS-956


and now I'm trying to remove the preEncode invocation.


2014-06-05 15:26 GMT+02:00 Karl Wright daddy...@gmail.com:

 Ah, it seems I remember it backwards.

 SolrJ did *not* url-encode field names; that was the bug.  Instead, it
 tried to send field names in unencoded form, which would mess up URLs and
 cause problems.  See this method in SolrConnector.java:

 
   /** Preprocess field name.
   * SolrJ has a bug where it does not URL-escape field names.  This causes
 carnage for
   * ManifoldCF, because it results in IllegalArgumentExceptions getting
 thrown deep in SolrJ.
   * See CONNECTORS-630.
   * In order to get around this, we need to URL-encode argument names, at
 least until the underlying
   * SolrJ issue is fixed.
   */
   protected static String preEncode(String fieldName)
   {
   return URLEncoder.encode(fieldName);
   }
 

 It sounds like the SolrJ issue may have been fixed.  Can you try, or have
 the customer try, changing this method to just return fieldName;?  Make
 sure that you can still ingest documents that have funky field names that
 include international characters and punctuation; these come from some of
 our connectors.

 Thanks,
 Karl



 On Thu, Jun 5, 2014 at 9:20 AM, Karl Wright daddy...@gmail.com wrote:

  Hi Piergiorgio,
 
  I had a back-and-forth with Eric Hatcher about this issue about a year
  ago.  Solr technically accepts only a limited set of characters, and
 SolrJ
  is therefore not well coded to deal with anything much out of the
  ordinary.  I tried to get them to consider removing the url encoding, but
  they said no for that reason: you are doing things which you shouldn't
 be
  doing anyway.
 
  We did work around this problem for field *values*.  I'll review what was
  done to see if can be applied to field *names* too.  In the meantime,
  please open a ticket to track the issue.
 
  Thanks,
  Karl
 
 
 
 
  On Thu, Jun 5, 2014 at 9:13 AM, Piergiorgio Lucidi 
 piergior...@apache.org
   wrote:
 
  Hi guys,
 
  I'm wondering if it is possible to disable the URL encoding on fields on
  this connector.
 
  Trying to create indexes from a repository that have the name of the
 field
  with a URI similar to the following:
 
  {http://www.alfresco.org/model/system}store_identifier
 
 
  But the field is stored in Solr in this way:
 
  http_3a_2f_2fwww_alfresco_org_2fmodel_2fsystem_2f1_0_7dstore_identifier
 
 
  That is bad, our customer needs to create a copyField to solve this
 issue.
 
  Is there a reason why we continue to use the URL encoding?
 
  I saw in the code that it seems to be an issue related to SolrJ, but do
  you
  think that we can find a workaround for this?
 
  Thank you.
 
  Cheers,
  Piergiorgio
  --
  Piergiorgio Lucidi
  Open Source ECM Specialist
  http://www.open4dev.com
 
 
 

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

[jira] [Resolved] (CONNECTORS-950) CMIS Connector should ingest only the properties specified in the select clause

2014-06-05 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-950.
---

Resolution: Fixed

r1600691.

 CMIS Connector should ingest only the properties specified in the select 
 clause
 ---

 Key: CONNECTORS-950
 URL: https://issues.apache.org/jira/browse/CONNECTORS-950
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF next

   Original Estimate: 24h
  Remaining Estimate: 24h

 Actually when we try to ingest contents using the following query:
 {code}
 select cmis:objectId, cmis:name from cmis:document
 {code}
 ManifoldCF will create indexes for all the contents including all the 
 metadata without considering what we have specified in the select clause.
 Probably a better behavior should be based on considering only the properties 
 specified in the select clause.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (CONNECTORS-957) ClassNotFoundException starting from Alfresco One 4.2.1

2014-06-05 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-957:
-

 Summary: ClassNotFoundException starting from Alfresco One 4.2.1
 Key: CONNECTORS-957
 URL: https://issues.apache.org/jira/browse/CONNECTORS-957
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.6.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi


It seems that there are some issues starting from Alfresco One 4.2.1, trying to 
use the alfresco-web-service-client ManifoldCF is returning the following error:

{code}
Caused by: org.apache.axis.ConfigurationException: 
java.lang.ClassNotFoundException: org.apache.ws.axis.security.WSDoAllSender
java.lang.ClassNotFoundException: org.apache.ws.axis.security.WSDoAllSender
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:187)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:353)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:295)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java:473)
at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269)
at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at 
org.alfresco.webservice.repository.RepositoryServiceSoapBindingStub.query(RepositoryServiceSoapBindingStub.java:753)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.SearchUtils.luceneSearch(SearchUtils.java:66)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.addSeedDocuments(AlfrescoRepositoryConnector.java:439)
at 
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.addSeedDocuments(BaseRepositoryConnector.java:156)
at 
org.apache.manifoldcf.crawler.system.StartupThread.run(StartupThread.java:153)
{code}

I have replicated the problem but I don't know how to solve it. Inside the 
Alfresco Web Service Client JAR there are all the needed classes.

Could be a corruption issue?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (CONNECTORS-957) ClassNotFoundException starting from Alfresco One 4.2.1

2014-06-05 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14018974#comment-14018974
 ] 

Piergiorgio Lucidi commented on CONNECTORS-957:
---

The first exception was sent to me by a ManifoldCF user directly via email.

Trying to replicate the problem locally on my Mac I have the following 
exception:
{code}
Caused by: org.apache.axis.ConfigurationException: 
java.lang.ClassNotFoundException: org.alfresco.webservice.util.CookieHandler
java.lang.ClassNotFoundException: org.alfresco.webservice.util.CookieHandler
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:423)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:187)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:160)
at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:100)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDeployableItem.java:353)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDDeployableItem.java:295)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
at 
org.apache.axis.deployment.wsdd.WSDDChain.makeNewInstance(WSDDChain.java:125)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDeployableItem.java:274)
at 
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeployableItem.java:260)
at 
org.apache.axis.deployment.wsdd.WSDDDeployment.getGlobalRequest(WSDDDeployment.java:473)
at 
org.apache.axis.configuration.FileProvider.getGlobalRequest(FileProvider.java:269)
at org.apache.axis.AxisEngine.getGlobalRequest(AxisEngine.java:365)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:126)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at 
org.alfresco.webservice.authentication.AuthenticationServiceSoapBindingStub.startSession(AuthenticationServiceSoapBindingStub.java:187)
at 
org.alfresco.webservice.util.AuthenticationUtils.startSession(AuthenticationUtils.java:84)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.getSession(AlfrescoRepositoryConnector.java:290)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.checkConnection(AlfrescoRepositoryConnector.java:338)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.check(AlfrescoRepositoryConnector.java:242)
at 
org.apache.jsp.viewconnection_jsp._jspService(viewconnection_jsp.java:284)
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:388)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java

Re: MongoDB Repository and Output Connectors

2014-05-27 Thread Piergiorgio Lucidi

WOW! Great work!

Anyway this is only related to GridFS and it is considering only binaries
without considering all the other values such as strings.
I think that we can add a similar connector for any type of metadata for
indexing all the values stored in the database.

This means that we should add a dedicated MongoDB Connector in addition to
this one for GridFS.

What do you think?
Please let me know.

Piergiorgio


2014-05-27 13:41 GMT+02:00 Karl Wright daddy...@gmail.com:

 The license is apparently Apache 2.0.

 I've created CONNECTORS-945 to track this; calling it the MongoDB/GridFS
 connector.  I would be very interested in hearing whether this has anything
 to do with Piergiorgio's thoughts on the matter.

 Karl



 On Tue, May 27, 2014 at 6:56 AM, Karl Wright daddy...@gmail.com wrote:

  Looks good!
 
  What is the license on mongo-java-driver?
 
  Karl
 
  Sent from my Windows Phone
  From: Muhammed Olgun
  Sent: 5/27/2014 5:19 AM
  To: dev@manifoldcf.apache.org
  Subject: Re: MongoDB Repository and Output Connectors
  Hi,
 
  I worked a MongoDB related work too. It’s GridFS specific and I wrote
  a repository connector. I would like to share my code. May be we can
  combine it with MongoDB connector. They can be separate too.
 
  https://github.com/molgun/MCF-GridFS-Connector
 
  On 26 May 2014, at 15:42, Piergiorgio Lucidi piergior...@apache.org
  wrote:
 
   Hi Karl,
  
  
   2014-05-26 13:17 GMT+02:00 Wright, Karl karl.wri...@here.com:
  
Hi Piergiorgio,
  
   When you say 'huge', how many documents do you mean?  Do you know of
 any
   specific installations, and if so, how many documents do they work
 with?
  
  
   I think it is fine to develop connectors for mongodb, but if the
 number
  of
   documents is truly huge, there will need to be a way of dividing up
 the
   task.
  
  
   I imagine the typical usage of MongoDB, for example to keep User
  Generated
   Contents (UGC), this means that the information is just a little
 section
  of
   data for implementing social features dedicated to a website or a
 portal.
  
   I'm sorry I don't have real-world numbers now but we could estimate
   thousands of contents. Actually I'm working on a project that is
 starting
   to use MongoDB and the use case is UGC.
  
   Please consider that MongoDB divide its contents into databases, and
 for
   each database you have different collections of contents.
   This means that the connector should ask for a database and a specific
   collection to work, this because MongoDB doesn't support the join of
 data
   from different collections, it is not a relational database.
  
   So I think that it should be very easy to implement in ManifoldCF.
  
   Piergiorgio
  
  
  
   Karl
  
   Sent from my Windows Phone
   --
   From: Piergiorgio Lucidi
   Sent: 5/26/2014 6:01 AM
   To: dev@manifoldcf.apache.org
   Subject: MongoDB Repository and Output Connectors
  
   Hi guys,
  
   I think that it could be very useful to add in ManifoldCF both the
   connectors related to MongoDB.
   During these days I have taken a look at MongoDB and I think that I
 can
   start to implement these connectors.
  
   The repository connector could make sense because MongoDB is a
 document
   repository so some people could need to create smart indexes in a
 search
   server, I'm thinking about huge repositories.
   The MongoDB search engine could be very slow in some scenarios
 compared
  to
   the modern search engines.
  
   The output connector could make sense because you probably want to
  convert
   your wide data to a flat view in MongoDB to execute queries in a flat
  way.
   Here you probably don't need performance but some good queries for
  analysis
   to create your monthly or weekly reports with MongoDB.
  
   I know that MongoDB is not a search server but it is used a lot for
   creating dashboards and reports and the usage is similar to a search
   engine.
  
   What do you think about this?
  
   Please let me know.
   Thank you all.
  
   Cheers,
   Piergiorgio
  
   --
   Piergiorgio Lucidi
   Open Source ECM Specialist
   http://www.open4dev.com
  
   --
   http://www.open4dev.com
   Piergiorgio Lucidi http://www.open4dev.com
   Open Source ECM Specialist
   http://www.open4dev.comhttp://www.open4dev.com
 

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

MongoDB Repository and Output Connectors

2014-05-26 Thread Piergiorgio Lucidi

Hi guys,

I think that it could be very useful to add in ManifoldCF both the
connectors related to MongoDB.
During these days I have taken a look at MongoDB and I think that I can
start to implement these connectors.

The repository connector could make sense because MongoDB is a document
repository so some people could need to create smart indexes in a search
server, I'm thinking about huge repositories.
The MongoDB search engine could be very slow in some scenarios compared to
the modern search engines.

The output connector could make sense because you probably want to convert
your wide data to a flat view in MongoDB to execute queries in a flat way.
Here you probably don't need performance but some good queries for analysis
to create your monthly or weekly reports with MongoDB.

I know that MongoDB is not a search server but it is used a lot for
creating dashboards and reports and the usage is similar to a search engine.

What do you think about this?

Please let me know.
Thank you all.

Cheers,
Piergiorgio

-- 
Piergiorgio Lucidi
Open Source ECM Specialist
http://www.open4dev.com

Re: MongoDB Repository and Output Connectors

2014-05-26 Thread Piergiorgio Lucidi

Hi Karl,


2014-05-26 13:17 GMT+02:00 Wright, Karl karl.wri...@here.com:

   Hi Piergiorgio,

 When you say 'huge', how many documents do you mean?  Do you know of any
 specific installations, and if so, how many documents do they work with?


 I think it is fine to develop connectors for mongodb, but if the number of
 documents is truly huge, there will need to be a way of dividing up the
 task.


I imagine the typical usage of MongoDB, for example to keep User Generated
Contents (UGC), this means that the information is just a little section of
data for implementing social features dedicated to a website or a portal.

I'm sorry I don't have real-world numbers now but we could estimate
thousands of contents. Actually I'm working on a project that is starting
to use MongoDB and the use case is UGC.

Please consider that MongoDB divide its contents into databases, and for
each database you have different collections of contents.
This means that the connector should ask for a database and a specific
collection to work, this because MongoDB doesn't support the join of data
from different collections, it is not a relational database.

So I think that it should be very easy to implement in ManifoldCF.

Piergiorgio



 Karl

 Sent from my Windows Phone
  --
 From: Piergiorgio Lucidi
 Sent: 5/26/2014 6:01 AM
 To: dev@manifoldcf.apache.org
 Subject: MongoDB Repository and Output Connectors

  Hi guys,

 I think that it could be very useful to add in ManifoldCF both the
 connectors related to MongoDB.
 During these days I have taken a look at MongoDB and I think that I can
 start to implement these connectors.

 The repository connector could make sense because MongoDB is a document
 repository so some people could need to create smart indexes in a search
 server, I'm thinking about huge repositories.
 The MongoDB search engine could be very slow in some scenarios compared to
 the modern search engines.

 The output connector could make sense because you probably want to convert
 your wide data to a flat view in MongoDB to execute queries in a flat way.
 Here you probably don't need performance but some good queries for analysis
 to create your monthly or weekly reports with MongoDB.

 I know that MongoDB is not a search server but it is used a lot for
 creating dashboards and reports and the usage is similar to a search
 engine.

 What do you think about this?

 Please let me know.
 Thank you all.

 Cheers,
 Piergiorgio

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

 --
 http://www.open4dev.com
 Piergiorgio Lucidi http://www.open4dev.com
 Open Source ECM Specialist
  http://www.open4dev.comhttp://www.open4dev.com

Re: Board report

2014-05-06 Thread Piergiorgio Lucidi

+1 from me ;)

Piergiorgio


2014-05-02 15:57 GMT+02:00 Karl Wright daddy...@gmail.com:

 Here's my proposed May report.

 [REPORT] ManifoldCF

 Board Report, ManifoldCF PMC

 ManifoldCF PMC Chair: Karl Wright (kwri...@apache.org)
 Date: May 2014

 Project description
 ==

 ManifoldCF is an effort to provide an open source framework for connecting
 source content repositories like Microsoft Sharepoint and EMC Documentum,
 to target repositories or indexes, such as Apache Solr, OpenSearchServer
 or ElasticSearch. ManifoldCF also defines a security model for target
 repositories
 that permits them to enforce source-repository security policies.

 Releases
 

 ManifoldCF graduated from the Apache Incubator on May 16, 2012.  Since
 then, there
 have been seven major releases, including a 1.6 release on April 30, 2014.

 Committers and PMC membership
 =

 The last committer and PMC member we signed up was Graeme Seaton (graemes),
 on March
 2, 2014.  Other contributors have been approached, but have also declined
 to accept

 consideration for possible committership.  The most recent of these
 encounters took

 place in September, 2013.


 Mailing list activity
 =

 Mailing list has been active, with a wide range of topics.  Most of our
 connectors
 now have significant use cases and constituencies, and the connector family
 continues
 to grow.  Dev list comments for this period centered around voting for the
 major 1.5
 release, people looking for integration advice, etc.

 Committer and external contributions have been significant this cycle.  I
 am unaware
 of any mailing-list question that has gone unanswered.

 Outstanding issues
 ==

 None known.

 Branding
 

 We have reviewed the site branding guidelines and believe we are now
 compliant with
 these, with the possible exception of (TM) signs in logos from other Apache
 products
 that don't have any such marks.  Hopefully we will be able to correct this
 issue
 soon.


 Please let me know of any problems with this.

 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.6, RC1

2014-04-28 Thread Piergiorgio Lucidi

Ran all the tests.

+1 from me.

Piergiorgio


2014-04-24 17:41 GMT+02:00 Minoru Osuka minoru.os...@gmail.com:

 Hi,

 Ran test.

 +1 from me.

 Thanks,

 Minoru

 On Apr 22, 2014, at 18:40, Karl Wright daddy...@gmail.com wrote:

  I also added, for the main English site, a release verification page
 stub,
  called verify.xml, which is linked from the download page.  If you
 would
  like to fill out how to verify a release now, that would be great.
 
  Thanks!
  Karl
 
 
 
  On Thu, Apr 17, 2014 at 4:05 PM, Karl Wright daddy...@gmail.com wrote:
 
  Please feel free to check in your scripts directly into the
  release-scripts directory.
 
  Thanks!
  Karl
 
 
  On Thu, Apr 17, 2014 at 4:03 PM, Ahmet Arslan iori...@yahoo.com
 wrote:
 
  Hi,
 
  * ant all
  * mvn package
  * MD5, SHA512 (hashes) and GPG (signature) verification on artifacts
 
  passes for me.
 
  Here is my +1.
 
  I created check_signatures.sh that performs MD5, SHA512 (hashes) and
 GPG
  (signature) verification on artifacts. Somehow analogous to
 lucene/solr's
  smokeTestRelease.py
 
 
  Thanks,
  Ahmet
 
 
  On Thursday, April 17, 2014 4:20 AM, Karl Wright daddy...@gmail.com
  wrote:
  Ran all tests.
 
  +1 from me.
 
  Karl
 
 
 
  On Wed, Apr 16, 2014 at 7:23 PM, Karl Wright daddy...@gmail.com
 wrote:
 
  Since, in another thread, we've concluded that it is OK to release
 with
  gpg signatures rather than pgp signatures, I withdraw my -1.  I still
  need
  to check the candidate though before granting +1.
 
 
 
  On Wed, Apr 16, 2014 at 3:07 PM, Karl Wright daddy...@gmail.com
  wrote:
 
  Hi Ahmet,
 
  The signature files, as I feared, are in an incorrect format.
 
  I created ticket CONNECTORS-926 for this issue, and provided examples
  of
  correct format MD5 and SHA file contents.  I did not check .ASC, but
  you'll
  probably want to confirm that too.
 
  -1 from me for RC1 for this reason.
 
  Thanks,
  Karl
 
 
 
  On Wed, Apr 16, 2014 at 2:58 PM, Ahmet Arslan iori...@yahoo.com
  wrote:
 
  Hi,
 
  In my previous mail, somehow a whitespace appended to end of URLs.
 
  Here are clickable ones :
 
  Artifacts can be downloaded from:
  http://people.apache.org/~iorixxx/apache-manifoldcf-1.6-RC1/
 
  There is also a release tag at:
  https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.6-RC1/
 
  Ahmet
 
 
 
  On Wednesday, April 16, 2014 9:51 PM, Ahmet Arslan 
 iori...@yahoo.com
 
  wrote:
  Hello,
 
  Please vote on whether to release Apache ManifoldCF 1.6, RC1.
 
  This is obviously a major release, so voting will remain open for
 two
  weeks, unless the RC is respun.
 
  Artifacts can be downloaded from:
  http://people.apache.org/~iorixxx/apache-manifoldcf-1.6-RC1/
 
  There is also a release tag at:
  https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.6-RC1/
 
  Thanks,
  Ahmet
 
 
 
 
 
 
 

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.6, RC0

2014-04-16 Thread Piergiorgio Lucidi

Hi guys,

just a question, is it normal that the package for source is so large
(454M)?

Thank you.

Piergiorgio


2014-04-16 10:16 GMT+02:00 Ahmet Arslan iori...@yahoo.com:

 Hello,

 Please vote on whether to release Apache ManifoldCF 1.6, RC0.

 This is obviously a major release, so voting will remain open for two
 weeks, unless the RC is respun.

 The artifact can be downloaded from:

 http://people.apache.org/~iorixxx/apache-manifoldcf-1.6-RC0

 There is also a release tag at:

 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.6-RC0


 Thanks,

 Ahmet

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

[jira] [Updated] (CONNECTORS-602) Add a new Alfresco WebScript API Repository Connector

2014-04-09 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-602:
--

Fix Version/s: (was: ManifoldCF 1.6)
   ManifoldCF next

 Add a new Alfresco WebScript API Repository Connector
 -

 Key: CONNECTORS-602
 URL: https://issues.apache.org/jira/browse/CONNECTORS-602
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF next

   Original Estimate: 120h
  Remaining Estimate: 120h

 Taking a look at the Alfresco roadmap, it seems that during the next 18 
 months the CML SOAP API will not be supported anymore:
 [http://wiki.alfresco.com/wiki/Product_Roadmap#End-of-life_3]
 The history of this connector is not happy, during the first step I asked to 
 some Alfresco guys about the life of the SOAP API and I was assured that it 
 would not be finished.
 Anyway this is not the best API exposed by Alfresco, for many reasons 
 developers should use the REST API as their first choice. 
 The SOAP API was the only one API that allows to invoke Lucene queries 
 without implementing new customizations/extensions on Alfresco.
 Now we have an official confirmation that the life of this SOAP API ends 
 during the end of this year and the begin of the next one.
 My idea is to do a brainstorming with some Alfresco guys to understand 
 together which APIs we should use to reimplement the connector.
 I would like to use the current HTTP services without installing nothing on 
 the Alfresco side. But I have to check with them if this solution is feasible.
 I hope to have good news soon.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: New committer: Graeme Seaton

2014-03-10 Thread Piergiorgio Lucidi

A warm welcome from Rome!

Piergiorgio


2014-03-10 8:18 GMT+01:00 Karl Wright daddy...@gmail.com:

 The Project Management Committee (PMC) for Apache ManifoldCFhas asked
 Graeme Seaton to become a committer and we are pleased to announce
 that they have accepted.

 Graeme has be instrumental in driving the ManifoldCF project in
 the direction of scalability, and will no doubt continue to do
 so now that he has committer and PMC privileges.

  Being a committer enables easier contribution to theproject since
 there is no need to go via the patchsubmission process. This should
 enable better productivity.Being a PMC member enables assistance with
 the managementand to guide the direction of the project.

 Thanks,
 Karl Wright

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.5, RC4

2014-01-24 Thread Piergiorgio Lucidi

Ran all tests with Maven.

+1 from me.

Piergiorgio


2014/1/24 Karl Wright daddy...@gmail.com

 This is a major release of ManifoldCF that includes the following:

 - Federated authority support
 - Multiple authorization domains
 - ZooKeeper process coordination
 - Multiple agents processes
 - Support for SharePoint Claims-based authorization
 - An Email connector
 - A revamped look-and-feel

 This is obviously a major release, so voting will remain open until the end
 of January, unless the RC is respun.

 You can download the artifacts from
 http://people.apache.org/~kwright/apache-manifoldcf-1.5 .  There is also a
 release tag at
 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.5-RC4 .

 This RC includes changes to the dist directory organization so that jar
 files are not duplicated, saving 40MB from each binary download.  It also
 fixes an issue with connection limits in the zookeeper example.  Finally,
 it fixes a limitation in the CMIS connector (CONNECTORS-864) and a maven
 build problem (CONNECTORS-865).  Also fixes CONNECTORS-866 (the lockclean
 script), and two more Maven version issues.

 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.5, RC2

2014-01-23 Thread Piergiorgio Lucidi

 download the artifacts from
 http://people.apache.org/~kwright/apache-manifoldcf-1.5 .  There is also a
 release tag at
 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.5-RC1 .

 This RC includes changes to the dist directory organization so that jar
 files are not duplicated, saving 40MB from each binary download.  It also
 fixes an issue with connection limits in the zookeeper example.  Finally,
 it fixes a limitation in the CMIS connector (CONNECTORS-864) and a maven
 build problem (CONNECTORS-865).

 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

[jira] [Commented] (CONNECTORS-864) Alfresco only provides 100 search results using CMIS connector with Apache ManifoldCF.

2014-01-20 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13876358#comment-13876358
 ] 

Piergiorgio Lucidi commented on CONNECTORS-864:
---

It seems that this is an Alfresco specific limitation about the CMIS search.

We could try to fix it using the following approach documented in the Apache 
Chemistry mailing list:

http://mail-archives.apache.org/mod_mbox/chemistry-dev/201110.mbox/%3c5843_1317719934_4e8acf7e_5843_4730_1_8af751cd48f5a14aada5e935bb6a406501ebbb596...@thsonea01cms03p.one.grp%3E

 

 Alfresco only provides 100 search results using CMIS connector with Apache 
 ManifoldCF.
 --

 Key: CONNECTORS-864
 URL: https://issues.apache.org/jira/browse/CONNECTORS-864
 Project: ManifoldCF
  Issue Type: Bug
  Components: CMIS connector
Affects Versions: ManifoldCF 1.4.1
 Environment: Alfresco 4.2, Windows 7 with manifold 1.4.1  solr 4.0.0
Reporter: lalit
Assignee: Piergiorgio Lucidi
Priority: Blocker
 Fix For: ManifoldCF 1.6

 Attachments: alfresco-job.PNG, cmis connection.PNG, solr.PNG


 I am using solr 4.0.0 as output channel for manifold 1.4.1. I have also 
 created a repository connection for alfresco 4.2 which is working fine. Next 
 i have configured a job for indexing alfresco repo for all content items. But 
 it only return first 100 items to solr. 
 I tried changing configurations from both manifold  solr perspective but 
 still i am getting 100 results only.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Resolved] (CONNECTORS-865) Wrong version of the parent pom in the alfresco-4-war

2014-01-20 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-865.
---

Resolution: Fixed
  Assignee: Piergiorgio Lucidi

r1559684.

 Wrong version of the parent pom in the alfresco-4-war
 -

 Key: CONNECTORS-865
 URL: https://issues.apache.org/jira/browse/CONNECTORS-865
 Project: ManifoldCF
  Issue Type: Bug
  Components: Build
Affects Versions: ManifoldCF 1.5
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi

 The build is broken the module test-materials/alfresco-4-war has a wrong 
 version of his parent module. It is pointing to the old one 1.5-SNAPSHOT



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: [VOTE] Release Apache ManifoldCF Plugin for Solr 3.x, RC1

2013-12-03 Thread Piergiorgio Lucidi

Ran all tests

+1 from me.

Piergiorgio


2013/12/3 Karl Wright daddy...@gmail.com

 This release of the plugin extends its capabilities to include multi-domain
 user names, to be released in ManifoldCF 1.5.

 The artifact can be downloaded from:

 http://people.apache.org/~kwright/apache-manifoldcf-solr-3.x-plugin

 There is also a tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/solr-3.x/tags/release-1.1-RC1
 
 https://svn.apache.org/repos/asf/manifoldcf/integration/solr-3.x/tags/release-1.1-RC0
 

 This RC1 release fixes a signature problem only; no source changes.

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF Plugin for Apache Solr 4.x 1.1, RC0

- Ran all the tests

+1 from me.

Piergiorgio


2013/11/24 Karl Wright daddy...@gmail.com

 This release of the plugin extends its capabilities to include multi-domain
 user names, to be released in ManifoldCF 1.5.

 The artifact can be downloaded from:

 http://people.apache.org/~kwright/apache-manifoldcf-solr-4.x-plugin

 There is also a tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/solr-4.x/tags/release-1.1-RC0

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF Plugin for Apache Solr 3.x 1.1, RC0

Ran all tests

+1 from me.

Piergiorgio


2013/11/24 Karl Wright daddy...@gmail.com

 This release of the plugin extends its capabilities to include multi-domain
 user names, to be released in ManifoldCF 1.5.

 The artifact can be downloaded from:

 http://people.apache.org/~kwright/apache-manifoldcf-solr-3.x-plugin

 There is also a tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/solr-3.x/tags/release-1.1-RC0

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF Plugin for ElasticSearch 1.1, RC0

Ran all tests

+1 from me.

Piergiorgio


2013/11/24 Karl Wright daddy...@gmail.com

 This release of the plugin extends its capabilities to include multi-domain
 user names, to be released in ManifoldCF 1.5.

 The artifact can be downloaded from:

 http://people.apache.org/~kwright/apache-manifoldcf-elasticsearch-plugin

 There is also a tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/elasticsearch/tags/release-1.1-RC0

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF Plugin for SharePoint 2010 0.4, RC0

Checked the binary and source package.

+1 from me.

Piergiorgio


2013/11/24 Karl Wright daddy...@gmail.com

 This release adds required functionality to return usable URLs for list
 items.  See CONNECTORS-813.

 You can download the artifact from:

 http://people.apache.org/~kwright/apache-manifoldcf-sharepoint-2010-plugin

 There is also a tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2010/tags/release-0.4-RC0

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.4.1, RC1

2013-11-14 Thread Piergiorgio Lucidi

+1 from me.

Ran all tests.

Piergiorgio


2013/11/13 Karl Wright daddy...@gmail.com

 Please vote on whether to release Apache ManifoldCF 1.4.1, RC1.

 You can download the release from
 http://people.apache.org/~kwright/apache-manifoldcf-1.4.1.

 There is also a release tag at:

 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.4.1-RC1
 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.4.1-RC0

 This release is being made to fix four critical bugs:
 CONNECTORS-796
 CONNECTORS-797
 CONNECTORS-806
 CONNECTORS-807

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: Should we release a 1.4.1?

2013-11-10 Thread Piergiorgio Lucidi

It seems that these are very critical issues so probably we should release
this new version as a service pack for the 1.4 release.

+1 from me.

Piergiorgio


2013/11/5 Karl Wright daddy...@gmail.com

 Fixes that are going to require a number of people apply patches are:

 CONNECTORS-796
 CONNECTORS-797

 Should we release a 1.4.1 to address these?
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.4, RC1

2013-10-28 Thread Piergiorgio Lucidi

- Ran all the tests

+1 from me

Piergiorgio


2013/10/28 Karl Wright daddy...@gmail.com

 Still looking for one more vote...
 Karl


 On Wed, Oct 23, 2013 at 10:38 AM, Erlend Garåsen e.f.gara...@usit.uio.no
 wrote:

 
  +1
 
  Looks good.
 
  1. Deployed the binary version on Resin and did a test crawl.
  2. Built the source version using Ant
  3. Ran UI tests
  4. Built docs (ant doc) using Forest 0.9
  5. Ran ant test
  6. Ran the single process model within the example dir, started the web
  crawler and posted to Solr 4
  7. Ran multiprocess example, started the web crawler and posted to Solr.
 
  Erlend
 
 
  On 10/22/13 12:05 AM, Karl Wright wrote:
 
  Please vote on whether to release Apache ManifoldCF 1.4, RC1.
 
  The release candidate can be downloaded from:
 
  http://people.apache.org/~**kwright/apache-manifoldcf-1.4
 http://people.apache.org/~kwright/apache-manifoldcf-1.4
 
  There is a tag at:
 
  http://svn.apache.org/repos/**asf/manifoldcf/tags/release-1.**4-RC1
 http://svn.apache.org/repos/asf/manifoldcf/tags/release-1.4-RC1
  http://svn.apache.org/**repos/asf/manifoldcf/tags/**release-1.4-RC0
 http://svn.apache.org/repos/asf/manifoldcf/tags/release-1.4-RC0
  
 
 
  This release contains a substantial refactoring of the SharePoint
  connector, as
  well as new features including attachment crawling.  Proxy support for
 the
  wiki
  and jira connectors has also been added.
 
  It also fixes CONNECTORS-790 and CONNECTORS-791.
 
  Vote will remain open for at least 72 hours.
 
  Thanks,
  Karl
 
 
 

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF SharePoint 2007 Plugin 0.5 RC0

2013-10-08 Thread Piergiorgio Lucidi

Hi,

- checked all the signatures
- verified the binary package
- verified the source package

+1 from me.

Piergiorgio


2013/9/11 Karl Wright daddy...@gmail.com

 Please vote whether to release a new version of the Apache ManifoldCF
 SharePoint 2007 Plugin, version 0.5, RC0.

 The artifact can be located at:


 http://people.apache.org/~kwright/apache-manifoldcf-sharepoint-2007-plugin-0.5

 There is also an SVN tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2007/tags/release-0.5-RC0

 This release of the plugin removes the requirement that the
 MCPermissions.asmx service be able to communicate with SharePoint's
 Permissions.asmx service. This communication has turned out to be
 problematic in the field under certain SharePoint configurations.

 Vote will remain open at least 72 hours.

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.3, RC4

2013-07-26 Thread Piergiorgio Lucidi

- Ran all the integration tests
- Tried the Google Drive connector
- Tried the CMIS Connector

+1 from me


2013/7/26 Karl Wright daddy...@gmail.com

 Please vote on whether we should release Apache ManifoldCF 1.3, RC4.

 You can download the release candidate from:
 http://people.apache.org/~kwright/apache-manifoldcf-1.3

 There is an svn tag at:
 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.3-RC4
 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.3-RC0

 This RC fixes CONNECTORS-761.  Previous RC's fixed CONNECTORS-760,
 CONNECTORS-757, and CONNECTORS-759.

 ManifoldCF 1.3 contains a large number of improvements over 1.2,
 specifically:

 - New Google Drive, Jira, and Hadoop File System connectors
 - A new connector type (a username mapper), and a Regular Expression mapper
 - Major crawler UI security improvements, including validation of
 administrative credentials
 - Many other fixes and improvements, which you can browse at

 https://svn.apache.org/repos/asf/manifoldcf/branches/release-1.3-branch/CHANGES.txt

 This vote will be held open until Monday (July 29) at 7:00AM EDT, unless
 cancelled.  But please evaluate the package at the earliest opportunity in
 case we need to respin.

 Thanks,
 Karl

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [WITHDRAW][VOTE] Release Apache ManifoldCF 1.3, RC2

2013-07-25 Thread Piergiorgio Lucidi

- Ran integration tests of the source bundle
- Tried the binary using the Google Drive connector and now I don't see any
issues

+1 from me


2013/7/25 Karl Wright daddy...@gmail.com

 While everyone is waiting for me to spin a new RC this evening, it would be
 good to keep evaluating the current RC2 kit to see if there are any other
 issues they can find.

 Thanks!
 Karl



 On Thu, Jul 25, 2013 at 7:29 AM, Karl Wright daddy...@gmail.com wrote:

  Withdrawn due to CONNECTORS-760.
 
  Karl
 
 
 
  On Thu, Jul 25, 2013 at 6:27 AM, Minoru Osuka minoru.os...@gmail.com
 wrote:
 
  Hi Karl,
 
  HDFSRepositoryConnector's version string is always start with '-'.
 
  -1
 
  https://issues.apache.org/jira/browse/CONNECTORS-760
 
 
  Thanks,
  Minoru
 
 
  Minoru Osuka
  minoru.os...@gmail.com
 
 
 
 
  On Jul 24, 2013, at 6:54 PM, Karl Wright daddy...@gmail.com wrote:
 
   Please vote on whether we should release Apache ManifoldCF 1.3, RC2.
  
   You can download the release candidate from:
   http://people.apache.org/~kwright/apache-manifoldcf-1.3
  
   There is an svn tag at:
   https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.3-RC2
  https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.3-RC0
  
   This RC fixes CONNECTORS-757 and CONNECTORS-759.
  
   ManifoldCF 1.3 contains a large number of improvements over 1.2,
   specifically:
  
   - New Google Drive, Jira, and Hadoop File System connectors
   - A new connector type (a username mapper), and a Regular Expression
  mapper
   - Major crawler UI security improvements, including validation of
   administrative credentials
   - Many other fixes and improvements, which you can browse at
  
 
 https://svn.apache.org/repos/asf/manifoldcf/branches/release-1.3-branch/CHANGES.txt
  
   Because of the number of changes, and the time of the year this is,
 this
   vote will be held open until Sunday (July 28) at 5:00PM EDT, unless
   cancelled.  But please evaluate the package at the earliest
 opportunity
  in
   case we need to respin.
  
   Thanks,
   Karl
 
 
 

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF 1.3, RC2

2013-07-24 Thread Piergiorgio Lucidi

Just a check for the LDAP issue


2013/7/24 Karl Wright daddy...@gmail.com

 - Verified login works with correct content-type
 - Reran ant-ratsources
 - Checked sizes of packages for consistency with previous RC's

 +1 from me.

 Karl



 On Wed, Jul 24, 2013 at 5:54 AM, Karl Wright daddy...@gmail.com wrote:

  Please vote on whether we should release Apache ManifoldCF 1.3, RC2.
 
  You can download the release candidate from:
  http://people.apache.org/~kwright/apache-manifoldcf-1.3
 
  There is an svn tag at:
  https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.3-RC2
 https://svn.apache.org/repos/asf/manifoldcf/tags/release-1.3-RC0
 
  This RC fixes CONNECTORS-757 and CONNECTORS-759.
 
  ManifoldCF 1.3 contains a large number of improvements over 1.2,
  specifically:
 
  - New Google Drive, Jira, and Hadoop File System connectors
  - A new connector type (a username mapper), and a Regular Expression
 mapper
  - Major crawler UI security improvements, including validation of
  administrative credentials
  - Many other fixes and improvements, which you can browse at
 
 https://svn.apache.org/repos/asf/manifoldcf/branches/release-1.3-branch/CHANGES.txt
 
  Because of the number of changes, and the time of the year this is, this
  vote will be held open until Sunday (July 28) at 5:00PM EDT, unless
  cancelled.  But please evaluate the package at the earliest opportunity
 in
  case we need to respin.
 
  Thanks,
  Karl
 

 --
 Piergiorgio Lucidi
 Open Source ECM Specialist
 http://www.open4dev.com

[jira] [Created] (CONNECTORS-757) NPE crawling with the GoogleDrive Connector

2013-07-22 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-757:
-

 Summary: NPE crawling with the GoogleDrive Connector
 Key: CONNECTORS-757
 URL: https://issues.apache.org/jira/browse/CONNECTORS-757
 Project: ManifoldCF
  Issue Type: Bug
  Components: GoogleDrive connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


Trying to use the GoogleDrive connector with my personal account ManifoldCF 
returns the following exception:
{code}
FATAL 2013-07-22 17:01:30,838 (Worker thread '8') - Error tossed: null
java.lang.NullPointerException
at 
org.apache.manifoldcf.crawler.connectors.googledrive.GoogleDriveRepositoryConnector.processDocuments(GoogleDriveRepositoryConnector.java:1064)
at 
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
{code}

It seems that the following instruction is causing the issue:
{code}
// Get the file length
long fileLength = googleFile.getFileSize();
{code}

Some files maybe doesn't have size, probably I have many different types of 
contents in my Drive account and I didn't changed the default query. But I 
think that should be fixed anyway.

What do you think?



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-757) NPE crawling with the GoogleDrive Connector

2013-07-22 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13715283#comment-13715283
 ] 

Piergiorgio Lucidi commented on CONNECTORS-757:
---

+1

 NPE crawling with the GoogleDrive Connector
 ---

 Key: CONNECTORS-757
 URL: https://issues.apache.org/jira/browse/CONNECTORS-757
 Project: ManifoldCF
  Issue Type: Bug
  Components: GoogleDrive connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3

   Original Estimate: 24h
  Remaining Estimate: 24h

 Trying to use the GoogleDrive connector with my personal account ManifoldCF 
 returns the following exception:
 {code}
 FATAL 2013-07-22 17:01:30,838 (Worker thread '8') - Error tossed: null
 java.lang.NullPointerException
   at 
 org.apache.manifoldcf.crawler.connectors.googledrive.GoogleDriveRepositoryConnector.processDocuments(GoogleDriveRepositoryConnector.java:1064)
   at 
 org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
   at 
 org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
 {code}
 It seems that the following instruction is causing the issue:
 {code}
 // Get the file length
 long fileLength = googleFile.getFileSize();
 {code}
 Some files maybe doesn't have size, probably I have many different types of 
 contents in my Drive account and I didn't changed the default query. But I 
 think that should be fixed anyway.
 What do you think?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-755) ant rat-sources finds unlicensed files in alfresco connector

2013-07-19 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-755.
---

Resolution: Fixed

r1504825.

 ant rat-sources finds unlicensed files in alfresco connector
 

 Key: CONNECTORS-755
 URL: https://issues.apache.org/jira/browse/CONNECTORS-755
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.3
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Priority: Blocker
 Fix For: ManifoldCF 1.3


 {code}
 [rat:report] Unapproved licenses:
 [rat:report]
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /alfresco/extension/dev-log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/webapp/WE
 B-INF/web.xml
 [rat:report]
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-755) ant rat-sources finds unlicensed files in alfresco connector

2013-07-19 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13713546#comment-13713546
 ] 

Piergiorgio Lucidi commented on CONNECTORS-755:
---

r1504825.

 ant rat-sources finds unlicensed files in alfresco connector
 

 Key: CONNECTORS-755
 URL: https://issues.apache.org/jira/browse/CONNECTORS-755
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.3
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Priority: Blocker
 Fix For: ManifoldCF 1.3


 {code}
 [rat:report] Unapproved licenses:
 [rat:report]
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /alfresco/extension/dev-log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/webapp/WE
 B-INF/web.xml
 [rat:report]
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Issue Comment Deleted] (CONNECTORS-755) ant rat-sources finds unlicensed files in alfresco connector

2013-07-19 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-755:
--

Comment: was deleted

(was: r1504825.)

 ant rat-sources finds unlicensed files in alfresco connector
 

 Key: CONNECTORS-755
 URL: https://issues.apache.org/jira/browse/CONNECTORS-755
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.3
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Priority: Blocker
 Fix For: ManifoldCF 1.3


 {code}
 [rat:report] Unapproved licenses:
 [rat:report]
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /alfresco/extension/dev-log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/webapp/WE
 B-INF/web.xml
 [rat:report]
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-755) ant rat-sources finds unlicensed files in alfresco connector

2013-07-18 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712266#comment-13712266
 ] 

Piergiorgio Lucidi commented on CONNECTORS-755:
---

Ok we can remove these three files that were created by the Alfresco Maven 
Archetype. 
We don't need to override one of these for executing integration tests.

I have just tested that removing these files the integration tests works 
correctly.
I suggest to remove these files.

How we want to solve?

 ant rat-sources finds unlicensed files in alfresco connector
 

 Key: CONNECTORS-755
 URL: https://issues.apache.org/jira/browse/CONNECTORS-755
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.3
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Priority: Blocker
 Fix For: ManifoldCF 1.3


 {code}
 [rat:report] Unapproved licenses:
 [rat:report]
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /alfresco/extension/dev-log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/webapp/WE
 B-INF/web.xml
 [rat:report]
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-755) ant rat-sources finds unlicensed files in alfresco connector

2013-07-18 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712404#comment-13712404
 ] 

Piergiorgio Lucidi commented on CONNECTORS-755:
---

All the files that you see in the project are related to the overlay process 
against the default Alfresco WAR.
So if you put a web.xml, the Maven lifecycle will override the default one with 
yours, otherwise it will leave the default.

So I think that we can remove these files in this way we are sure to use the 
default settings of any Alfresco installation.

The license is Apache 2.0:
https://code.google.com/p/maven-alfresco-archetypes/


 ant rat-sources finds unlicensed files in alfresco connector
 

 Key: CONNECTORS-755
 URL: https://issues.apache.org/jira/browse/CONNECTORS-755
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.3
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Priority: Blocker
 Fix For: ManifoldCF 1.3


 {code}
 [rat:report] Unapproved licenses:
 [rat:report]
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /alfresco/extension/dev-log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/resources
 /log4j.properties
 [rat:report]   
 C:/wip/mcf/trunk/test-materials/alfresco-4-war/src/main/webapp/WE
 B-INF/web.xml
 [rat:report]
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-553) [GSoC] Create an Email connector for Apache ManifoldCF

2013-06-27 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-553:
--

Affects Version/s: (was: ManifoldCF 1.3)
   ManifoldCF next

 [GSoC] Create an Email connector for Apache ManifoldCF
 --

 Key: CONNECTORS-553
 URL: https://issues.apache.org/jira/browse/CONNECTORS-553
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Email connector
Affects Versions: ManifoldCF next
Reporter: Erlend Garåsen
Assignee: Piergiorgio Lucidi
  Labels: gsoc, gsoc2013, mentor
 Fix For: ManifoldCF 1.3


 Apache ManifoldCF is an effort to provide an open source framework for 
 connecting source content repositories like Microsoft Sharepoint and EMC 
 Documentum, to target repositories or indexes, such as Apache Solr, Open 
 Search Server, or ElasticSearch. Apache ManifoldCF also defines a security 
 model for target repositories that permits them to enforce source-repository 
 security policies.
 ManifoldCF is based on a framework structure that allows developers to 
 implement new connectors for repositories, search servers and authorities 
 servers [1].
 Proposal:
 Implement an email connector that should support both IMAP and POP3 servers 
 as well as SSL/TLS encryption and server certificates.
 Skills needed:
 - Java programming
 - IMAP and POP protocols
 - XML
 [1] - http://manifoldcf.apache.org/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-553) [GSoC] Create an Email connector for Apache ManifoldCF

2013-06-27 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-553:
--

Fix Version/s: (was: ManifoldCF 1.3)
   ManifoldCF next
Affects Version/s: (was: ManifoldCF next)
   ManifoldCF 1.2

 [GSoC] Create an Email connector for Apache ManifoldCF
 --

 Key: CONNECTORS-553
 URL: https://issues.apache.org/jira/browse/CONNECTORS-553
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Email connector
Affects Versions: ManifoldCF 1.2
Reporter: Erlend Garåsen
Assignee: Piergiorgio Lucidi
  Labels: gsoc, gsoc2013, mentor
 Fix For: ManifoldCF next


 Apache ManifoldCF is an effort to provide an open source framework for 
 connecting source content repositories like Microsoft Sharepoint and EMC 
 Documentum, to target repositories or indexes, such as Apache Solr, Open 
 Search Server, or ElasticSearch. Apache ManifoldCF also defines a security 
 model for target repositories that permits them to enforce source-repository 
 security policies.
 ManifoldCF is based on a framework structure that allows developers to 
 implement new connectors for repositories, search servers and authorities 
 servers [1].
 Proposal:
 Implement an email connector that should support both IMAP and POP3 servers 
 as well as SSL/TLS encryption and server certificates.
 Skills needed:
 - Java programming
 - IMAP and POP protocols
 - XML
 [1] - http://manifoldcf.apache.org/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-602) Add a new Alfresco WebScript API Repository Connector

2013-06-27 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-602:
--

Fix Version/s: (was: ManifoldCF 1.3)
   ManifoldCF next

 Add a new Alfresco WebScript API Repository Connector
 -

 Key: CONNECTORS-602
 URL: https://issues.apache.org/jira/browse/CONNECTORS-602
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF next

   Original Estimate: 120h
  Remaining Estimate: 120h

 Taking a look at the Alfresco roadmap, it seems that during the next 18 
 months the CML SOAP API will not be supported anymore:
 [http://wiki.alfresco.com/wiki/Product_Roadmap#End-of-life_3]
 The history of this connector is not happy, during the first step I asked to 
 some Alfresco guys about the life of the SOAP API and I was assured that it 
 would not be finished.
 Anyway this is not the best API exposed by Alfresco, for many reasons 
 developers should use the REST API as their first choice. 
 The SOAP API was the only one API that allows to invoke Lucene queries 
 without implementing new customizations/extensions on Alfresco.
 Now we have an official confirmation that the life of this SOAP API ends 
 during the end of this year and the begin of the next one.
 My idea is to do a brainstorming with some Alfresco guys to understand 
 together which APIs we should use to reimplement the connector.
 I would like to use the current HTTP services without installing nothing on 
 the Alfresco side. But I have to check with them if this solution is feasible.
 I hope to have good news soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-418) Re-examine the call to the non-published method on the next release of OpenCMIS

2013-06-27 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-418:
--

Fix Version/s: (was: ManifoldCF 1.3)
   ManifoldCF next

 Re-examine the call to the non-published method on the next release of 
 OpenCMIS
 ---

 Key: CONNECTORS-418
 URL: https://issues.apache.org/jira/browse/CONNECTORS-418
 Project: ManifoldCF
  Issue Type: Task
  Components: CMIS connector
Affects Versions: ManifoldCF 1.0
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF next


 We have to re-examine the way that we are using to retrieve the document uri 
 (content stream).
 Now we are using a way suggested by Florian Muller but it seems that it could 
 be the possibility of a future public method in the OpenCMIS API.
 Here the link of the suggestion:
 http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201009.mbox/%3c13092343.447851284629268276.javamail.r...@zimbra.alfresco.com%3E

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-602) Add a new Alfresco WebScript API Repository Connector

2013-06-27 Thread Piergiorgio Lucidi (JIRA)

[
https://issues.apache.org/jira/browse/CONNECTORS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13694711#comment-13694711
]

Piergiorgio Lucidi commented on CONNECTORS-602:
---

Due to the Alfresco roadmap this improvement is actually stopped.
We are waiting some informations from Alfresco to understand how to use their
new client REST.

Add a new Alfresco WebScript API Repository Connector
-

Key: CONNECTORS-602
URL: https://issues.apache.org/jira/browse/CONNECTORS-602
Project: ManifoldCF
Issue Type: New Feature
Components: Alfresco connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF next

Original Estimate: 120h
Remaining Estimate: 120h

Taking a look at the Alfresco roadmap, it seems that during the next 18
months the CML SOAP API will not be supported anymore:
[http://wiki.alfresco.com/wiki/Product_Roadmap#End-of-life_3]
The history of this connector is not happy, during the first step I asked to
some Alfresco guys about the life of the SOAP API and I was assured that it
would not be finished.
Anyway this is not the best API exposed by Alfresco, for many reasons
developers should use the REST API as their first choice.
The SOAP API was the only one API that allows to invoke Lucene queries
without implementing new customizations/extensions on Alfresco.
Now we have an official confirmation that the life of this SOAP API ends
during the end of this year and the begin of the next one.
My idea is to do a brainstorming with some Alfresco guys to understand
together which APIs we should use to reimplement the connector.
I would like to use the current HTTP services without installing nothing on
the Alfresco side. But I have to check with them if this solution is feasible.
I hope to have good news soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (CONNECTORS-717) Alfresco Connector needs a new parameter for the Socket Timeout

2013-06-20 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi reopened CONNECTORS-717:
---


We have to update the documentation for the Alfresco connector to describe and 
show the new parameter also in screenshots.

 Alfresco Connector needs a new parameter for the Socket Timeout
 ---

 Key: CONNECTORS-717
 URL: https://issues.apache.org/jira/browse/CONNECTORS-717
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 During the crawling process against an Alfresco repository could be useful in 
 some cases to make some tuning of the Alfresco Web Services Client.
 The typical exception returned from the client is the following:
 {code}
  WARN 2013-06-14 15:25:29,836 (Worker thread '34') - Alfresco: IOException 
 closing file input stream: ; nested exception is: 
   java.net.SocketTimeoutException: Read timed out
 AxisFault
  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
  faultSubcode: 
  faultString: java.net.SocketTimeoutException: Read timed out
  faultActor: 
  faultNode: 
  faultDetail: 
   
 {http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException: Read 
 timed out
   at java.net.SocketInputStream.socketRead0(Native Method)
   at java.net.SocketInputStream.read(SocketInputStream.java:150)
   at java.net.SocketInputStream.read(SocketInputStream.java:121)
   at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
   at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
   at 
 org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)
   at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
   at 
 org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
   at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
   at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
   at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
   at org.apache.axis.client.Call.invoke(Call.java:2767)
   at org.apache.axis.client.Call.invoke(Call.java:2443)
   at org.apache.axis.client.Call.invoke(Call.java:2366)
   at org.apache.axis.client.Call.invoke(Call.java:1812)
   at 
 org.alfresco.webservice.repository.RepositoryServiceSoapBindingStub.queryChildren(RepositoryServiceSoapBindingStub.java:800)
   at 
 org.apache.manifoldcf.crawler.connectors.alfresco.ContentModelUtils.isFolder(ContentModelUtils.java:65)
   at 
 org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:839)
   at 
 org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
   at 
 org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
   {http://xml.apache.org/axis/}hostname:iPjNew.local
 java.net.SocketTimeoutException: Read timed out
   at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
   at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
   at 
 org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
   at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
   at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
   at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
   at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
   at org.apache.axis.client.Call.invoke(Call.java:2767)
   at org.apache.axis.client.Call.invoke(Call.java:2443)
   at org.apache.axis.client.Call.invoke(Call.java:2366)
   at org.apache.axis.client.Call.invoke(Call.java:1812)
   at 
 org.alfresco.webservice.repository.RepositoryServiceSoapBindingStub.queryChildren(RepositoryServiceSoapBindingStub.java:800)
   at 
 org.apache.manifoldcf.crawler.connectors.alfresco.ContentModelUtils.isFolder(ContentModelUtils.java:65)
   at 
 org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:839)
   at 
 org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
   at 
 org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
 Caused by: java.net.SocketTimeoutException: Read timed out
   at java.net.SocketInputStream.socketRead0(Native Method)
   at java.net.SocketInputStream.read

[jira] [Created] (CONNECTORS-720) We need some Japanese translations for the new parameter of Alfresco Connector

2013-06-17 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-720:
-

 Summary: We need some Japanese translations for the new parameter 
of Alfresco Connector
 Key: CONNECTORS-720
 URL: https://issues.apache.org/jira/browse/CONNECTORS-720
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


We have to add and translate in Japanese all the properties related to the new 
parameter socketTimeout:
{code}
AlfrescoConnector.SocketTimeoutColon=Socket Timeout:
AlfrescoConnector.SocketTimeoutEquals=socketTimeout=
AlfrescoConnector.TheSocketTimeoutMustNotBeNull=The connector socket timeout 
must not be null
AlfrescoConnector.TheSocketTimeoutMustBeAValidInteger=The connector socket 
timeout must be a valid integer
{code}
Does any Japanese guy want to contribute here? :) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-720) We need some Japanese translations for the new parameter of Alfresco Connector

2013-06-17 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13685707#comment-13685707
 ] 

Piergiorgio Lucidi commented on CONNECTORS-720:
---

I have added the new keys in the properties file (r1493844.)

 We need some Japanese translations for the new parameter of Alfresco Connector
 --

 Key: CONNECTORS-720
 URL: https://issues.apache.org/jira/browse/CONNECTORS-720
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3

   Original Estimate: 1h
  Remaining Estimate: 1h

 We have to add and translate in Japanese all the properties related to the 
 new parameter socketTimeout:
 {code}
 AlfrescoConnector.SocketTimeoutColon=Socket Timeout:
 AlfrescoConnector.SocketTimeoutEquals=socketTimeout=
 AlfrescoConnector.TheSocketTimeoutMustNotBeNull=The connector socket timeout 
 must not be null
 AlfrescoConnector.TheSocketTimeoutMustBeAValidInteger=The connector socket 
 timeout must be a valid integer
 {code}
 Does any Japanese guy want to contribute here? :) 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-716) java.lang.StackOverflowError with Java 1.7

2013-06-14 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-716:
-

 Summary: java.lang.StackOverflowError with Java 1.7
 Key: CONNECTORS-716
 URL: https://issues.apache.org/jira/browse/CONNECTORS-716
 Project: ManifoldCF
  Issue Type: Bug
  Components: Framework agents process
Affects Versions: ManifoldCF 1.2
 Environment: Mac OS X 10.8.4, ManifoldCF compiled with JDK 1.7 update 
21
Reporter: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


Trying to crawl big repositories it seems that Manifold returns the following 
exception:

{code}
FATAL 2013-06-14 11:23:42,017 (Worker thread '37') - Error tossed: null
java.lang.StackOverflowError
at 
org.apache.manifoldcf.agents.interfaces.RepositoryDocument.addField(RepositoryDocument.java:346)
at 
org.apache.manifoldcf.agents.interfaces.RepositoryDocument.addField(RepositoryDocument.java:346)
at 
org.apache.manifoldcf.agents.interfaces.RepositoryDocument.addField(RepositoryDocument.java:346)
at 
org.apache.manifoldcf.agents.interfaces.RepositoryDocument.addField(RepositoryDocument.java:346)
at 
org.apache.manifoldcf.agents.interfaces.RepositoryDocument.addField(RepositoryDocument.java:346)
at 

{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-713) Alfresco connector needs to deal with IOExceptions better

2013-06-14 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-713.
---

Resolution: Fixed

r1493075.

 Alfresco connector needs to deal with IOExceptions better
 -

 Key: CONNECTORS-713
 URL: https://issues.apache.org/jira/browse/CONNECTORS-713
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 The Alfresco Connector deals with IOExceptions by just tossing a wrapping 
 ManifoldCFException.  This is a problem for several reasons.  First, 
 IOExceptions are usually transient, and should mostly be converted into 
 ServiceInterruptions instead.  Second, IOExceptions *may* represent thread 
 interrupts, in which case the software should instead throw new 
 ManifoldCFException(msg, ManifoldCFException.INTERRUPTED).
 A good model is to have a method called void handleIOException(IOException) 
 throws ServiceInterruption, ManifoldCFException called from everywhere that 
 IOExceptions are caught.  Usually they get implemented something like this, 
 although you can also throw ServiceInterruptions with different 
 characteristics dependent on the kind of IOException being caught:
 {code}
   private static void handleIOException(IOException e)
 throws ManifoldCFException, ServiceInterruption {
 if (!(e instanceof java.net.SocketTimeoutException)  (e instanceof 
 InterruptedIOException)) {
   throw new ManifoldCFException(Interrupted:  + e.getMessage(), e,
 ManifoldCFException.INTERRUPTED);
 }
 long currentTime = System.currentTimeMillis();
 throw new ServiceInterruption(IO exception: +e.getMessage(), e, 
 currentTime + 30L,
   currentTime + 3 * 60 * 6L,-1,false);
   }
 {code}
 The exception returned is the following:
 {code}
 FATAL 2013-06-11 16:40:03,441 (Worker thread '12') - Error tossed: Unable to 
 get content as inputStream.
 org.alfresco.webservice.util.WebServiceException: Unable to get content as 
 inputStream.
 at 
 org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:139)
 at 
 org.apache.manifoldcf.crawler.connectors.alfresco.ContentReader.getBinary(ContentReader.java:73)
 at 
 org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:824)
 at 
 org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
 at 
 org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
 Caused by: java.io.IOException: Server returned HTTP response code: 500 for 
 URL: 
 http://localhost:9090/alfresco/download/direct/workspace/SpacesStore/1e4f7fe4-d58a-4d69-b26f-3349546af7ca/testdata2.txt?ticket=TICKET_33ac1ec81c5b0ca9d024f0489df115286d0ac030
 at 
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
 at 
 org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:135)
 ... 4 more
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-717) Alfresco Connector needs a new parameter for the Socket Timeout

2013-06-14 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-717:
-

 Summary: Alfresco Connector needs a new parameter for the Socket 
Timeout
 Key: CONNECTORS-717
 URL: https://issues.apache.org/jira/browse/CONNECTORS-717
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


During the crawling process against an Alfresco repository could be useful in 
some cases to make some tuning of the Alfresco Web Services Client.

The typical exception returned from the client is the following:

{code}
 WARN 2013-06-14 15:25:29,836 (Worker thread '34') - Alfresco: IOException 
closing file input stream: ; nested exception is: 
java.net.SocketTimeoutException: Read timed out
AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: java.net.SocketTimeoutException: Read timed out
 faultActor: 
 faultNode: 
 faultDetail: 

{http://xml.apache.org/axis/}stackTrace:java.net.SocketTimeoutException: Read 
timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254)
at 
org.apache.axis.transport.http.HTTPSender.readHeadersFromSocket(HTTPSender.java:583)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at 
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at 
org.alfresco.webservice.repository.RepositoryServiceSoapBindingStub.queryChildren(RepositoryServiceSoapBindingStub.java:800)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.ContentModelUtils.isFolder(ContentModelUtils.java:65)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:839)
at 
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)

{http://xml.apache.org/axis/}hostname:iPjNew.local

java.net.SocketTimeoutException: Read timed out
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
at 
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at 
org.alfresco.webservice.repository.RepositoryServiceSoapBindingStub.queryChildren(RepositoryServiceSoapBindingStub.java:800)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.ContentModelUtils.isFolder(ContentModelUtils.java:65)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:839)
at 
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:150)
at java.net.SocketInputStream.read(SocketInputStream.java:121)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
at java.io.BufferedInputStream.read(BufferedInputStream.java:254

[jira] [Created] (CONNECTORS-718) Alfresco Connector must throw exceptions with handler methods

2013-06-14 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-718:
-

 Summary: Alfresco Connector must throw exceptions with handler 
methods
 Key: CONNECTORS-718
 URL: https://issues.apache.org/jira/browse/CONNECTORS-718
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-713) Alfresco connector needs to deal with IOExceptions better

2013-06-12 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-713:
--

Description: 
The Alfresco Connector deals with IOExceptions by just tossing a wrapping 
ManifoldCFException.  This is a problem for several reasons.  First, 
IOExceptions are usually transient, and should mostly be converted into 
ServiceInterruptions instead.  Second, IOExceptions *may* represent thread 
interrupts, in which case the software should instead throw new 
ManifoldCFException(msg, ManifoldCFException.INTERRUPTED).

A good model is to have a method called void handleIOException(IOException) 
throws ServiceInterruption, ManifoldCFException called from everywhere that 
IOExceptions are caught.  Usually they get implemented something like this, 
although you can also throw ServiceInterruptions with different characteristics 
dependent on the kind of IOException being caught:

{code}
  private static void handleIOException(IOException e)
throws ManifoldCFException, ServiceInterruption {
if (!(e instanceof java.net.SocketTimeoutException)  (e instanceof 
InterruptedIOException)) {
  throw new ManifoldCFException(Interrupted:  + e.getMessage(), e,
ManifoldCFException.INTERRUPTED);
}
long currentTime = System.currentTimeMillis();
throw new ServiceInterruption(IO exception: +e.getMessage(), e, 
currentTime + 30L,
  currentTime + 3 * 60 * 6L,-1,false);
  }
{code}

The exception returned is the following:
{code}
FATAL 2013-06-11 16:40:03,441 (Worker thread '12') - Error tossed: Unable to 
get content as inputStream.
org.alfresco.webservice.util.WebServiceException: Unable to get content as 
inputStream.
at 
org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:139)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.ContentReader.getBinary(ContentReader.java:73)
at 
org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:824)
at 
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at 
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
Caused by: java.io.IOException: Server returned HTTP response code: 500 for 
URL: 
http://localhost:9090/alfresco/download/direct/workspace/SpacesStore/1e4f7fe4-d58a-4d69-b26f-3349546af7ca/testdata2.txt?ticket=TICKET_33ac1ec81c5b0ca9d024f0489df115286d0ac030
at 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
at 
org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:135)
... 4 more
{code}

  was:
The Alfresco Connector deals with IOExceptions by just tossing a wrapping 
ManifoldCFException.  This is a problem for several reasons.  First, 
IOExceptions are usually transient, and should mostly be converted into 
ServiceInterruptions instead.  Second, IOExceptions *may* represent thread 
interrupts, in which case the software should instead throw new 
ManifoldCFException(msg, ManifoldCFException.INTERRUPTED).

A good model is to have a method called void handleIOException(IOException) 
throws ServiceInterruption, ManifoldCFException called from everywhere that 
IOExceptions are caught.  Usually they get implemented something like this, 
although you can also throw ServiceInterruptions with different characteristics 
dependent on the kind of IOException being caught:

{code}
  private static void handleIOException(IOException e)
throws ManifoldCFException, ServiceInterruption {
if (!(e instanceof java.net.SocketTimeoutException)  (e instanceof 
InterruptedIOException)) {
  throw new ManifoldCFException(Interrupted:  + e.getMessage(), e,
ManifoldCFException.INTERRUPTED);
}
long currentTime = System.currentTimeMillis();
throw new ServiceInterruption(IO exception: +e.getMessage(), e, 
currentTime + 30L,
  currentTime + 3 * 60 * 6L,-1,false);
  }
{code}



 Alfresco connector needs to deal with IOExceptions better
 -

 Key: CONNECTORS-713
 URL: https://issues.apache.org/jira/browse/CONNECTORS-713
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 The Alfresco Connector deals with IOExceptions by just tossing a wrapping 
 ManifoldCFException.  This is a problem for several reasons.  First, 
 IOExceptions are usually transient, and should mostly be converted into 
 ServiceInterruptions instead.  Second, IOExceptions *may* represent thread 
 interrupts, in which case the software should instead throw

[jira] [Comment Edited] (CONNECTORS-713) Alfresco connector needs to deal with IOExceptions better

2013-06-12 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681172#comment-13681172
 ] 

Piergiorgio Lucidi edited comment on CONNECTORS-713 at 6/12/13 12:41 PM:
-

It could exists another bug in the getContentProperties method, I think that 
there is a problem. 
It could make sense to have a similar stacktrace if something goes wrong there.

  was (Author: piergiorgioluc...@gmail.com):
It could be bug in the getContentProperties method, I think that there is a 
problem. 
It could make sense to have a similar stacktrace if something goes wrong there.
  
 Alfresco connector needs to deal with IOExceptions better
 -

 Key: CONNECTORS-713
 URL: https://issues.apache.org/jira/browse/CONNECTORS-713
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 The Alfresco Connector deals with IOExceptions by just tossing a wrapping 
 ManifoldCFException.  This is a problem for several reasons.  First, 
 IOExceptions are usually transient, and should mostly be converted into 
 ServiceInterruptions instead.  Second, IOExceptions *may* represent thread 
 interrupts, in which case the software should instead throw new 
 ManifoldCFException(msg, ManifoldCFException.INTERRUPTED).
 A good model is to have a method called void handleIOException(IOException) 
 throws ServiceInterruption, ManifoldCFException called from everywhere that 
 IOExceptions are caught.  Usually they get implemented something like this, 
 although you can also throw ServiceInterruptions with different 
 characteristics dependent on the kind of IOException being caught:
 {code}
   private static void handleIOException(IOException e)
 throws ManifoldCFException, ServiceInterruption {
 if (!(e instanceof java.net.SocketTimeoutException)  (e instanceof 
 InterruptedIOException)) {
   throw new ManifoldCFException(Interrupted:  + e.getMessage(), e,
 ManifoldCFException.INTERRUPTED);
 }
 long currentTime = System.currentTimeMillis();
 throw new ServiceInterruption(IO exception: +e.getMessage(), e, 
 currentTime + 30L,
   currentTime + 3 * 60 * 6L,-1,false);
   }
 {code}
 The exception returned is the following:
 {code}
 FATAL 2013-06-11 16:40:03,441 (Worker thread '12') - Error tossed: Unable to 
 get content as inputStream.
 org.alfresco.webservice.util.WebServiceException: Unable to get content as 
 inputStream.
 at 
 org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:139)
 at 
 org.apache.manifoldcf.crawler.connectors.alfresco.ContentReader.getBinary(ContentReader.java:73)
 at 
 org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:824)
 at 
 org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
 at 
 org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
 Caused by: java.io.IOException: Server returned HTTP response code: 500 for 
 URL: 
 http://localhost:9090/alfresco/download/direct/workspace/SpacesStore/1e4f7fe4-d58a-4d69-b26f-3349546af7ca/testdata2.txt?ticket=TICKET_33ac1ec81c5b0ca9d024f0489df115286d0ac030
 at 
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
 at 
 org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:135)
 ... 4 more
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-713) Alfresco connector needs to deal with IOExceptions better

2013-06-12 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681172#comment-13681172
 ] 

Piergiorgio Lucidi commented on CONNECTORS-713:
---

It could be bug in the getContentProperties method, I think that there is a 
problem. 
It could make sense to have a similar stacktrace if something goes wrong there.

 Alfresco connector needs to deal with IOExceptions better
 -

 Key: CONNECTORS-713
 URL: https://issues.apache.org/jira/browse/CONNECTORS-713
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 The Alfresco Connector deals with IOExceptions by just tossing a wrapping 
 ManifoldCFException.  This is a problem for several reasons.  First, 
 IOExceptions are usually transient, and should mostly be converted into 
 ServiceInterruptions instead.  Second, IOExceptions *may* represent thread 
 interrupts, in which case the software should instead throw new 
 ManifoldCFException(msg, ManifoldCFException.INTERRUPTED).
 A good model is to have a method called void handleIOException(IOException) 
 throws ServiceInterruption, ManifoldCFException called from everywhere that 
 IOExceptions are caught.  Usually they get implemented something like this, 
 although you can also throw ServiceInterruptions with different 
 characteristics dependent on the kind of IOException being caught:
 {code}
   private static void handleIOException(IOException e)
 throws ManifoldCFException, ServiceInterruption {
 if (!(e instanceof java.net.SocketTimeoutException)  (e instanceof 
 InterruptedIOException)) {
   throw new ManifoldCFException(Interrupted:  + e.getMessage(), e,
 ManifoldCFException.INTERRUPTED);
 }
 long currentTime = System.currentTimeMillis();
 throw new ServiceInterruption(IO exception: +e.getMessage(), e, 
 currentTime + 30L,
   currentTime + 3 * 60 * 6L,-1,false);
   }
 {code}
 The exception returned is the following:
 {code}
 FATAL 2013-06-11 16:40:03,441 (Worker thread '12') - Error tossed: Unable to 
 get content as inputStream.
 org.alfresco.webservice.util.WebServiceException: Unable to get content as 
 inputStream.
 at 
 org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:139)
 at 
 org.apache.manifoldcf.crawler.connectors.alfresco.ContentReader.getBinary(ContentReader.java:73)
 at 
 org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnector.processDocuments(AlfrescoRepositoryConnector.java:824)
 at 
 org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
 at 
 org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
 Caused by: java.io.IOException: Server returned HTTP response code: 500 for 
 URL: 
 http://localhost:9090/alfresco/download/direct/workspace/SpacesStore/1e4f7fe4-d58a-4d69-b26f-3349546af7ca/testdata2.txt?ticket=TICKET_33ac1ec81c5b0ca9d024f0489df115286d0ac030
 at 
 sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1625)
 at 
 org.alfresco.webservice.util.ContentUtils.getContentAsInputStream(ContentUtils.java:135)
 ... 4 more
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-711) Wrong date parsing of the Alfresco Connector

2013-06-11 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-711:
-

 Summary: Wrong date parsing of the Alfresco Connector
 Key: CONNECTORS-711
 URL: https://issues.apache.org/jira/browse/CONNECTORS-711
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


Trying to get date properties returns the following exception:
{code}
WARN 2013-06-11 06:10:24,092 (Worker thread '4') - Alfresco: Error during the r
eading process of dates: Unparseable date: 2013-06-11T06:10:10.323-04:00
java.text.ParseException: Unparseable date: 2013-06-11T06:10:10.323-04:00
at java.text.DateFormat.parse(DateFormat.java:357)
at org.apache.manifoldcf.crawler.connectors.alfresco.PropertiesUtils.get
DatePropertyValue(PropertiesUtils.java:197)
at org.apache.manifoldcf.crawler.connectors.alfresco.PropertiesUtils.ing
estProperties(PropertiesUtils.java:84)
at org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryC
onnector.processDocuments(AlfrescoRepositoryConnector.java:817)
at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.proc
essDocuments(BaseRepositoryConnector.java:423)
at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.ja
va:559)
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-712) ArrayIndexOutOfBoundsException in the Alfresco Connector during tests

2013-06-11 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-712:
-

 Summary: ArrayIndexOutOfBoundsException in the Alfresco Connector 
during tests
 Key: CONNECTORS-712
 URL: https://issues.apache.org/jira/browse/CONNECTORS-712
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


During the exception of the integration tests the Alfresco Connector causes a 
test failure because when a content doesn't have the encoding then it will try 
to get mimetype value in a wrong way.

This is done by the same string that contains a multi value property.
It seems that on Windows there are some contents without encoding informations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-712) ArrayIndexOutOfBoundsException in the Alfresco Connector during tests

2013-06-11 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-712.
---

Resolution: Fixed

r1491794.

 ArrayIndexOutOfBoundsException in the Alfresco Connector during tests
 -

 Key: CONNECTORS-712
 URL: https://issues.apache.org/jira/browse/CONNECTORS-712
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3

   Original Estimate: 1h
  Remaining Estimate: 1h

 During the exception of the integration tests the Alfresco Connector causes a 
 test failure because when a content doesn't have the encoding then it will 
 try to get mimetype value in a wrong way.
 This is done by the same string that contains a multi value property.
 It seems that on Windows there are some contents without encoding 
 informations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-635) Alfresco test sometimes fails; upgrade to Alfresco 4.0 recommended

2013-06-10 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-635.
---

Resolution: Fixed

r1491531.

 Alfresco test sometimes fails; upgrade to Alfresco 4.0 recommended
 --

 Key: CONNECTORS-635
 URL: https://issues.apache.org/jira/browse/CONNECTORS-635
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 Here's the trace from the failure:
 {code}
 java.lang.UnsupportedOperationException: Entity deletion by key is not 
 supported
 at 
 org.alfresco.repo.cache.lookup.EntityLookupCache$EntityLookupCallback
 DAOAdaptor.deleteByKey(EntityLookupCache.java:202)
 at 
 org.alfresco.repo.cache.lookup.EntityLookupCache.deleteByKey(EntityLo
 okupCache.java:639)
 at 
 org.alfresco.repo.domain.node.AbstractNodeDAOImpl.addNodeAspects(Abst
 ractNodeDAOImpl.java:1987)
 at 
 org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProperties(D
 bNodeServiceImpl.java:526)
 at 
 org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProperties(D
 bNodeServiceImpl.java:439)
 at 
 org.alfresco.repo.node.db.DbNodeServiceImpl.addAspect(DbNodeServiceIm
 pl.java:736)
 at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
 on(AopUtils.java:307)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
 inpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:150)
 at 
 org.alfresco.repo.tenant.MultiTNodeServiceInterceptor.invoke(MultiTNo
 deServiceInterceptor.java:104)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
 cAopProxy.java:202)
 at $Proxy10.addAspect(Unknown Source)
 at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.alfresco.repo.service.StoreRedirectorProxyFactory$RedirectorInvoc
 ationHandler.invoke(StoreRedirectorProxyFactory.java:215)
 at $Proxy11.addAspect(Unknown Source)
 at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
 on(AopUtils.java:307)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
 inpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:150)
 at 
 org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropertyInterce
 ptor.java:303)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropertyInterce
 ptor.java:303)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invoke(NodeRe
 fPropertyMethodInterceptor.java:135)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invoke(NodeRe
 fPropertyMethodInterceptor.java:135)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
 cAopProxy.java:202)
 at $Proxy10.addAspect(Unknown Source)
 at 
 org.alfresco.repo.configuration.ConfigurableServiceImpl.makeConfigura
 ble(ConfigurableServiceImpl.java:51)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
 java:39

[jira] [Commented] (CONNECTORS-635) Alfresco test sometimes fails; upgrade to Alfresco 4.0 recommended

2013-06-10 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13679648#comment-13679648
 ] 

Piergiorgio Lucidi commented on CONNECTORS-635:
---

Yes, this commit requires Java 7 for executing the integration test for the 
Alfresco Connector.

 Alfresco test sometimes fails; upgrade to Alfresco 4.0 recommended
 --

 Key: CONNECTORS-635
 URL: https://issues.apache.org/jira/browse/CONNECTORS-635
 Project: ManifoldCF
  Issue Type: Bug
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 Here's the trace from the failure:
 {code}
 java.lang.UnsupportedOperationException: Entity deletion by key is not 
 supported
 at 
 org.alfresco.repo.cache.lookup.EntityLookupCache$EntityLookupCallback
 DAOAdaptor.deleteByKey(EntityLookupCache.java:202)
 at 
 org.alfresco.repo.cache.lookup.EntityLookupCache.deleteByKey(EntityLo
 okupCache.java:639)
 at 
 org.alfresco.repo.domain.node.AbstractNodeDAOImpl.addNodeAspects(Abst
 ractNodeDAOImpl.java:1987)
 at 
 org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProperties(D
 bNodeServiceImpl.java:526)
 at 
 org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProperties(D
 bNodeServiceImpl.java:439)
 at 
 org.alfresco.repo.node.db.DbNodeServiceImpl.addAspect(DbNodeServiceIm
 pl.java:736)
 at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
 on(AopUtils.java:307)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
 inpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:150)
 at 
 org.alfresco.repo.tenant.MultiTNodeServiceInterceptor.invoke(MultiTNo
 deServiceInterceptor.java:104)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
 cAopProxy.java:202)
 at $Proxy10.addAspect(Unknown Source)
 at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.alfresco.repo.service.StoreRedirectorProxyFactory$RedirectorInvoc
 ationHandler.invoke(StoreRedirectorProxyFactory.java:215)
 at $Proxy11.addAspect(Unknown Source)
 at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
 sorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflecti
 on(AopUtils.java:307)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJo
 inpoint(ReflectiveMethodInvocation.java:183)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:150)
 at 
 org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropertyInterce
 ptor.java:303)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropertyInterce
 ptor.java:303)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invoke(NodeRe
 fPropertyMethodInterceptor.java:135)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invoke(NodeRe
 fPropertyMethodInterceptor.java:135)
 at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(
 ReflectiveMethodInvocation.java:172)
 at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynami
 cAopProxy.java:202)
 at $Proxy10.addAspect(Unknown Source)
 at 
 org.alfresco.repo.configuration.ConfigurableServiceImpl.makeConfigura
 ble(ConfigurableServiceImpl.java:51)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method

[jira] [Resolved] (CONNECTORS-705) Upgrade to OpenCMIS 0.9.0

2013-06-10 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-705.
---

Resolution: Fixed

Upgraded OpenCMIS for the CMIS Connector and ElasticSearch Connector 
(integration tests).

r1491547.

 Upgrade to OpenCMIS 0.9.0
 -

 Key: CONNECTORS-705
 URL: https://issues.apache.org/jira/browse/CONNECTORS-705
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 We have to keep the latest version of CMIS, for more information please see 
 the following release notes:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310936version=12323957

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-705) Upgrade to OpenCMIS 0.9.0

2013-06-06 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-705:
--

Fix Version/s: ManifoldCF 1.3
 Assignee: Piergiorgio Lucidi
  Description: 
We have to keep the latest version of CMIS, for more information please see the 
following release notes:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310936version=12323957

   Issue Type: Improvement  (was: Bug)
Affects Version/s: ManifoldCF 1.2

 Upgrade to OpenCMIS 0.9.0
 -

 Key: CONNECTORS-705
 URL: https://issues.apache.org/jira/browse/CONNECTORS-705
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.2
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.3


 We have to keep the latest version of CMIS, for more information please see 
 the following release notes:
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310936version=12323957

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-553) [GSoC] Create an Email connector for Apache ManifoldCF

2013-05-03 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13648383#comment-13648383
 ] 

Piergiorgio Lucidi commented on CONNECTORS-553:
---

Done! I would like to say that implement the connector means also to implement 
the test suite (unit + integration test).
We could use Apache James for implementing integration tests for this connector.

 [GSoC] Create an Email connector for Apache ManifoldCF
 --

 Key: CONNECTORS-553
 URL: https://issues.apache.org/jira/browse/CONNECTORS-553
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Email connector
Affects Versions: ManifoldCF 1.3
Reporter: Erlend Garåsen
Assignee: Piergiorgio Lucidi
  Labels: gsoc, gsoc2013, mentor
 Fix For: ManifoldCF 1.3


 Apache ManifoldCF is an effort to provide an open source framework for 
 connecting source content repositories like Microsoft Sharepoint and EMC 
 Documentum, to target repositories or indexes, such as Apache Solr, Open 
 Search Server, or ElasticSearch. Apache ManifoldCF also defines a security 
 model for target repositories that permits them to enforce source-repository 
 security policies.
 ManifoldCF is based on a framework structure that allows developers to 
 implement new connectors for repositories, search servers and authorities 
 servers [1].
 Proposal:
 Implement an email connector that should support both IMAP and POP3 servers 
 as well as SSL/TLS encryption and server certificates.
 Skills needed:
 - Java programming
 - IMAP and POP protocols
 - XML
 [1] - http://manifoldcf.apache.org/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-553) Create an Email connector

2013-04-16 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13633097#comment-13633097
 ] 

Piergiorgio Lucidi commented on CONNECTORS-553:
---

Hi Buddhima,

nice to meet you, I'm trying to finish my registration as a mentor and then I 
will contact you :)

 Create an Email connector
 -

 Key: CONNECTORS-553
 URL: https://issues.apache.org/jira/browse/CONNECTORS-553
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Email connector
Affects Versions: ManifoldCF 1.3
Reporter: Erlend Garåsen
Assignee: Piergiorgio Lucidi
  Labels: gsoc2013
 Fix For: ManifoldCF 1.3


 Such a connector should support both IMAP and POP3 servers as well as SSL/TLS 
 encryption and server certificates.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Looking for a PMC member to volunteer to be a GSOC mentor

2013-04-12 Thread Piergiorgio Lucidi

Hi Karl,

I think that I can follow this student for this task :)

Please let me know what is needed to register me as a mentor, only if for
all of you is ok.

Thanks.

PJ
 Il giorno 12/apr/2013 15:58, Karl Wright daddy...@gmail.com ha scritto:

 Hi fellow PMC members,

 We have a student who is interested in a GSOC project (CONNECTORS-553).
 However, we have no registered GSOC mentors at this time.  We will need
 one, according to Mike McCandless:

 

 Yes, you need a PMC member to mentor (registered with Google, registered
 with Apache) the GSoC student, and you need an appropriate bite-sized
 project in ManifoldCF.



 If you don't have a mentor then the student can't do the project ...

 but the student can go find another Apache project that has GSoC
 mentors/projects.



 And all of this must happen before the deadline ... not sure exactly when
 that is but probably only a few weeks from now.



 Mike McCandless
 

 I'm hoping we have someone willing to volunteer?

 Karl

Re: Proposal for an official Twitter account of Apache ManifoldCF

2013-03-29 Thread Piergiorgio Lucidi

Do we need to propose a vote for this?
Or can I create the account?

Anyway for the new Twitter account we need an email address for the
registration, probably we need to create a new email account (GMail?)
dedicated to manage social accounts of ManifoldCF, or not?

PJ


2013/3/28 Karl Wright daddy...@gmail.com

 Ok - I'm happy to contribute occasional tweets based on whatever I'm
 doing that I think is exciting.

 Karl

 On Thu, Mar 28, 2013 at 6:29 AM, Piergiorgio Lucidi
 piergior...@apache.org wrote:
  I mean to spread all the activities around Apache ManifoldCF development:
 
  - each release version that we will release
  - important commits
  - the current issues on which we are working on
 
  But also spread news and events on which ManifoldCF is involved.
 
  In this way we can get more interest in the project, we have to share
 what
  we are doing, not every day (it could be nice :) ), but I think at least
  every week.
 
 
 
  2013/3/28 Karl Wright daddy...@gmail.com
 
  I think it is a fine idea!  I'm also glad if you want to manage it.
  I'm not sure what helping in this matter would mean.  What did you
  have in mind as far as responsibilities are concerned?
 
  Karl
 
  On Thu, Mar 28, 2013 at 4:44 AM, Piergiorgio Lucidi
  piergior...@apache.org wrote:
   Hi guys,
  
   I think that it could be very useful for us and all the community to
  create
   an official Twitter account dedicated to Apache ManifoldCF.
  
   I see that some of the Apache projects have this and tweets about the
   development and releases can help us to spread the project.
  
   What do you think about this?
  
   I offer myself as a volunteer to manage it but if someone else would
 like
   to help me he will be welcome :)
  
   Please let me know.
  
   Thank you.
   PJ
  
   --
   Piergiorgio Lucidi
   http://www.open4dev.com
 
  --
  Piergiorgio Lucidi
  http://www.open4dev.com
 




-- 
Piergiorgio Lucidi
http://www.open4dev.com

Re: Proposal for an official Twitter account of Apache ManifoldCF

2013-03-29 Thread Piergiorgio Lucidi

I have found GroupTweet [1] that is a free service to manage an unique
Twitter account with multiple users.

The contributors of the account can have or not a Twitter account, they
only need to register on GroupTweet.
The limit of the free version of the service is a maximum of three
contributors, but I think that could be enough for us :)

Please let me know what you think.
Thanks.

PJ

[1] - http://www.grouptweet.com/



2013/3/29 Piergiorgio Lucidi piergior...@apache.org

 Do we need to propose a vote for this?
 Or can I create the account?

 Anyway for the new Twitter account we need an email address for the
 registration, probably we need to create a new email account (GMail?)
 dedicated to manage social accounts of ManifoldCF, or not?

 PJ


 2013/3/28 Karl Wright daddy...@gmail.com

 Ok - I'm happy to contribute occasional tweets based on whatever I'm
 doing that I think is exciting.

 Karl

 On Thu, Mar 28, 2013 at 6:29 AM, Piergiorgio Lucidi
 piergior...@apache.org wrote:
  I mean to spread all the activities around Apache ManifoldCF
 development:
 
  - each release version that we will release
  - important commits
  - the current issues on which we are working on
 
  But also spread news and events on which ManifoldCF is involved.
 
  In this way we can get more interest in the project, we have to share
 what
  we are doing, not every day (it could be nice :) ), but I think at least
  every week.
 
 
 
  2013/3/28 Karl Wright daddy...@gmail.com
 
  I think it is a fine idea!  I'm also glad if you want to manage it.
  I'm not sure what helping in this matter would mean.  What did you
  have in mind as far as responsibilities are concerned?
 
  Karl
 
  On Thu, Mar 28, 2013 at 4:44 AM, Piergiorgio Lucidi
  piergior...@apache.org wrote:
   Hi guys,
  
   I think that it could be very useful for us and all the community to
  create
   an official Twitter account dedicated to Apache ManifoldCF.
  
   I see that some of the Apache projects have this and tweets about the
   development and releases can help us to spread the project.
  
   What do you think about this?
  
   I offer myself as a volunteer to manage it but if someone else would
 like
   to help me he will be welcome :)
  
   Please let me know.
  
   Thank you.
   PJ
  
   --
   Piergiorgio Lucidi
   http://www.open4dev.com
 
  --
  Piergiorgio Lucidi
  http://www.open4dev.com
 




 --
 Piergiorgio Lucidi
 http://www.open4dev.com




-- 
Piergiorgio Lucidi
http://www.open4dev.com

Re: Proposal for an official Twitter account of Apache ManifoldCF

2013-03-29 Thread Piergiorgio Lucidi

Ok, now we have an official Twitter account [1]

Hope this helps :)

Now I'm going to configure the GroupTweet and I'll try to add an account
for Karl.

[1] - https://twitter.com/ApacheManifold




2013/3/29 Karl Wright daddy...@gmail.com

 Hmm.  I don't think we need a vote unless we're expending monies; and
 we are not proposing to do that.

 For twitter registration, we can either create a dedicated account per
 person just for ManifoldCF twitter, or use their Apache email account.
  Using the apache account seems actually more likely to be the best
 solution.  What do you think?

 Karl

 On Fri, Mar 29, 2013 at 6:49 AM, Piergiorgio Lucidi
 piergior...@apache.org wrote:
  Do we need to propose a vote for this?
  Or can I create the account?
 
  Anyway for the new Twitter account we need an email address for the
  registration, probably we need to create a new email account (GMail?)
  dedicated to manage social accounts of ManifoldCF, or not?
 
  PJ
 
 
  2013/3/28 Karl Wright daddy...@gmail.com
 
  Ok - I'm happy to contribute occasional tweets based on whatever I'm
  doing that I think is exciting.
 
  Karl
 
  On Thu, Mar 28, 2013 at 6:29 AM, Piergiorgio Lucidi
  piergior...@apache.org wrote:
   I mean to spread all the activities around Apache ManifoldCF
 development:
  
   - each release version that we will release
   - important commits
   - the current issues on which we are working on
  
   But also spread news and events on which ManifoldCF is involved.
  
   In this way we can get more interest in the project, we have to share
  what
   we are doing, not every day (it could be nice :) ), but I think at
 least
   every week.
  
  
  
   2013/3/28 Karl Wright daddy...@gmail.com
  
   I think it is a fine idea!  I'm also glad if you want to manage it.
   I'm not sure what helping in this matter would mean.  What did you
   have in mind as far as responsibilities are concerned?
  
   Karl
  
   On Thu, Mar 28, 2013 at 4:44 AM, Piergiorgio Lucidi
   piergior...@apache.org wrote:
Hi guys,
   
I think that it could be very useful for us and all the community
 to
   create
an official Twitter account dedicated to Apache ManifoldCF.
   
I see that some of the Apache projects have this and tweets about
 the
development and releases can help us to spread the project.
   
What do you think about this?
   
I offer myself as a volunteer to manage it but if someone else
 would
  like
to help me he will be welcome :)
   
Please let me know.
   
Thank you.
PJ
   
--
Piergiorgio Lucidi
http://www.open4dev.com
  
   --
   Piergiorgio Lucidi
   http://www.open4dev.com
  
 
 
 
 
  --
  Piergiorgio Lucidi
  http://www.open4dev.com




-- 
Piergiorgio Lucidi
http://www.open4dev.com

Proposal for an official Twitter account of Apache ManifoldCF

2013-03-28 Thread Piergiorgio Lucidi

Hi guys,

I think that it could be very useful for us and all the community to create
an official Twitter account dedicated to Apache ManifoldCF.

I see that some of the Apache projects have this and tweets about the
development and releases can help us to spread the project.

What do you think about this?

I offer myself as a volunteer to manage it but if someone else would like
to help me he will be welcome :)

Please let me know.

Thank you.
PJ

-- 
Piergiorgio Lucidi
http://www.open4dev.com

Re: Proposal for an official Twitter account of Apache ManifoldCF

2013-03-28 Thread Piergiorgio Lucidi

I mean to spread all the activities around Apache ManifoldCF development:

- each release version that we will release
- important commits
- the current issues on which we are working on

But also spread news and events on which ManifoldCF is involved.

In this way we can get more interest in the project, we have to share what
we are doing, not every day (it could be nice :) ), but I think at least
every week.



2013/3/28 Karl Wright daddy...@gmail.com

 I think it is a fine idea!  I'm also glad if you want to manage it.
 I'm not sure what helping in this matter would mean.  What did you
 have in mind as far as responsibilities are concerned?

 Karl

 On Thu, Mar 28, 2013 at 4:44 AM, Piergiorgio Lucidi
 piergior...@apache.org wrote:
  Hi guys,
 
  I think that it could be very useful for us and all the community to
 create
  an official Twitter account dedicated to Apache ManifoldCF.
 
  I see that some of the Apache projects have this and tweets about the
  development and releases can help us to spread the project.
 
  What do you think about this?
 
  I offer myself as a volunteer to manage it but if someone else would like
  to help me he will be welcome :)
 
  Please let me know.
 
  Thank you.
  PJ
 
  --
  Piergiorgio Lucidi
  http://www.open4dev.com

 --
 Piergiorgio Lucidi
 http://www.open4dev.com

[jira] [Updated] (CONNECTORS-594) SolrCloud Output Connector

2013-03-27 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-594:
--

Component/s: Lucene/SOLR connector

 SolrCloud Output Connector
 --

 Key: CONNECTORS-594
 URL: https://issues.apache.org/jira/browse/CONNECTORS-594
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Lucene/SOLR connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Minoru Osuka
Assignee: Karl Wright
Priority: Minor
 Fix For: ManifoldCF 1.1

 Attachments: CONNECTORS-594.properties.patch, 
 solrcloud-output-connector.tar.gz


 The Output Connectors doesn't support SolrCloud currently.
 Since the Solr 4.0 released, I think there is a need for support for 
 SolrCloud.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-665) Update documentation for SolrCloud support

2013-03-27 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-665:
-

 Summary: Update documentation for SolrCloud support
 Key: CONNECTORS-665
 URL: https://issues.apache.org/jira/browse/CONNECTORS-665
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Documentation, Lucene/SOLR connector
Affects Versions: ManifoldCF 1.1.1
Reporter: Piergiorgio Lucidi


I think that we have to update the documentation for the Solr Output Connector, 
there is no information about the support of SolrCloud, ZooKeeper and the 
latest improvements.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (CONNECTORS-666) Ant Build broken

2013-03-27 Thread Piergiorgio Lucidi (JIRA)

Piergiorgio Lucidi created CONNECTORS-666:
-

 Summary: Ant Build broken
 Key: CONNECTORS-666
 URL: https://issues.apache.org/jira/browse/CONNECTORS-666
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Build
Affects Versions: ManifoldCF 1.1.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi


Trying to execute the command ant make-core-deps returns the following 
exception:

{code}
/Users/matteogrolla/Development/alf_sourcesense/manifold/apache-manifoldcf-1.1.1/build.xml:3501:
 Can't get 
http://svn.alfresco.com/repos/alfresco-open-mirror/alfresco/HEAD/root/projects/3rd-party/lib/xmlsec-1.4.1.jar
 to 
/Users/matteogrolla/Development/alf_sourcesense/manifold/apache-manifoldcf-1.1.1/lib/xmlsec.jar
{code}

There are three dependencies that are using the same path, trying to get deps 
from the svn.alfresco.com, we have to update that path using the official Maven 
Alfresco Repository

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-655) Add mimetype and/or filename support to Alfresco connector

2013-03-04 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-655.
---

Resolution: Fixed

r1452476.

 Add mimetype and/or filename support to Alfresco connector
 --

 Key: CONNECTORS-655
 URL: https://issues.apache.org/jira/browse/CONNECTORS-655
 Project: ManifoldCF
  Issue Type: Improvement
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.2


 Add mimetype and/or filename support to Alfresco connector.  The appropriate 
 methods are:
 RepositoryDocument.setFileName(...)
 and
 RepositoryDocument.setMimeType(...)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (CONNECTORS-656) Add mimetype and/or filename support to CMIS connector

2013-03-04 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi resolved CONNECTORS-656.
---

Resolution: Fixed

r1452485.

 Add mimetype and/or filename support to CMIS connector
 --

 Key: CONNECTORS-656
 URL: https://issues.apache.org/jira/browse/CONNECTORS-656
 Project: ManifoldCF
  Issue Type: Improvement
  Components: CMIS connector
Affects Versions: ManifoldCF 1.1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.2


 Add mimetype and/or filename support to CMIS connector.  The appropriate 
 methods are:
 RepositoryDocument.setFileName(...)
 and
 RepositoryDocument.setMimeType(...)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (CONNECTORS-602) Add a new Alfresco WebScript API Repository Connector

2013-02-13 Thread Piergiorgio Lucidi (JIRA)


 [ 
https://issues.apache.org/jira/browse/CONNECTORS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Piergiorgio Lucidi updated CONNECTORS-602:
--

Issue Type: New Feature  (was: Task)
   Summary: Add a new Alfresco WebScript API Repository Connector  (was: 
Remove the SOAP API from the Alfresco Connector)

 Add a new Alfresco WebScript API Repository Connector
 -

 Key: CONNECTORS-602
 URL: https://issues.apache.org/jira/browse/CONNECTORS-602
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.2

   Original Estimate: 120h
  Remaining Estimate: 120h

 Taking a look at the Alfresco roadmap, it seems that during the next 18 
 months the CML SOAP API will not be supported anymore:
 [http://wiki.alfresco.com/wiki/Product_Roadmap#End-of-life_3]
 The history of this connector is not happy, during the first step I asked to 
 some Alfresco guys about the life of the SOAP API and I was assured that it 
 would not be finished.
 Anyway this is not the best API exposed by Alfresco, for many reasons 
 developers should use the REST API as their first choice. 
 The SOAP API was the only one API that allows to invoke Lucene queries 
 without implementing new customizations/extensions on Alfresco.
 Now we have an official confirmation that the life of this SOAP API ends 
 during the end of this year and the begin of the next one.
 My idea is to do a brainstorming with some Alfresco guys to understand 
 together which APIs we should use to reimplement the connector.
 I would like to use the current HTTP services without installing nothing on 
 the Alfresco side. But I have to check with them if this solution is feasible.
 I hope to have good news soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (CONNECTORS-602) Add a new Alfresco WebScript API Repository Connector

2013-02-13 Thread Piergiorgio Lucidi (JIRA)


[ 
https://issues.apache.org/jira/browse/CONNECTORS-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13577443#comment-13577443
 ] 

Piergiorgio Lucidi commented on CONNECTORS-602:
---

After a first chat with Maurizio Pillitu (Alfresco) we decided to work together 
in an external module on github for implementing this new connector. 

Then I will migrate all the source code in a ManifoldCF branch for also adding 
integration tests.

The github module is available at the following address:
https://github.com/maoo/alfresco-webscript-manifold-connector


 Add a new Alfresco WebScript API Repository Connector
 -

 Key: CONNECTORS-602
 URL: https://issues.apache.org/jira/browse/CONNECTORS-602
 Project: ManifoldCF
  Issue Type: New Feature
  Components: Alfresco connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
 Fix For: ManifoldCF 1.2

   Original Estimate: 120h
  Remaining Estimate: 120h

 Taking a look at the Alfresco roadmap, it seems that during the next 18 
 months the CML SOAP API will not be supported anymore:
 [http://wiki.alfresco.com/wiki/Product_Roadmap#End-of-life_3]
 The history of this connector is not happy, during the first step I asked to 
 some Alfresco guys about the life of the SOAP API and I was assured that it 
 would not be finished.
 Anyway this is not the best API exposed by Alfresco, for many reasons 
 developers should use the REST API as their first choice. 
 The SOAP API was the only one API that allows to invoke Lucene queries 
 without implementing new customizations/extensions on Alfresco.
 Now we have an official confirmation that the life of this SOAP API ends 
 during the end of this year and the begin of the next one.
 My idea is to do a brainstorming with some Alfresco guys to understand 
 together which APIs we should use to reimplement the connector.
 I would like to use the current HTTP services without installing nothing on 
 the Alfresco side. But I have to check with them if this solution is feasible.
 I hope to have good news soon.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Need one more vote for each of the four new plugin releases

Hi Karl,

during the afternoon I can take a look at these plugins ;)
I'll let you know later.

Piergiorgio


2013/2/5 Karl Wright daddy...@gmail.com

 Hi Committers,

 If you haven't already, please take a moment to examine the four open
 votes, one for each of our ManifoldCF plugins.  We just need one more
 vote each to wrap them up.  All that is really still needed is:

 - check signatures
 - make sure the README's, NOTICE's, and LICENSE's seem sensible

 There have been essentially no functional changes over previous
 releases - just packaging (with the sole exception of the Solr 4.x
 plugin, where exception handling had to change slightly).

 Thanks in advance for your help!

 Karl

 --
 Piergiorgio Lucidi
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF SharePoint 2007 Plugin 0.4, RC0

Checked package contents.

+1 from me.


2013/1/31 Karl Wright daddy...@gmail.com

 Please vote on whether to release Apache ManifoldCF SharePoint 2007
 Plugin 0.4, RC0.  The release artifact can be found at:


 http://people.apache.org/~kwright/apache-manifoldcf-sharepoint-2007-plugin-0.4

 There is an svn tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2007/tags/release-0.4-RC0

 This release has no functional changes, other than documentation
 fixes, copyright date updates, and repackaging.  See CONNECTORS-534.

 Karl

 --
 Piergiorgio Lucidi
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF SharePoint 2010 Plugin 0.2, RC1

Checked package contents.

+1 from me.


2013/2/1 Karl Wright daddy...@gmail.com

 Please vote on whether to release Apache ManifoldCF SharePoint 2010
 Plugin 0.2, RC1.  The release artifact can be found at:


 http://people.apache.org/~kwright/apache-manifoldcf-sharepoint-2010-plugin-0.2

 There is an svn tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2010/tags/release-0.2-RC1

 This release has no functional changes, other than documentation
 fixes, copyright date updates, and repackaging.  See CONNECTORS-534.

 Karl

 --
 Piergiorgio Lucidi
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF Solr 3.x Plugin 0.4, RC0

Checked package contents.

+1 from me.


2013/1/31 Karl Wright daddy...@gmail.com

 Please vote on whether to release Apache ManifoldCF Solr 3.x Plugin
 0.4, RC0.  The release artifact can be found at:

 http://people.apache.org/~kwright/apache-manifoldcf-solr-3.x-plugin-0.4

 There is an svn tag at:


 https://svn.apache.org/repos/asf/manifoldcf/integration/solr-3.x/tags/release-0.4-RC0

 This release has no functional changes, other than documentation
 fixes, copyright date updates, and repackaging.  See CONNECTORS-534.

 Karl

 --
 Piergiorgio Lucidi
 http://www.open4dev.com

Re: [VOTE] Release Apache ManifoldCF Solr 4.x Plugin 0.4, RC0