[jira] [Resolved] (CONNECTORS-712) ArrayIndexOutOfBoundsException in the Alfresco Connector during tests
[ 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
[
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)
at
[jira] [Commented] (CONNECTORS-635) Alfresco test sometimes fails; upgrade to Alfresco 4.0 recommended
[
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)
at
[jira] [Resolved] (CONNECTORS-705) Upgrade to OpenCMIS 0.9.0
[ 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
[ 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
[ 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
[ 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
[jira] [Updated] (CONNECTORS-594) SolrCloud Output Connector
[ 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
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
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
[ 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
[ 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
[ 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
[ 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
[jira] [Commented] (CONNECTORS-635) Alfresco test fails
[
https://issues.apache.org/jira/browse/CONNECTORS-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13568589#comment-13568589
]
Piergiorgio Lucidi commented on CONNECTORS-635:
---
It seems that I can't replicate this issue.
Discovering the Alfresco JIRA I found that this is a bug that affects Alfresco
3.4 and it is fixed in Alfresco 4.0:
https://issues.alfresco.com/jira/browse/ALF-5229
So this means that I have to upgrade Alfresco in the project to the latest
version.
Probably I should create another ticket dedicated to the upgrade of the
Alfresco version, because many things are changed now.
Alfresco test fails
---
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.2
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
[jira] [Created] (CONNECTORS-628) Maven integration tests broken
Piergiorgio Lucidi created CONNECTORS-628:
-
Summary: Maven integration tests broken
Key: CONNECTORS-628
URL: https://issues.apache.org/jira/browse/CONNECTORS-628
Project: ManifoldCF
Issue Type: Bug
Components: Build, Tests
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.2
Trying to execute integration tests using Maven it returns the following
exception:
{code}
Running org.apache.manifoldcf.filesystem_tests.APISanityCombinedHSQLDBIT
Configuration file successfully read
45 [main] INFO org.eclipse.jetty.server.Server - jetty-7.5.4.v20111024
90 [main] WARN org.eclipse.jetty.webapp.WebInfConfiguration - Web application
not found ../../framework/build/war-proprietary/mcf-combined-service.war
91 [main] WARN org.eclipse.jetty.webapp.WebAppContext - Failed startup of
context
o.e.j.w.WebAppContext{/mcf,null},../../framework/build/war-proprietary/mcf-combined-service.war
java.io.FileNotFoundException:
../../framework/build/war-proprietary/mcf-combined-service.war
at
org.eclipse.jetty.webapp.WebInfConfiguration.unpack(WebInfConfiguration.java:479)
at
org.eclipse.jetty.webapp.WebInfConfiguration.preConfigure(WebInfConfiguration.java:52)
at
org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:417)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:453)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:224)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:167)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:89)
at org.eclipse.jetty.server.Server.doStart(Server.java:261)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at
org.apache.manifoldcf.crawler.tests.ManifoldCFInstance.start(ManifoldCFInstance.java:519)
at
org.apache.manifoldcf.crawler.tests.BaseITHSQLDB.setUp(BaseITHSQLDB.java:214)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
at
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
at
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27)
at
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
at
org.junit.runners.BlockJUnit4ClassRunner.runNotIgnored(BlockJUnit4ClassRunner.java:79)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:71)
at
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:49)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:236)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:134)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:113)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:103)
at
[jira] [Created] (CONNECTORS-622) CMIS Connector return NPE trying to get an empty boolean or date value
Piergiorgio Lucidi created CONNECTORS-622:
-
Summary: CMIS Connector return NPE trying to get an empty boolean
or date value
Key: CONNECTORS-622
URL: https://issues.apache.org/jira/browse/CONNECTORS-622
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Trying to work on some CMIS repositories, it seems that getting a boolean or a
date value from a content can return a null value.
I found this exception related to boolean values:
{code}
FATAL 2013-01-25 09:10:40,475 (Worker thread '32') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1120)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{code}
And another one related to date values:
{code}
FATAL 2013-01-25 09:10:49,744 (Worker thread '27') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1157)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{code}
After getting these errors the crawling remains looping, the unique way is to
stop the job manually, because there are some active threads.
So we need to add some check instructions to avoid NPE.
--
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-622) CMIS Connector returns NPE trying to get an empty boolean or date value
[
https://issues.apache.org/jira/browse/CONNECTORS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi updated CONNECTORS-622:
--
Fix Version/s: ManifoldCF 1.1
Summary: CMIS Connector returns NPE trying to get an empty boolean or
date value (was: CMIS Connector return NPE trying to get an empty boolean or
date value)
CMIS Connector returns NPE trying to get an empty boolean or date value
---
Key: CONNECTORS-622
URL: https://issues.apache.org/jira/browse/CONNECTORS-622
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.1
Original Estimate: 24h
Remaining Estimate: 24h
Trying to work on some CMIS repositories, it seems that getting a boolean or
a date value from a content can return a null value.
I found this exception related to boolean values:
{code}
FATAL 2013-01-25 09:10:40,475 (Worker thread '32') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1120)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{code}
And another one related to date values:
{code}
FATAL 2013-01-25 09:10:49,744 (Worker thread '27') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1157)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{code}
After getting these errors the crawling remains looping, the unique way is to
stop the job manually, because there are some active threads.
So we need to add some check instructions to avoid NPE.
--
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-622) CMIS Connector returns NPE trying to get an empty boolean or date value
[
https://issues.apache.org/jira/browse/CONNECTORS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-622.
---
Resolution: Fixed
r1438458.
CMIS Connector returns NPE trying to get an empty boolean or date value
---
Key: CONNECTORS-622
URL: https://issues.apache.org/jira/browse/CONNECTORS-622
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 1.0.1
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.1
Original Estimate: 24h
Remaining Estimate: 24h
Trying to work on some CMIS repositories, it seems that getting a boolean or
a date value from a content can return a null value.
I found this exception related to boolean values:
{code}
FATAL 2013-01-25 09:10:40,475 (Worker thread '32') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1120)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{code}
And another one related to date values:
{code}
FATAL 2013-01-25 09:10:49,744 (Worker thread '27') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1157)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{code}
After getting these errors the crawling remains looping, the unique way is to
stop the job manually, because there are some active threads.
So we need to add some check instructions to avoid NPE.
--
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-602) Remove the SOAP API from the Alfresco Connector
Piergiorgio Lucidi created CONNECTORS-602: - Summary: Remove the SOAP API from the Alfresco Connector Key: CONNECTORS-602 URL: https://issues.apache.org/jira/browse/CONNECTORS-602 Project: ManifoldCF Issue Type: Task Components: Alfresco connector Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi 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-555) Alfresco maven build is broken
[
https://issues.apache.org/jira/browse/CONNECTORS-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13475995#comment-13475995
]
Piergiorgio Lucidi commented on CONNECTORS-555:
---
Have you tried to remove that dependency from your local Maven repository and
re-run the install goal?
Alfresco maven build is broken
--
Key: CONNECTORS-555
URL: https://issues.apache.org/jira/browse/CONNECTORS-555
Project: ManifoldCF
Issue Type: Bug
Components: Build
Affects Versions: ManifoldCF 1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.1
The maven build steps:
{code}
mvn-bootstrap
mvn clean -DskipTests install
{code}
fail in the following way:
{code}
[ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
reso
lve dependencies for project
org.apache.manifoldcf:mcf-alfresco-connector:jar:1.
1-SNAPSHOT: Could not find artifact javax.activation:activation:jar:1.0.2 in
alf
resco-release
(https://artifacts.alfresco.com/nexus/content/repositories/release
s) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :mcf-alfresco-connector
C:\wip\mcf\trunk
{code}
It looks like there is a missing dependency we may need. I think
activation.jar was there before, not sure what happened to it.
--
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-555) Alfresco maven build is broken
[
https://issues.apache.org/jira/browse/CONNECTORS-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13476317#comment-13476317
]
Piergiorgio Lucidi commented on CONNECTORS-555:
---
I reproduced this issue removing all the dependencies of javax.activation from
my local repository and removing any specific settings in the settings.xml of
Maven.
But I noticed that, during the execution of the command mvn clean install, the
CMIS Connector uses the same version of activation (1.0.2) and it was
successfully downloaded from the standard Maven repo:
{code}
Downloaded:
http://repo.maven.apache.org/maven2/javax/activation/activation/1.0.2/activation-1.0.2.pom
(776 B at 1.5 KB/sec)
{code}
It sounds strange...
Alfresco maven build is broken
--
Key: CONNECTORS-555
URL: https://issues.apache.org/jira/browse/CONNECTORS-555
Project: ManifoldCF
Issue Type: Bug
Components: Build
Affects Versions: ManifoldCF 1.0, ManifoldCF 1.0.1, ManifoldCF 1.1
Reporter: Karl Wright
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0.1
The maven build steps:
{code}
mvn-bootstrap
mvn clean -DskipTests install
{code}
fail in the following way:
{code}
[ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
reso
lve dependencies for project
org.apache.manifoldcf:mcf-alfresco-connector:jar:1.
1-SNAPSHOT: Could not find artifact javax.activation:activation:jar:1.0.2 in
alf
resco-release
(https://artifacts.alfresco.com/nexus/content/repositories/release
s) - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
rea
d the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyReso
lutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn goals -rf :mcf-alfresco-connector
C:\wip\mcf\trunk
{code}
It looks like there is a missing dependency we may need. I think
activation.jar was there before, not sure what happened to it.
--
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-549) Wrong credentials not correctly managed by CMIS Connector
Piergiorgio Lucidi created CONNECTORS-549:
-
Summary: Wrong credentials not correctly managed by CMIS Connector
Key: CONNECTORS-549
URL: https://issues.apache.org/jira/browse/CONNECTORS-549
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0
If you try to register a CMIS Connection with wrong credentials the
CmisPermissionDeniedException is not managed, the UI remain without any output
and it returns the following exception in the log file:
{code}
84334 [qtp1595252236-192] WARN org.eclipse.jetty.servlet.ServletHandler -
/mcf-crawler-ui/execute.jsp
org.apache.jasper.JasperException: An exception occurred processing JSP page
/viewconnection.jsp at line 108
105:{
106:try
107:{
108:connectionStatus = c.check();
109:}
110:finally
111:{
Stacktrace:
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:521)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:430)
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:288)
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:115)
at
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:709)
at
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:680)
at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:392)
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.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
at org.eclipse.jetty.server.Server.handle(Server.java:349)
at
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
at
org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224)
at
[jira] [Resolved] (CONNECTORS-549) Wrong credentials not correctly managed by CMIS Connector
[
https://issues.apache.org/jira/browse/CONNECTORS-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-549.
---
Resolution: Fixed
r1392006.
Wrong credentials not correctly managed by CMIS Connector
-
Key: CONNECTORS-549
URL: https://issues.apache.org/jira/browse/CONNECTORS-549
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0
If you try to register a CMIS Connection with wrong credentials the
CmisPermissionDeniedException is not managed, the UI remain without any
output and it returns the following exception in the log file:
{code}
84334 [qtp1595252236-192] WARN org.eclipse.jetty.servlet.ServletHandler -
/mcf-crawler-ui/execute.jsp
org.apache.jasper.JasperException: An exception occurred processing JSP page
/viewconnection.jsp at line 108
105: {
106: try
107: {
108: connectionStatus = c.check();
109: }
110: finally
111: {
Stacktrace:
at
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:521)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:430)
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:288)
at org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:115)
at
org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:709)
at
org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:680)
at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:392)
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.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
at org.eclipse.jetty.server.Server.handle(Server.java:349)
at
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
at
[jira] [Created] (CONNECTORS-538) Maven build broken on SharePoint Connector
Piergiorgio Lucidi created CONNECTORS-538:
-
Summary: Maven build broken on SharePoint Connector
Key: CONNECTORS-538
URL: https://issues.apache.org/jira/browse/CONNECTORS-538
Project: ManifoldCF
Issue Type: Bug
Components: Build, SharePoint connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Trying to execute the maven build, it returns the following exception:
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 23.103s
[INFO] Finished at: Mon Sep 24 15:53:10 CEST 2012
[INFO] Final Memory: 9M/486M
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java (default) on project
mcf-sharepoint-connector: Execution default of goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java failed: A required class
was missing while executing
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java:
org/apache/axis/wsdl/WSDL2Java
[ERROR] -
[ERROR] realm =pluginorg.codehaus.mojo:axistools-maven-plugin:1.4
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/mojo/axistools-maven-plugin/1.4/axistools-maven-plugin-1.4.jar
[ERROR] urls[1] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-compiler-api/1.5.3/plexus-compiler-api-1.5.3.jar
[ERROR] urls[2] =
file:/Users/piergiorgiolucidi/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[3] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
[ERROR] urls[4] =
file:/Users/piergiorgiolucidi/.m2/repository/axis/axis/1.4/axis-1.4.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -:
org.apache.axis.wsdl.WSDL2Java
{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-538) Maven build broken on SharePoint Connector
[
https://issues.apache.org/jira/browse/CONNECTORS-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-538.
---
Resolution: Fixed
r1389389.
Maven build broken on SharePoint Connector
--
Key: CONNECTORS-538
URL: https://issues.apache.org/jira/browse/CONNECTORS-538
Project: ManifoldCF
Issue Type: Bug
Components: Build, SharePoint connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 1.0
Original Estimate: 1h
Remaining Estimate: 1h
Trying to execute the maven build, it returns the following exception:
{code}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 23.103s
[INFO] Finished at: Mon Sep 24 15:53:10 CEST 2012
[INFO] Final Memory: 9M/486M
[INFO]
[ERROR] Failed to execute goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java (default) on project
mcf-sharepoint-connector: Execution default of goal
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java failed: A required
class was missing while executing
org.codehaus.mojo:axistools-maven-plugin:1.4:wsdl2java:
org/apache/axis/wsdl/WSDL2Java
[ERROR] -
[ERROR] realm =pluginorg.codehaus.mojo:axistools-maven-plugin:1.4
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/mojo/axistools-maven-plugin/1.4/axistools-maven-plugin-1.4.jar
[ERROR] urls[1] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-compiler-api/1.5.3/plexus-compiler-api-1.5.3.jar
[ERROR] urls[2] =
file:/Users/piergiorgiolucidi/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[3] =
file:/Users/piergiorgiolucidi/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.6/plexus-utils-1.5.6.jar
[ERROR] urls[4] =
file:/Users/piergiorgiolucidi/.m2/repository/axis/axis/1.4/axis-1.4.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[maven.api, parent: null]]
[ERROR]
[ERROR] -:
org.apache.axis.wsdl.WSDL2Java
{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-527) Error during CMIS ingestion of nodes without binary content
Piergiorgio Lucidi created CONNECTORS-527:
-
Summary: Error during CMIS ingestion of nodes without binary
content
Key: CONNECTORS-527
URL: https://issues.apache.org/jira/browse/CONNECTORS-527
Project: ManifoldCF
Issue Type: Bug
Components: CMIS connector
Affects Versions: ManifoldCF 0.6
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Fix For: ManifoldCF 0.7
In case of some nodes in the CMIS repository don't have binary stream, the
connector returns:
{code}
FATAL 2012-09-13 10:05:14,961 (Worker thread '1') - Error tossed: null
java.lang.NullPointerException
at
org.apache.manifoldcf.crawler.connectors.cmis.CmisRepositoryConnector.processDocuments(CmisRepositoryConnector.java:1070)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:551)
{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-525) Upgrade to OpenCMIS 0.7.0
[ https://issues.apache.org/jira/browse/CONNECTORS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-525. --- Resolution: Fixed r1384250. I have updated the scripts for building the lib folder. But now we need to release a new lib package ready to download, because now with this new version of OpenCMIS we have to remove these dependencies: jsr181-api-1.0-MR1 and jsr250-api-1.0. Upgrade to OpenCMIS 0.7.0 - Key: CONNECTORS-525 URL: https://issues.apache.org/jira/browse/CONNECTORS-525 Project: ManifoldCF Issue Type: Improvement Components: CMIS connector Affects Versions: ManifoldCF 0.6 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.7 Original Estimate: 2h Remaining Estimate: 2h We should upgrade CMIS Connector with the latest version of the OpenCMIS library. -- 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] [Comment Edited] (CONNECTORS-519) maven build of mcf-test-materials/mcf-alfresco-war-test fails
[
https://issues.apache.org/jira/browse/CONNECTORS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13450698#comment-13450698
]
Piergiorgio Lucidi edited comment on CONNECTORS-519 at 9/8/12 2:13 AM:
---
Fixed also the URL of the Alfresco Maven repository in the Ant script: now it
is invoked in HTTPS (r1382060).
was (Author: piergiorgioluc...@gmail.com):
Fixed also the URL in the Ant script: now it is invoked in HTTPS (r1382060).
maven build of mcf-test-materials/mcf-alfresco-war-test fails
-
Key: CONNECTORS-519
URL: https://issues.apache.org/jira/browse/CONNECTORS-519
Project: ManifoldCF
Issue Type: Bug
Components: Alfresco connector, Build
Environment: Mac OS X Version 10.7.4
java version 1.6.0_33
Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.4, arch: x86_64, family: mac
Reporter: Ahmet Arslan
Assignee: Piergiorgio Lucidi
Labels: alfresco-war-test, test-materials,
Fix For: ManifoldCF 0.7
Attachments: CONNECTORS-519.patch
When I try mvn clean install on trunk, I get the following error:
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] ManifoldCF SUCCESS [2.736s]
[INFO] ManifoldCF - Framework SUCCESS [0.074s]
[INFO] ManifoldCF - Framework - Core . SUCCESS [7.149s]
[INFO] ManifoldCF - Framework - UI Core .. SUCCESS [2.686s]
[INFO] ManifoldCF - Framework - Agents ... SUCCESS [18.703s]
[INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [21.628s]
[INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.355s]
[INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.411s]
[INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.314s]
[INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.042s]
[INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [2.889s]
[INFO] ManifoldCF - Framework - Script Engine SUCCESS [3.546s]
[INFO] ManifoldCF - Connectors ... SUCCESS [0.032s]
[INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.479s]
[INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [16.125s]
[INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.766s]
[INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [2.368s]
[INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.855s]
[INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.345s]
[INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.245s]
[INFO] ManifoldCF - Connectors - RSS . SUCCESS [3.012s]
[INFO] ManifoldCF - Connectors - SharePoint .. SUCCESS [12.172s]
[INFO] ManifoldCF - Connectors - Solr SUCCESS [1.864s]
[INFO] ManifoldCF - Connectors - Web . SUCCESS [3.292s]
[INFO] ManifoldCF - Connectors - CMIS SUCCESS [17.579s]
[INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [1.511s]
[INFO] ManifoldCF - Connectors - Wiki SUCCESS [16.313s]
[INFO] ManifoldCF - Connectors - Alfresco SUCCESS [16.978s]
[INFO] ManifoldCF - Connectors - ElasticSearch ... SUCCESS [2.101s]
[INFO] ManifoldCF - Test materials ... SUCCESS [0.020s]
[INFO] ManifoldCF - Test Materials - Alfresco WAR FAILURE [4.305s]
[INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
[INFO] ManifoldCF - Tests SKIPPED
[INFO] ManifoldCF - Test - ElasticSearch . SKIPPED
[INFO] ManifoldCF - Test - Alfresco .. SKIPPED
[INFO] ManifoldCF - Test - Wiki .. SKIPPED
[INFO] ManifoldCF - Test - CMIS .. SKIPPED
[INFO] ManifoldCF - Test - Filesystem SKIPPED
[INFO] ManifoldCF - Test - Sharepoint SKIPPED
[INFO] ManifoldCF - Test - RSS ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[jira] [Resolved] (CONNECTORS-519) maven build of mcf-test-materials/mcf-alfresco-war-test fails
[
https://issues.apache.org/jira/browse/CONNECTORS-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piergiorgio Lucidi resolved CONNECTORS-519.
---
Resolution: Fixed
Resolved in r1381277.
maven build of mcf-test-materials/mcf-alfresco-war-test fails
-
Key: CONNECTORS-519
URL: https://issues.apache.org/jira/browse/CONNECTORS-519
Project: ManifoldCF
Issue Type: Bug
Components: Alfresco connector, Build
Environment: Mac OS X Version 10.7.4
java version 1.6.0_33
Java(TM) SE Runtime Environment (build 1.6.0_33-b03-424-11M3720)
Java HotSpot(TM) 64-Bit Server VM (build 20.8-b03-424, mixed mode)
Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
Maven home: /usr/share/maven
Java version: 1.6.0_33, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.4, arch: x86_64, family: mac
Reporter: Ahmet Arslan
Assignee: Piergiorgio Lucidi
Labels: alfresco-war-test, test-materials,
Fix For: ManifoldCF 0.7
Attachments: CONNECTORS-519.patch
When I try mvn clean install on trunk, I get the following error:
{noformat}
[INFO] Reactor Summary:
[INFO]
[INFO] ManifoldCF SUCCESS [2.736s]
[INFO] ManifoldCF - Framework SUCCESS [0.074s]
[INFO] ManifoldCF - Framework - Core . SUCCESS [7.149s]
[INFO] ManifoldCF - Framework - UI Core .. SUCCESS [2.686s]
[INFO] ManifoldCF - Framework - Agents ... SUCCESS [18.703s]
[INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [21.628s]
[INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.355s]
[INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.411s]
[INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.314s]
[INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.042s]
[INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [2.889s]
[INFO] ManifoldCF - Framework - Script Engine SUCCESS [3.546s]
[INFO] ManifoldCF - Connectors ... SUCCESS [0.032s]
[INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.479s]
[INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [16.125s]
[INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.766s]
[INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [2.368s]
[INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.855s]
[INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.345s]
[INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.245s]
[INFO] ManifoldCF - Connectors - RSS . SUCCESS [3.012s]
[INFO] ManifoldCF - Connectors - SharePoint .. SUCCESS [12.172s]
[INFO] ManifoldCF - Connectors - Solr SUCCESS [1.864s]
[INFO] ManifoldCF - Connectors - Web . SUCCESS [3.292s]
[INFO] ManifoldCF - Connectors - CMIS SUCCESS [17.579s]
[INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [1.511s]
[INFO] ManifoldCF - Connectors - Wiki SUCCESS [16.313s]
[INFO] ManifoldCF - Connectors - Alfresco SUCCESS [16.978s]
[INFO] ManifoldCF - Connectors - ElasticSearch ... SUCCESS [2.101s]
[INFO] ManifoldCF - Test materials ... SUCCESS [0.020s]
[INFO] ManifoldCF - Test Materials - Alfresco WAR FAILURE [4.305s]
[INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
[INFO] ManifoldCF - Tests SKIPPED
[INFO] ManifoldCF - Test - ElasticSearch . SKIPPED
[INFO] ManifoldCF - Test - Alfresco .. SKIPPED
[INFO] ManifoldCF - Test - Wiki .. SKIPPED
[INFO] ManifoldCF - Test - CMIS .. SKIPPED
[INFO] ManifoldCF - Test - Filesystem SKIPPED
[INFO] ManifoldCF - Test - Sharepoint SKIPPED
[INFO] ManifoldCF - Test - RSS ... SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 2:54.944s
[INFO] Finished at: Tue Sep 04 03:10:14 EEST 2012
[INFO] Final Memory: 24M/81M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:2.3:unpack-dependencies
(unpack-amps) on
[jira] [Updated] (CONNECTORS-525) Upgrade to OpenCMIS 0.7.0
[ https://issues.apache.org/jira/browse/CONNECTORS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi updated CONNECTORS-525: -- Fix Version/s: ManifoldCF 0.7 Upgrade to OpenCMIS 0.7.0 - Key: CONNECTORS-525 URL: https://issues.apache.org/jira/browse/CONNECTORS-525 Project: ManifoldCF Issue Type: Improvement Components: CMIS connector Affects Versions: ManifoldCF 0.6 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.7 Original Estimate: 2h Remaining Estimate: 2h We should upgrade CMIS Connector with the latest version of the OpenCMIS library. -- 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-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13447819#comment-13447819
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
Ok, my Mac is crashed and then I retried and the selected version is 4.0 (2010).
Now it returns a different exception, maybe a little step forward:
Service interruption reported for job 1346775681055 connection 'SharePoint
2010': Remote procedure exception: List
'{715A7457-3366-40C0-80F4-FC9BCAE8CEC8}' does not exist at site with URL
'http://win-0hb0c25kl3n/my/personal/administrator'.
It seems that there is an issue about the site url for the list or something
similar. The site URL for the list should be the following:
http://win-0hb0c25kl3n/my/personal/administrator/demosite
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
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
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{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-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13431660#comment-13431660
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
Ok I installed Apache Ant, Apache SVN and I have built the project directly
from Windows Server.
Then I copied the Microsoft.Sharepoint.dll in the right place in Windows.
Then I executed the setup.bat but it seems that I don't find the right URL to
get the WSDL, it returns always a code 404.
In the README is mentioned this URL:
http://your server name:server port/server
location/_vti_bin/MCPermissions.asmx
But now on my SharePoint instance I have this URLs:
Administration:
http://win-0hb0c25kl3n:33445/default.aspx
My personal documents on my site:
http://win-0hb0c25kl3n/my/personal/administrator/default.aspx
Have you got some ideas about what could be the right URL to get WSDL?
Any feedback is welcome :)
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
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
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
[jira] [Commented] (CONNECTORS-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13427315#comment-13427315
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
Finally I have finished a complete SharePoint installation in my virtual
machine based on Windows Server 2008 R2, SQL Server 2008 R2 and SharePoint 2010
SP1 :-P
The next steps are:
- configuring a personal site with some documents in the document library
- download, compile and run ManifoldCF on this environment
- execute tests against SharePoint
I'll let you know soon any updates on this.
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
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
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-492) SharePoint connector on SP2010 throws exception when there are too many documents in a library
[
https://issues.apache.org/jira/browse/CONNECTORS-492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418126#comment-13418126
]
Piergiorgio Lucidi commented on CONNECTORS-492:
---
I'm downloading Windows Server 2008 R2 and SharePoint 2010, and during the next
week I'll try to take a look at this issue.
In this way I can start to use my MSDN account :D
I'll let you know more soon...
SharePoint connector on SP2010 throws exception when there are too many
documents in a library
--
Key: CONNECTORS-492
URL: https://issues.apache.org/jira/browse/CONNECTORS-492
Project: ManifoldCF
Issue Type: Bug
Components: SharePoint connector
Affects Versions: ManifoldCF 0.7
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.7
When there are more than the document list limit set by the administrator, no
documents for the library are crawled. Instead the following exception is
thrown:
{code}
DEBUG 2012-07-16 23:58:04,036 (Worker thread '19') - Mapping Exception to
AxisFault
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Exception of type
'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
faultActor:
faultNode:
faultDetail:
{http://schemas.microsoft.com/sharepoint/soap/}errorstring:The
attempted operation is prohibited because it exceeds the list view threshold
enforced by the administrator.
{http://schemas.microsoft.com/sharepoint/soap/}errorcode:0x80070024
Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was
thrown.
at
org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at
org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at
org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
Source)
at
org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
Source)
at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
at
org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at
org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
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
com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListItems(ListsSoapStub.java:1841)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocuments(SPSProxyHelper.java:629)
at
org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:909)
at
org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
at
org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561)
DEBUG
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
