[jira] [Updated] (CONNECTORS-471) HSQLDB runs out of memory during load test
[ https://issues.apache.org/jira/browse/CONNECTORS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-471: --- Affects Version/s: ManifoldCF 0.5 HSQLDB runs out of memory during load test -- Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- 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] [Reopened] (CONNECTORS-471) HSQLDB runs out of memory during load test
[ https://issues.apache.org/jira/browse/CONNECTORS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reopened CONNECTORS-471: HSQLDB runs out of memory during load test -- Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- 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] [Reopened] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reopened CONNECTORS-467: Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- 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] [Updated] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-467: --- Priority: Critical (was: Major) Affects Version/s: ManifoldCF 0.6 Fix Version/s: ManifoldCF 0.5.1 Assignee: Karl Wright (was: Erlend Garåsen) Triaging this for the 0.5.1 release. Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- 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-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273862#comment-13273862 ] Karl Wright commented on CONNECTORS-467: r1337451 on release branch. Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- 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] [Resolved] (CONNECTORS-467) Remove outdated taglib directives in web.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-467. Resolution: Fixed Remove outdated taglib directives in web.xml Key: CONNECTORS-467 URL: https://issues.apache.org/jira/browse/CONNECTORS-467 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Erlend Garåsen Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Attachments: CONNECTORS-467.patch Resin does not accept the web.xml file which belongs to the web-crawler-ui application and returns 500 Server error after deployment. Resin complains about an unexpected taglib-tag. The taglib directive is not longer needed in JSP 2.0 which we're now using. Some information about how we can configure MCF properly for JSP 2.0: http://wiki.metawerx.net/wiki/RemovingTaglibFromWeb.xml It's probably possible to place the taglib directives inside a jsp-config directive as a quick fix as well. -- 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-471) HSQLDB runs out of memory during load test
[ https://issues.apache.org/jira/browse/CONNECTORS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273864#comment-13273864 ] Karl Wright commented on CONNECTORS-471: r1337452 on release branch HSQLDB runs out of memory during load test -- Key: CONNECTORS-471 URL: https://issues.apache.org/jira/browse/CONNECTORS-471 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 For ManifoldCF 0.4-incubating, the standard HSQLDB load test could complete with 384M. It now runs out of memory even with 1.5G, which is the maximum my machine has. -- 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] [Updated] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-453: --- Priority: Critical (was: Major) Fix Version/s: ManifoldCF 0.5.1 ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- 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] [Reopened] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright reopened CONNECTORS-453: Reopening for inclusion in 0.5.1 ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- 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-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13273872#comment-13273872 ] Karl Wright commented on CONNECTORS-453: r1337457 (release branch) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- 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] [Resolved] (CONNECTORS-453) ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs
[ https://issues.apache.org/jira/browse/CONNECTORS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-453. Resolution: Fixed ManifoldCF running with Derby 10.8.1.1 has problems pausing and aborting jobs - Key: CONNECTORS-453 URL: https://issues.apache.org/jira/browse/CONNECTORS-453 Project: ManifoldCF Issue Type: Bug Components: Framework core Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Priority: Critical Fix For: ManifoldCF 0.5.1, ManifoldCF 0.6 Since upgrading to Derby 10.8.x.x, tt takes minutes to crawl just 20 documents. Clearly the Derby contention/locking bugs are back with a vengeance in 10.8.x.x. Either we use 10.7.x.x or we get the Derby team to look at them again. In the interim, maybe it is time to use hsqldb as the default embedded database for the single-process example instead of Derby. -- 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
Re: Should we release an 0.5.1?
It looks like this is probably happening, so I've pulled up three tickets into the 0.5 release branch: CONNECTORS-453 CONNECTORS-467 CONNECTORS-471 I suppose we could even spin a release candidate now, even though we shouldn't probably vote on it until we've officially graduated. The release candidate should be 0.5.1, not 0.5.1-incubating. Abe-san, did you want to be release manager for this? Karl On Mon, May 7, 2012 at 7:00 AM, Erlend Garåsen e.f.gara...@usit.uio.no wrote: If we succeed in graduating in May, then +1 from me. This problem does not only affects Tomcat, but also Resin, and probably other web containers as well. Erlend On 04.05.12 21.03, Karl Wright wrote: My view: It will be relatively easy to do this once we graduate, and too much of a pain before then. If we succeed in graduating in May, I'd give a +1. If not, then maybe we should just try to release the 0.6 version instead. Karl On Fri, May 4, 2012 at 1:01 PM, Piergiorgio Lucidi piergior...@apache.org wrote: I think that it is important to release a 0.5.1 version to enable compatibility for Tomcat 7.x. +1 for me for releasing a 0.5.1 version Piergiorgio 2012/5/1 Karl Wrightdaddy...@gmail.com We've had a number of people using Tomcat 7.x who have tripped over CONNECTORS-467. Does the community want to release a 0.5.1 version to fix this one issue? Or, alternatively, try to push 0.6 out the door early? Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Should we release an 0.5.1?
Yes I did. I will be able to work as release manager next week. Please create 0.5.1 branch. Regards, Shinichiro Abe On 2012/05/12, at 16:14, Karl Wright wrote: It looks like this is probably happening, so I've pulled up three tickets into the 0.5 release branch: CONNECTORS-453 CONNECTORS-467 CONNECTORS-471 I suppose we could even spin a release candidate now, even though we shouldn't probably vote on it until we've officially graduated. The release candidate should be 0.5.1, not 0.5.1-incubating. Abe-san, did you want to be release manager for this? Karl On Mon, May 7, 2012 at 7:00 AM, Erlend Garåsen e.f.gara...@usit.uio.no wrote: If we succeed in graduating in May, then +1 from me. This problem does not only affects Tomcat, but also Resin, and probably other web containers as well. Erlend On 04.05.12 21.03, Karl Wright wrote: My view: It will be relatively easy to do this once we graduate, and too much of a pain before then. If we succeed in graduating in May, I'd give a +1. If not, then maybe we should just try to release the 0.6 version instead. Karl On Fri, May 4, 2012 at 1:01 PM, Piergiorgio Lucidi piergior...@apache.org wrote: I think that it is important to release a 0.5.1 version to enable compatibility for Tomcat 7.x. +1 for me for releasing a 0.5.1 version Piergiorgio 2012/5/1 Karl Wrightdaddy...@gmail.com We've had a number of people using Tomcat 7.x who have tripped over CONNECTORS-467. Does the community want to release a 0.5.1 version to fix this one issue? Or, alternatively, try to push 0.6 out the door early? Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Should we release an 0.5.1?
Hi Abe-san, For point releases, the usual standard is to use the same branch as the main release. So we would continue to use the 0.5-incubating branch, and just make a new release from it, and of course new tags. Thanks, Karl On Sat, May 12, 2012 at 5:35 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: Yes I did. I will be able to work as release manager next week. Please create 0.5.1 branch. Regards, Shinichiro Abe On 2012/05/12, at 16:14, Karl Wright wrote: It looks like this is probably happening, so I've pulled up three tickets into the 0.5 release branch: CONNECTORS-453 CONNECTORS-467 CONNECTORS-471 I suppose we could even spin a release candidate now, even though we shouldn't probably vote on it until we've officially graduated. The release candidate should be 0.5.1, not 0.5.1-incubating. Abe-san, did you want to be release manager for this? Karl On Mon, May 7, 2012 at 7:00 AM, Erlend Garåsen e.f.gara...@usit.uio.no wrote: If we succeed in graduating in May, then +1 from me. This problem does not only affects Tomcat, but also Resin, and probably other web containers as well. Erlend On 04.05.12 21.03, Karl Wright wrote: My view: It will be relatively easy to do this once we graduate, and too much of a pain before then. If we succeed in graduating in May, I'd give a +1. If not, then maybe we should just try to release the 0.6 version instead. Karl On Fri, May 4, 2012 at 1:01 PM, Piergiorgio Lucidi piergior...@apache.org wrote: I think that it is important to release a 0.5.1 version to enable compatibility for Tomcat 7.x. +1 for me for releasing a 0.5.1 version Piergiorgio 2012/5/1 Karl Wrightdaddy...@gmail.com We've had a number of people using Tomcat 7.x who have tripped over CONNECTORS-467. Does the community want to release a 0.5.1 version to fix this one issue? Or, alternatively, try to push 0.6 out the door early? Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Should we release an 0.5.1?
Okay. Do we need to change release-version into 0.5.1 at build.xml in the branch? Shinichiro Abe On 2012/05/12, at 19:39, Karl Wright wrote: Hi Abe-san, For point releases, the usual standard is to use the same branch as the main release. So we would continue to use the 0.5-incubating branch, and just make a new release from it, and of course new tags. Thanks, Karl On Sat, May 12, 2012 at 5:35 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: Yes I did. I will be able to work as release manager next week. Please create 0.5.1 branch. Regards, Shinichiro Abe On 2012/05/12, at 16:14, Karl Wright wrote: It looks like this is probably happening, so I've pulled up three tickets into the 0.5 release branch: CONNECTORS-453 CONNECTORS-467 CONNECTORS-471 I suppose we could even spin a release candidate now, even though we shouldn't probably vote on it until we've officially graduated. The release candidate should be 0.5.1, not 0.5.1-incubating. Abe-san, did you want to be release manager for this? Karl On Mon, May 7, 2012 at 7:00 AM, Erlend Garåsen e.f.gara...@usit.uio.no wrote: If we succeed in graduating in May, then +1 from me. This problem does not only affects Tomcat, but also Resin, and probably other web containers as well. Erlend On 04.05.12 21.03, Karl Wright wrote: My view: It will be relatively easy to do this once we graduate, and too much of a pain before then. If we succeed in graduating in May, I'd give a +1. If not, then maybe we should just try to release the 0.6 version instead. Karl On Fri, May 4, 2012 at 1:01 PM, Piergiorgio Lucidi piergior...@apache.org wrote: I think that it is important to release a 0.5.1 version to enable compatibility for Tomcat 7.x. +1 for me for releasing a 0.5.1 version Piergiorgio 2012/5/1 Karl Wrightdaddy...@gmail.com We've had a number of people using Tomcat 7.x who have tripped over CONNECTORS-467. Does the community want to release a 0.5.1 version to fix this one issue? Or, alternatively, try to push 0.6 out the door early? Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
Re: Should we release an 0.5.1?
Yes we do. Would you be willing to do that? Thanks! Karl On Sat, May 12, 2012 at 7:03 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: Okay. Do we need to change release-version into 0.5.1 at build.xml in the branch? Shinichiro Abe On 2012/05/12, at 19:39, Karl Wright wrote: Hi Abe-san, For point releases, the usual standard is to use the same branch as the main release. So we would continue to use the 0.5-incubating branch, and just make a new release from it, and of course new tags. Thanks, Karl On Sat, May 12, 2012 at 5:35 AM, Shinichiro Abe shinichiro.ab...@gmail.com wrote: Yes I did. I will be able to work as release manager next week. Please create 0.5.1 branch. Regards, Shinichiro Abe On 2012/05/12, at 16:14, Karl Wright wrote: It looks like this is probably happening, so I've pulled up three tickets into the 0.5 release branch: CONNECTORS-453 CONNECTORS-467 CONNECTORS-471 I suppose we could even spin a release candidate now, even though we shouldn't probably vote on it until we've officially graduated. The release candidate should be 0.5.1, not 0.5.1-incubating. Abe-san, did you want to be release manager for this? Karl On Mon, May 7, 2012 at 7:00 AM, Erlend Garåsen e.f.gara...@usit.uio.no wrote: If we succeed in graduating in May, then +1 from me. This problem does not only affects Tomcat, but also Resin, and probably other web containers as well. Erlend On 04.05.12 21.03, Karl Wright wrote: My view: It will be relatively easy to do this once we graduate, and too much of a pain before then. If we succeed in graduating in May, I'd give a +1. If not, then maybe we should just try to release the 0.6 version instead. Karl On Fri, May 4, 2012 at 1:01 PM, Piergiorgio Lucidi piergior...@apache.org wrote: I think that it is important to release a 0.5.1 version to enable compatibility for Tomcat 7.x. +1 for me for releasing a 0.5.1 version Piergiorgio 2012/5/1 Karl Wrightdaddy...@gmail.com We've had a number of people using Tomcat 7.x who have tripped over CONNECTORS-467. Does the community want to release a 0.5.1 version to fix this one issue? Or, alternatively, try to push 0.6 out the door early? Karl -- Piergiorgio Lucidi http://www.open4dev.com -- Erlend Garåsen Center for Information Technology Services University of Oslo P.O. Box 1086 Blindern, N-0317 OSLO, Norway Ph: (+47) 22840193, Fax: (+47) 22852970, Mobile: (+47) 91380968, VIP: 31050
[jira] [Commented] (CONNECTORS-470) SharePoint 2010 support
[
https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274208#comment-13274208
]
Karl Wright commented on CONNECTORS-470:
Further analysis indicates that some of these services still work, while others
(e.g. the DspSts service) have problems. Specifically, this query request:
{code}
dsQuery select=/list[@id='{D7E22603-5B7D-415D-B12A-4543957E8430}']/
{code}
yields:
{code}
HTTP/1.1 500 Internal Server Error
{code}
... plus some stuff that the user didn't actually include from the transaction
which might have been helpful.
SharePoint 2010 support
---
Key: CONNECTORS-470
URL: https://issues.apache.org/jira/browse/CONNECTORS-470
Project: ManifoldCF
Issue Type: Improvement
Components: SharePoint connector
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
See here for list of the SharePoint web services for SharePoint 2010:
http://msdn.microsoft.com/en-us/library/ee705814.aspx
--
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] [Issue Comment Edited] (CONNECTORS-470) SharePoint 2010 support
[
https://issues.apache.org/jira/browse/CONNECTORS-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13274208#comment-13274208
]
Karl Wright edited comment on CONNECTORS-470 at 5/13/12 4:52 AM:
-
Further analysis indicates that some of these services still work, while others
(e.g. the DspSts service) have problems. Specifically, this query request:
{code}
dsQuery select=/list[@id='{D7E22603-5B7D-415D-B12A-4543957E8430}']/
{code}
yields:
{code}
HTTP/1.1 500 Internal Server Error
{code}
... plus some stuff that the user didn't actually include from the transaction
which might have been helpful.
From this I conclude that the DspSts service on this installation is broken -
and ONLY that service is broken. This is because the GUID that is included is
indeed valid and must have come from somewhere - the Lists service, no doubt,
which still seems to actually work on SharePoint 2010.
was (Author: kwri...@metacarta.com):
Further analysis indicates that some of these services still work, while
others (e.g. the DspSts service) have problems. Specifically, this query
request:
{code}
dsQuery select=/list[@id='{D7E22603-5B7D-415D-B12A-4543957E8430}']/
{code}
yields:
{code}
HTTP/1.1 500 Internal Server Error
{code}
... plus some stuff that the user didn't actually include from the transaction
which might have been helpful.
SharePoint 2010 support
---
Key: CONNECTORS-470
URL: https://issues.apache.org/jira/browse/CONNECTORS-470
Project: ManifoldCF
Issue Type: Improvement
Components: SharePoint connector
Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6
Reporter: Karl Wright
Assignee: Karl Wright
Fix For: ManifoldCF 0.6
See here for list of the SharePoint web services for SharePoint 2010:
http://msdn.microsoft.com/en-us/library/ee705814.aspx
--
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
