[jira] [Updated] (CONNECTORS-257) Input-able response lifetime for Active Directory authority
[ https://issues.apache.org/jira/browse/CONNECTORS-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-257: --- Attachment: CONNECTORS-257-3.patch Here is a patch that makes the LRU parameters non-static, now that you are setting them per instance. I hope this clarifies the issue for you. > Input-able response lifetime for Active Directory authority > --- > > Key: CONNECTORS-257 > URL: https://issues.apache.org/jira/browse/CONNECTORS-257 > Project: ManifoldCF > Issue Type: Improvement > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-257-1.patch, CONNECTORS-257-2.patch, > CONNECTORS-257-3.patch > > > The access tokens are cached for one minute, and up to 1000 different > users' access tokens will be cached at any one time. > The access token's cache per username remains idle before expiring. > Its expiration time depends response lifetime, and > expiration time is updated after looking up the cache. > Currently response lifetime is 1 minute. > Since I want not to access Active Directory frequently, > I make this response lifetime to be input-able for users. -- 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-268) Move SharePoint MCPermissions target extension code and build scripts to "integration" area
[ https://issues.apache.org/jira/browse/CONNECTORS-268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-268: --- Component/s: SharePoint 3.x MCPermissions extension > Move SharePoint MCPermissions target extension code and build scripts to > "integration" area > --- > > Key: CONNECTORS-268 > URL: https://issues.apache.org/jira/browse/CONNECTORS-268 > Project: ManifoldCF > Issue Type: Task > Components: SharePoint 3.x MCPermissions extension >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.4 > > > The new integration area seems like a logical place to move the SharePoint > 3.0 MCPermissions extension code, once we have all the necessary pieces to > allow us to prebuild it for users. This will also involve creating a > connectors/sharepoint/integration directory, as well as appropriate build.xml > changes. -- 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-260) Maven build should download jtds.jar automatically, and maybe the mysql jdbc driver jar too, as part of JDBC connector build
[ https://issues.apache.org/jira/browse/CONNECTORS-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-260: --- Assignee: Shinichiro Abe > Maven build should download jtds.jar automatically, and maybe the mysql jdbc > driver jar too, as part of JDBC connector build > > > Key: CONNECTORS-260 > URL: https://issues.apache.org/jira/browse/CONNECTORS-260 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Shinichiro Abe > Fix For: ManifoldCF 0.4 > > > The JDBC connector build under Maven should download all the supported JDBC > drivers that it can, including jtds.jar and maybe mysql's jdbc driver jar. -- 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-271) Need Wiki connector documentation
[ https://issues.apache.org/jira/browse/CONNECTORS-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-271: --- Component/s: (was: Wiki connector) Documentation > Need Wiki connector documentation > - > > Key: CONNECTORS-271 > URL: https://issues.apache.org/jira/browse/CONNECTORS-271 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.4 > > > We need end-user documentation for the wiki connector, as well as references > from all the other usual places. -- 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-262) Ant build could download WSDL's for SharePoint, if the public Microsoft SharePoint site has them
[ https://issues.apache.org/jira/browse/CONNECTORS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-262: --- Attachment: CONNECTORS-262.patch Attached a patch that seems to work. What do you think? > Ant build could download WSDL's for SharePoint, if the public Microsoft > SharePoint site has them > > > Key: CONNECTORS-262 > URL: https://issues.apache.org/jira/browse/CONNECTORS-262 > Project: ManifoldCF > Issue Type: Improvement > Components: Build, SharePoint connector >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Shinichiro Abe > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-262.patch > > > There is a public Microsoft SharePoint site. If we can get at it, we might > be able to download the Microsoft WSDL's we need from it automatically during > the "download-dependencies" target. -- 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-209) HSQLDB driver does not know how to deal with remote HSQLDB instances
[ https://issues.apache.org/jira/browse/CONNECTORS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-209: --- Affects Version/s: (was: ManifoldCF 0.3) ManifoldCF 0.4 Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.4 Assignee: Karl Wright Picking this up in 0.4 since the HSQLDB group wanted us to look at doing it this way. > HSQLDB driver does not know how to deal with remote HSQLDB instances > > > Key: CONNECTORS-209 > URL: https://issues.apache.org/jira/browse/CONNECTORS-209 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework core >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.4 > > > The HSQLDB driver only knows how to work with local instances of HSQLDB. > This could be readily changed. According to the HSQLDB team: > > Regarding deployment options, HSQLDB is not just for embedded use and > > can easily be run as a server. It would be nice if manifoldCF db access > > does not inadvertently prevent this. So long as the url is not edited by > > manifoldCF, the user can replace it with a client/server URL. > > > > URL for embedded jdbc:hsqldb:file:;hsqldb.shutdown=true URL > > for client server jdbc:hsqldb:hsql:/dbname URL for > > client server when server allows remote opening of databases > > jdbc:hsqldb:hsql:/dbname;file: -- 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-100) DB lock timeout, and/or indefinite or excessive database activity
[
https://issues.apache.org/jira/browse/CONNECTORS-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-100:
---
Affects Version/s: ManifoldCF 0.4
Fix Version/s: (was: ManifoldCF next)
ManifoldCF 0.4
Comments in the Derby ticket indicate that this is a known problem with query
optimization in Derby, and thus they regard it as an enhancement to fix it.
We're therefore going to need to try and rejigger the queries in question to
use "IN" clauses, which Derby knows how to use, and hopefully not break any of
the other databases. PostgreSQL has certainly improved in this regard since
7.4, and HSQLDB seems pretty robust about handling clause transformations, so
all that I really need is a good test case to be able to verify that I haven't
broken anything.
> DB lock timeout, and/or indefinite or excessive database activity
> -
>
> Key: CONNECTORS-100
> URL: https://issues.apache.org/jira/browse/CONNECTORS-100
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
>Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3,
> ManifoldCF 0.4
> Environment: Running unmodified dist/example from trunk/ using the
> default configuration.
>Reporter: Andrzej Bialecki
>Assignee: Karl Wright
> Fix For: ManifoldCF 0.4
>
>
> When a job is started and running (via crawler-ui) occasionally it's not
> possible to display a list of running jobs. The problem persists even after
> restarting ACF. The following exception is thrown in the console:
> {code}
> org.apache.acf.core.interfaces.ACFException: Database exception: Exception
> doing query: A lock could not be obtained within the time requested
> at
> org.apache.acf.core.database.Database.executeViaThread(Database.java:421)
> at
> org.apache.acf.core.database.Database.executeUncachedQuery(Database.java:465)
> at
> org.apache.acf.core.database.Database$QueryCacheExecutor.create(Database.java:1072)
> at
> org.apache.acf.core.cachemanager.CacheManager.findObjectsAndExecute(CacheManager.java:144)
> at
> org.apache.acf.core.database.Database.executeQuery(Database.java:167)
> at
> org.apache.acf.core.database.DBInterfaceDerby.performQuery(DBInterfaceDerby.java:727)
> at
> org.apache.acf.crawler.jobs.JobManager.makeJobStatus(JobManager.java:5611)
> at
> org.apache.acf.crawler.jobs.JobManager.getAllStatus(JobManager.java:5549)
> at
> org.apache.jsp.showjobstatus_jsp._jspService(showjobstatus_jsp.java:316)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
> at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at
> org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> at
> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390)
> at
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at
> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at
> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at
> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
> at
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at
> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
> at
> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542)
> at
> org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:923)
> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:547)
> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> at
> org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
> at
> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> Caused by: java.sql.SQLTransactionRollbackException: A lock could not be
> obtained within the time requested
> at
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
> a
[jira] [Updated] (CONNECTORS-277) WikiConnector - option to limit crawl by namespace
[ https://issues.apache.org/jira/browse/CONNECTORS-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-277: --- Affects Version/s: (was: ManifoldCF next) ManifoldCF 0.4 Fix Version/s: ManifoldCF 0.4 Assignee: Karl Wright > WikiConnector - option to limit crawl by namespace > -- > > Key: CONNECTORS-277 > URL: https://issues.apache.org/jira/browse/CONNECTORS-277 > Project: ManifoldCF > Issue Type: Improvement > Components: Wiki connector >Affects Versions: ManifoldCF 0.4 >Reporter: Tobias Wunderlich >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.4 > > > At the moment, the WikiConnector crawls the whole Wiki. This can take up a > lot of time. For testing purposes an option to limit the pages to crawl by > namespaces(title) would be great. > Tobias -- 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-291) Active Directory authority fails to recover from error gracefully
[ https://issues.apache.org/jira/browse/CONNECTORS-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-291: --- Attachment: CONNECTORS-291.patch May fix the problem > Active Directory authority fails to recover from error gracefully > - > > Key: CONNECTORS-291 > URL: https://issues.apache.org/jira/browse/CONNECTORS-291 > Project: ManifoldCF > Issue Type: Bug > Components: Active Directory authority >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-291.patch > > > When the active directory authority gets an error during ctx.reconnect(), it > seems to be put into a state where it doesn't recover until 5 minutes go by > (that is until the LdapContext is flushed). It really needs to drop the LDAP > context at that point and start fresh immediately. -- 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-292) Problems compiling agents, pull-agent, connectors/filesystem, etc directly in Maven
[
https://issues.apache.org/jira/browse/CONNECTORS-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-292:
---
Priority: Minor (was: Major)
Fix Version/s: ManifoldCF next
Summary: Problems compiling agents, pull-agent,
connectors/filesystem, etc directly in Maven (was: compiling mcf-agents
project with maven)
> Problems compiling agents, pull-agent, connectors/filesystem, etc directly in
> Maven
> ---
>
> Key: CONNECTORS-292
> URL: https://issues.apache.org/jira/browse/CONNECTORS-292
> Project: ManifoldCF
> Issue Type: Bug
> Components: Build
>Affects Versions: ManifoldCF 0.4
> Environment: java 6, maven 3.0.3, ManifoldCF trunk version from
> http://svn.apache.org/repos/asf/incubator/lcf/trunk
>Reporter: Luca Stancapiano
>Assignee: Karl Wright
>Priority: Minor
> Fix For: ManifoldCF next
>
>
> if I try to execute the command 'mvn install -Dmaven.test.skip inside
> 'framework/agents' I get this error:
> [ERROR] Failed to execute goal on project mcf-agents: Could not resolve
> dependencies for project org.apache.manifoldcf:mcf-agents:jar:0.4.0-SNAPSHOT:
> Failure to find org.apache.manifoldcf:mcf-core:jar:tests:0.4.0-SNAPSHOT in
> was cached in the local repository, resolution will not be
> reattempted until the update interval of sose-private has elapsed or updates
> are forced -> [Help 1]
> In the pom.xml of the mcf-agents project there is a wrong dependency:
>
> ${project.groupId}
> mcf-core
> ${project.version}
> test-jar
> test
>
--
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-298) Web connector: SSL trust error message highly misleading
[ https://issues.apache.org/jira/browse/CONNECTORS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-298: --- Priority: Minor (was: Major) Summary: Web connector: SSL trust error message highly misleading (was: Web connector: SSL does not use custom SSL socket factory in all cases) > Web connector: SSL trust error message highly misleading > > > Key: CONNECTORS-298 > URL: https://issues.apache.org/jira/browse/CONNECTORS-298 > Project: ManifoldCF > Issue Type: Bug > Components: Web connector >Affects Versions: ManifoldCF 0.3 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.4 > > > When crawling learningresources.nga.gov, the web connector gets a strange > exception from certificate verification logic in Sun's SSL implementation. > The stack trace indicates that the ManifoldCF secure socket factory may not > have been used to set up the stream either. Here's the trace: > INFO 2011-11-29 20:13:33,397 (Thread-535) - I/O exception > (javax.net.ssl.SSLException) caught when processing request: > java.lang.RuntimeException: Unexpected error: > java.security.InvalidAlgorithmParameterException: the trustAnchors parameter > must be non-empty > DEBUG 2011-11-29 20:13:33,397 (Thread-535) - java.lang.RuntimeException: > Unexpected error: java.security.InvalidAlgorithmParameterException: the > trustAnchors parameter must be non-empty > javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: > java.security.InvalidAlgorithmParameterException: the trustAnchors parameter > must be non-empty > at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1649) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1612) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1595) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1521) > at > com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:64) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at > org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(Unknown > Source) > at > org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.flushRequestOutputStream(Unknown > Source) > at org.apache.commons.httpclient.HttpMethodBase.writeRequest(Unknown > Source) > at org.apache.commons.httpclient.HttpMethodBase.execute(Unknown Source) > at > org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown > Source) > at > org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source) > at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown > Source) > at > org.apache.manifoldcf.crawler.connectors.webcrawler.ThrottledFetcher$ThrottledConnection$ExecuteMethodThread.run(ThrottledFetcher.java:1244) > Caused by: java.lang.RuntimeException: Unexpected error: > java.security.InvalidAlgorithmParameterException: the trustAnchors parameter > must be non-empty > at sun.security.validator.PKIXValidator.(PKIXValidator.java:57) > at sun.security.validator.Validator.getInstance(Validator.java:161) > at > com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:108) > at > com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:204) > at > com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1185) > at > com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136) > at > com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593) > at > com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:893) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138) > at > com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:632) > at > com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) > ... 10 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/s
[jira] [Updated] (CONNECTORS-298) Web connector: SSL trust error message highly misleading
[ https://issues.apache.org/jira/browse/CONNECTORS-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-298: --- Description: When crawling learningresources.nga.gov, the web connector gets a strange exception from certificate verification logic in Sun's SSL implementation. Here's the trace: INFO 2011-11-29 20:13:33,397 (Thread-535) - I/O exception (javax.net.ssl.SSLException) caught when processing request: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty DEBUG 2011-11-29 20:13:33,397 (Thread-535) - java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1649) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1612) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1595) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1521) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:64) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(Unknown Source) at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.flushRequestOutputStream(Unknown Source) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(Unknown Source) at org.apache.commons.httpclient.HttpMethodBase.execute(Unknown Source) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(Unknown Source) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(Unknown Source) at org.apache.commons.httpclient.HttpClient.executeMethod(Unknown Source) at org.apache.manifoldcf.crawler.connectors.webcrawler.ThrottledFetcher$ThrottledConnection$ExecuteMethodThread.run(ThrottledFetcher.java:1244) Caused by: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty at sun.security.validator.PKIXValidator.(PKIXValidator.java:57) at sun.security.validator.Validator.getInstance(Validator.java:161) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.getValidator(X509TrustManagerImpl.java:108) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:204) at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1185) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:893) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1138) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:632) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59) ... 10 more was: When crawling learningresources.nga.gov, the web connector gets a strange exception from certificate verification logic in Sun's SSL implementation. The stack trace indicates that the ManifoldCF secure socket factory may not have been used to set up the stream either. Here's the trace: INFO 2011-11-29 20:13:33,397 (Thread-535) - I/O exception (javax.net.ssl.SSLException) caught when processing request: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty DEBUG 2011-11-29 20:13:33,397 (Thread-535) - java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:190) at com.sun.net.ssl.internal.ssl.SSLSocketImp
[jira] [Updated] (CONNECTORS-299) Crawling using Postgresql 9.1 hangs occasionally for a while
[ https://issues.apache.org/jira/browse/CONNECTORS-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-299: --- Description: The hang takes place because of this postgresql error: ERROR 2011-11-28 14:46:23,959 (Worker thread '25') - Worker thread aborting and restarting due to database connection reset: Database exception: Exception doing query: ERROR: could not serialize access due to read/write dependencies among transactions Detail: Reason code: Canceled on identification as a pivot, during commit attempt. Hint: The transaction might succeed if retried. org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database exception: Exception doing query: ERROR: could not serialize access due to read/write dependencies among transactions Detail: Reason code: Canceled on identification as a pivot, during commit attempt. Hint: The transaction might succeed if retried. at org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:608) at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.commitCurrentTransaction(DBInterfacePostgreSQL.java:1141) at org.apache.manifoldcf.core.database.Database.endTransaction(Database.java:321) at org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.endTransaction(DBInterfacePostgreSQL.java:1112) at org.apache.manifoldcf.crawler.jobs.JobManager.finishDocuments(JobManager.java:4072) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:567) Caused by: org.postgresql.util.PSQLException: ERROR: could not serialize access due to read/write dependencies among transactions This is happening during the commit phase of the transaction, at a point where none of the transaction blocks in ManifoldCF know to look for it. It is therefore likely that all transaction blocks throughout ManifoldCF that deal with deadlock will need to be changed. was: The hang takes place because of this postgresql error: message: ERROR: could not serialize access due to read/write dependencies among transactions Detail: Reason code: Canceled on identification as a pivot, during conflict in checking. Hint: The transaction might succeed if retried., - state: 40001 The state code 40001 should be interpreted as a "deadlock" so that the transaction is retried. > Crawling using Postgresql 9.1 hangs occasionally for a while > > > Key: CONNECTORS-299 > URL: https://issues.apache.org/jira/browse/CONNECTORS-299 > Project: ManifoldCF > Issue Type: Bug > Components: Framework core >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.4 > > > The hang takes place because of this postgresql error: > ERROR 2011-11-28 14:46:23,959 (Worker thread '25') - Worker thread aborting > and restarting due to database connection reset: Database exception: > Exception doing query: ERROR: could not serialize access due to read/write > dependencies among transactions > Detail: Reason code: Canceled on identification as a pivot, during commit > attempt. > Hint: The transaction might succeed if retried. > org.apache.manifoldcf.core.interfaces.ManifoldCFException: Database > exception: Exception doing query: ERROR: could not serialize access due to > read/write dependencies among transactions > Detail: Reason code: Canceled on identification as a pivot, during commit > attempt. > Hint: The transaction might succeed if retried. >at > org.apache.manifoldcf.core.database.Database.executeViaThread(Database.java:608) >at > org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.commitCurrentTransaction(DBInterfacePostgreSQL.java:1141) >at > org.apache.manifoldcf.core.database.Database.endTransaction(Database.java:321) >at > org.apache.manifoldcf.core.database.DBInterfacePostgreSQL.endTransaction(DBInterfacePostgreSQL.java:1112) >at > org.apache.manifoldcf.crawler.jobs.JobManager.finishDocuments(JobManager.java:4072) >at > org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:567) > Caused by: org.postgresql.util.PSQLException: ERROR: could not serialize > access due to read/write dependencies among transactions > This is happening during the commit phase of the transaction, at a point > where none of the transaction blocks in ManifoldCF know to look for it. It is > therefore likely that all transaction blocks throughout ManifoldCF that deal > with deadlock will need to be changed. -- 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,
[jira] [Updated] (CONNECTORS-287) An Alfresco connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-287: --- Attachment: Typetab.png > An Alfresco connector would be helpful > -- > > Key: CONNECTORS-287 > URL: https://issues.apache.org/jira/browse/CONNECTORS-287 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF 0.4 > > Attachments: Typetab.png > > Original Estimate: 120h > Remaining Estimate: 120h > > The idea of this connector is based on the fact that there are many Alfresco > installations that don't yet support the CMIS protocol (2.1-2.9). > I'm starting to think about the Alfresco Repository Connector. > Alfresco doesn't expose any REST API to execute Lucene queries without adding > some custom WebScripts. I would like to implement a connector that doesn't > need to install any other custom plugin and that it can work with any > Alfresco 2.x out of the box installation. > The unique search service exposed by Alfresco via REST is a keyword search > service, but it is not useful for our connector. > I think that the right way to follow is to use the Alfresco Web Services API, > this API is based on the SOAP protocol and we have a specific Alfresco Web > Services Client provided by Alfresco. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-305) Alfresco documentation needs new screenshots
[ https://issues.apache.org/jira/browse/CONNECTORS-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-305: --- Component/s: Alfresco connector > Alfresco documentation needs new screenshots > > > Key: CONNECTORS-305 > URL: https://issues.apache.org/jira/browse/CONNECTORS-305 > Project: ManifoldCF > Issue Type: Bug > Components: Alfresco connector >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF 0.4 > > > The Alfresco end-user documentation shows screen shots of tabs before the > "Server" tab was added, and need to be updated. -- 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-193) Not all output connectors adhere to the standard convention for naming of tabs, form elements, and javascript methods
[ https://issues.apache.org/jira/browse/CONNECTORS-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-193: --- Fix Version/s: (was: ManifoldCF 0.4) ManifoldCF next > Not all output connectors adhere to the standard convention for naming of > tabs, form elements, and javascript methods > - > > Key: CONNECTORS-193 > URL: https://issues.apache.org/jira/browse/CONNECTORS-193 > Project: ManifoldCF > Issue Type: Task > Components: GTS connector, Lucene/SOLR connector >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3 >Reporter: Karl Wright >Assignee: Erlend Garåsen > Fix For: ManifoldCF next > > > The convention for form elements and javascript methods is that all element > names and methods must begin with lowercase "oc". The convention for output > specification tabs is that the tab name should contain the name of the > target, e.g. "GTS Parameters" or "Solr Metadata Mapping". -- 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-311) Files have missing licenses
[
https://issues.apache.org/jira/browse/CONNECTORS-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-311:
---
Component/s: CMIS connector
> Files have missing licenses
> ---
>
> Key: CONNECTORS-311
> URL: https://issues.apache.org/jira/browse/CONNECTORS-311
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector, CMIS connector
>Affects Versions: ManifoldCF 0.4
>Reporter: Karl Wright
>Assignee: Piergiorgio Lucidi
>Priority: Blocker
> Fix For: ManifoldCF 0.4
>
>
> "ant rat-sources" lists the following files as having unapproved or missing
> license headers. This must be addressed before we can release.
> {code}
> [rat:report] Unapproved licenses:
> [rat:report]
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/META-INF/MANIFEST.MF
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/AlfrescoConfig.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/AlfrescoRepositoryConnector.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/Constants.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/ContentModelUtils.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/ContentReader.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/NodeUtils.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/PropertiesUtils.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/alfresco/SearchUtils.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/resource/org/apache/manifoldcf/crawler/connectors/alfresco/hiddenConfiguration.html
> [rat:report]
> C:/wip/mcf/trunk/connectors/alfresco/connector/src/main/resource/org/apache/manifoldcf/crawler/connectors/alfresco/hiddenSpecification.html
> [rat:report]
> C:/wip/mcf/trunk/connectors/cmis/connector/src/main/java/org/apache/manifoldcf/crawler/connectors/cmis/CmisConfig.java
> [rat:report]
> C:/wip/mcf/trunk/connectors/cmis/connector/src/main/resource/org/apache/manifoldcf/crawler/connectors/cmis/hiddenConfiguration.html
> [rat:report]
> C:/wip/mcf/trunk/connectors/cmis/connector/src/main/resource/org/apache/manifoldcf/crawler/connectors/cmis/hiddenSpecification.html
> [rat:report]
> {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] [Updated] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-308:
---
Priority: Blocker (was: Major)
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
> Environment: Windows (although this shouldn't matter)
>Reporter: Karl Wright
>Assignee: Piergiorgio Lucidi
>Priority: Blocker
> Fix For: ManifoldCF 0.4
>
>
> I get this error when I do "ant test":
> {code}
> ...
> setup-alfresco-connector-tests:
> [copy] Copying 6 files to C:\wip\mcf\trunk\connectors\alfresco\lib
> BUILD FAILED
> C:\wip\mcf\trunk\build.xml:316: The following error occurred while executing
> this line:
> C:\wip\mcf\trunk\tests\alfresco-war\build.xml:25: The following error
> occurred while executing this line:
> C:\wip\mcf\trunk\tests\alfresco-war\tools\ant\tasks\tomcat-tasks.xml:30:
> C:\wip\mcf\trunk\${appserver.dir}\server\lib does not exist.
> Total time: 18 seconds
> C:\wip\mcf\trunk>
> {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] [Updated] (CONNECTORS-310) Maven build of Alfresco connector fails
[
https://issues.apache.org/jira/browse/CONNECTORS-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-310:
---
Priority: Blocker (was: Major)
> Maven build of Alfresco connector fails
> ---
>
> Key: CONNECTORS-310
> URL: https://issues.apache.org/jira/browse/CONNECTORS-310
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector, Build
>Affects Versions: ManifoldCF 0.4
>Reporter: Karl Wright
>Assignee: Piergiorgio Lucidi
>Priority: Blocker
> Fix For: ManifoldCF 0.4
>
>
> When I try "mvn clean install" on trunk, I get the following error:
> {code}
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] ManifoldCF SUCCESS [0.752s]
> [INFO] ManifoldCF - Framework SUCCESS [0.099s]
> [INFO] ManifoldCF - Framework - Core . SUCCESS [3.788s]
> [INFO] ManifoldCF - Framework - UI Core .. SUCCESS [1.327s]
> [INFO] ManifoldCF - Framework - Agents ... SUCCESS [12.891s]
> [INFO] ManifoldCF - Framework - Pull Agent ... SUCCESS [19.641s]
> [INFO] ManifoldCF - Framework - Authority Servlet SUCCESS [1.089s]
> [INFO] ManifoldCF - Framework - API Servlet .. SUCCESS [1.209s]
> [INFO] ManifoldCF - Framework - Authority Service SUCCESS [4.296s]
> [INFO] ManifoldCF - Framework - API Service .. SUCCESS [2.148s]
> [INFO] ManifoldCF - Framework - Crawler UI ... SUCCESS [5.093s]
> [INFO] ManifoldCF - Framework - Script Engine SUCCESS [6.514s]
> [INFO] ManifoldCF - Connectors ... SUCCESS [0.075s]
> [INFO] ManifoldCF - Connectors - Active Directory SUCCESS [1.702s]
> [INFO] ManifoldCF - Connectors - Filesystem .. SUCCESS [12.696s]
> [INFO] ManifoldCF - Connectors - MetaCarta GTS ... SUCCESS [1.450s]
> [INFO] ManifoldCF - Connectors - jCIFS ... SUCCESS [1.638s]
> [INFO] ManifoldCF - Connectors - JDBC SUCCESS [1.560s]
> [INFO] ManifoldCF - Connectors - Null Authority .. SUCCESS [1.332s]
> [INFO] ManifoldCF - Connectors - Null Output . SUCCESS [1.027s]
> [INFO] ManifoldCF - Connectors - RSS . SUCCESS [2.727s]
> [INFO] ManifoldCF - Connectors - Solr SUCCESS [1.474s]
> [INFO] ManifoldCF - Connectors - Web . SUCCESS [3.440s]
> [INFO] ManifoldCF - Connectors - CMIS SUCCESS [16.662s]
> [INFO] ManifoldCF - Connectors - OpenSearchServer SUCCESS [2.050s]
> [INFO] ManifoldCF - Connectors - Wiki SUCCESS [12.567s]
> [INFO] ManifoldCF - Connectors - Alfresco FAILURE [2:15.432s]
> [INFO] ManifoldCF - Test materials ... SKIPPED
> [INFO] ManifoldCF - Test Materials - Alfresco WAR SKIPPED
> [INFO] ManifoldCF - Framework - Jetty Runner . SKIPPED
> [INFO] ManifoldCF - Tests 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]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 4:15.090s
> [INFO] Finished at: Thu Dec 08 03:43:10 EST 2011
> [INFO] Final Memory: 72M/181M
> [INFO]
>
> [ERROR] Failed to execute goal on project mcf-alfresco-connector: Could not
> reso
> lve dependencies for project
> org.apache.manifoldcf:mcf-alfresco-connector:jar:0.
> 4.0-SNAPSHOT: The following artifacts could not be resolved:
> org.opensaml:opensa
> ml:jar:1.0.1, bouncycastle:bcprov-jdk15:jar:137,
> xml-security:xmlsec:jar:1.4.1:
> Could not find artifact org.opensaml:opensaml:jar:1.0.1 in alfresco-public
> (http
> ://maven.alfresco.com/nexus/content/groups/public) -> [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 correc
[jira] [Updated] (CONNECTORS-308) "ant test" fails due to Alfresco test problem
[
https://issues.apache.org/jira/browse/CONNECTORS-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-308:
---
Assignee: Karl Wright (was: Piergiorgio Lucidi)
> "ant test" fails due to Alfresco test problem
> -
>
> Key: CONNECTORS-308
> URL: https://issues.apache.org/jira/browse/CONNECTORS-308
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
> Environment: Windows (although this shouldn't matter)
>Reporter: Karl Wright
>Assignee: Karl Wright
>Priority: Blocker
> Fix For: ManifoldCF 0.4
>
>
> I get this error when I do "ant test":
> {code}
> ...
> setup-alfresco-connector-tests:
> [copy] Copying 6 files to C:\wip\mcf\trunk\connectors\alfresco\lib
> BUILD FAILED
> C:\wip\mcf\trunk\build.xml:316: The following error occurred while executing
> this line:
> C:\wip\mcf\trunk\tests\alfresco-war\build.xml:25: The following error
> occurred while executing this line:
> C:\wip\mcf\trunk\tests\alfresco-war\tools\ant\tasks\tomcat-tasks.xml:30:
> C:\wip\mcf\trunk\${appserver.dir}\server\lib does not exist.
> Total time: 18 seconds
> C:\wip\mcf\trunk>
> {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] [Updated] (CONNECTORS-313) movedir-afterbuild
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-313: --- Fix Version/s: (was: ManifoldCF 0.4) ManifoldCF next > movedir-afterbuild > -- > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch > > > The scripts of processes/ and script-engine/ request its location under > $MCF_HOME. I want to move those dirs to beneath example/ after building. -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-313: --- Description: The multiprocess setup does not have an example properties.xml file. We should deliver one, in the right place so that all the scripts find it (the "dist" directory). It would also be helpful to deliver into this directory scripts for: - Registering all the connectors that were built - Starting the agents process was:The scripts of processes/ and script-engine/ request its location under $MCF_HOME. I want to move those dirs to beneath example/ after building. Summary: An example multi-process properties.xml delivered to the "dist" folder would be very helpful (was: movedir-afterbuild) > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF next > > Attachments: CONNECTOR-313.patch > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-288: --- Fix Version/s: ManifoldCF next > An ElasticSearch connector would be helpful > --- > > Key: CONNECTORS-288 > URL: https://issues.apache.org/jira/browse/CONNECTORS-288 > Project: ManifoldCF > Issue Type: New Feature >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF next > > Original Estimate: 120h > Remaining Estimate: 120h > > An ElasticSearch connector could be very useful to spread the use of > ManifoldCF -- 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-261) Maven build needs to be conditionalized in order to handle proprietary connectors
[ https://issues.apache.org/jira/browse/CONNECTORS-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-261: --- Fix Version/s: ManifoldCF next > Maven build needs to be conditionalized in order to handle proprietary > connectors > - > > Key: CONNECTORS-261 > URL: https://issues.apache.org/jira/browse/CONNECTORS-261 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF next > > > The maven build currently does not handle proprietary connectors, but should. > This involves figuring out how to conditionalize it. -- 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-275) Clarify documentation as to how to set up session login for web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-275: --- Fix Version/s: ManifoldCF 0.4 Assignee: Karl Wright Documentation was actually updated, and there is agreement that we will open tickets for new features, so I'm going to resolve this ticket. > Clarify documentation as to how to set up session login for web connector > - > > Key: CONNECTORS-275 > URL: https://issues.apache.org/jira/browse/CONNECTORS-275 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation, Web connector >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-275.patch > > > A book reader has this comment, which basically implies that we need to > improve the documentation for the web connector: > "I was excited to get the full version of the online book, but then > disappointed when it referred back to the online doc for setting up logins > for a Web spidering. The online doc is very vague and only gives one example. > I've used Ultraseek's and Google's spider, but I still find the Session login > sequences non-obvious. > I've got a subscription request into the user mailing list, but here's the > parts that are not clear. > I generally understand about using regexes to define sites and sorting out > content pages from login pages. > But it's not clear why there's TWO Regex's per entry. There's a "Login URL" > regex, and also a "Form name/link target" regex. > It's also not clear about the "page type" radio button choices. > For "rediection", am I saying "look for a redirect event", or am I saying > "then DO a redirect to this page". > And for "form name", what if my login page doesn't have a named form? In the > case of the site I'm trying to spider, when your session expires, you > manually go back to an https page and supply your username and password as > CGI parameters. I know this sounds odd, but it's apparently how a number of > the sites we're trying to spider work, some proprietary software. > Karl, I really think the book or Wiki or doc needs 3 or 4 different examples > of login scenarios. > Here's the scenario I'm trying, if you'd like to use it: > Try to fetch: http://site.com/product?id=1234 > If you get a redirect to: http://site.com/Main.asp > Note that there's no login form nor link on this page. > Then invoke this login URL: > https://site.com/validate?username=me&password=that&otherArg=something > Note that you can't just visit this page and fill in a form, that gives an > error, it has to be passed in (I think as a GET) > Then record the session cookie and try for /product?id=1234 again. > I realize this is odd, I didn't design it. " -- 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-275) Clarify documentation as to how to set up session login for web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-275: --- Resolution: Fixed Status: Resolved (was: Patch Available) Create new feature tickets as needed > Clarify documentation as to how to set up session login for web connector > - > > Key: CONNECTORS-275 > URL: https://issues.apache.org/jira/browse/CONNECTORS-275 > Project: ManifoldCF > Issue Type: Improvement > Components: Documentation, Web connector >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTORS-275.patch > > > A book reader has this comment, which basically implies that we need to > improve the documentation for the web connector: > "I was excited to get the full version of the online book, but then > disappointed when it referred back to the online doc for setting up logins > for a Web spidering. The online doc is very vague and only gives one example. > I've used Ultraseek's and Google's spider, but I still find the Session login > sequences non-obvious. > I've got a subscription request into the user mailing list, but here's the > parts that are not clear. > I generally understand about using regexes to define sites and sorting out > content pages from login pages. > But it's not clear why there's TWO Regex's per entry. There's a "Login URL" > regex, and also a "Form name/link target" regex. > It's also not clear about the "page type" radio button choices. > For "rediection", am I saying "look for a redirect event", or am I saying > "then DO a redirect to this page". > And for "form name", what if my login page doesn't have a named form? In the > case of the site I'm trying to spider, when your session expires, you > manually go back to an https page and supply your username and password as > CGI parameters. I know this sounds odd, but it's apparently how a number of > the sites we're trying to spider work, some proprietary software. > Karl, I really think the book or Wiki or doc needs 3 or 4 different examples > of login scenarios. > Here's the scenario I'm trying, if you'd like to use it: > Try to fetch: http://site.com/product?id=1234 > If you get a redirect to: http://site.com/Main.asp > Note that there's no login form nor link on this page. > Then invoke this login URL: > https://site.com/validate?username=me&password=that&otherArg=something > Note that you can't just visit this page and fill in a form, that gives an > error, it has to be passed in (I think as a GET) > Then record the session cookie and try for /product?id=1234 again. > I realize this is odd, I didn't design it. " -- 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-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-258: --- Fix Version/s: ManifoldCF next > pom.xml refers to jars not available in public repositories > --- > > Key: CONNECTORS-258 > URL: https://issues.apache.org/jira/browse/CONNECTORS-258 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.4 > Environment: all supported platforms >Reporter: Alex Ott >Priority: Minor > Labels: maven > Fix For: ManifoldCF next > > Attachments: mvn-bootstrap.sh > > > Maven's pom.xmls refers to jars that aren't available in public repositories, > as maven central, apache repository, etc. This includes: > - com.bitmechanic:jdbcpool > - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 > is available right now) > I think, that ManifoldCF should adopt the same approach as other Apache > projects, like Tika, when all needed jars first promoted to public > repositories, and only after that, they are used as dependency... -- 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-309) On Canonicalization Tab , Allow regex transforms to modify the URL's for a crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-309: --- Fix Version/s: ManifoldCF next > On Canonicalization Tab , Allow regex transforms to modify the URL's for a > crawl > > > Key: CONNECTORS-309 > URL: https://issues.apache.org/jira/browse/CONNECTORS-309 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector >Affects Versions: ManifoldCF 0.4 >Reporter: Michael J. Kelleher >Priority: Minor > Fix For: ManifoldCF next > > > There was not a "Component" for a Job. Canonicalization is part of the Job > definition. > I would like the ability to use a regex to transform a URL (not necessarily > including the hostname and port). Specifically what I would like to use this > for is to remove certain URL request parameters from the URL. -- 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-313) An example multi-process properties.xml delivered to the "dist" folder would be very helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-313: --- Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.4 I think we are almost done with this, so let's try to pull it into 0.4-incubating. > An example multi-process properties.xml delivered to the "dist" folder would > be very helpful > > > Key: CONNECTORS-313 > URL: https://issues.apache.org/jira/browse/CONNECTORS-313 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.4 >Reporter: Shinichiro Abe >Assignee: Shinichiro Abe >Priority: Minor > Fix For: ManifoldCF 0.4 > > Attachments: CONNECTOR-313.patch, CONNECTOR-313.patch, > register-draft.sh > > > The multiprocess setup does not have an example properties.xml file. We > should deliver one, in the right place so that all the scripts find it (the > "dist" directory). It would also be helpful to deliver into this directory > scripts for: > - Registering all the connectors that were built > - Starting the agents process -- 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-319) AgentRun command needs a shutdown hook
[ https://issues.apache.org/jira/browse/CONNECTORS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-319: --- Priority: Major (was: Critical) > AgentRun command needs a shutdown hook > -- > > Key: CONNECTORS-319 > URL: https://issues.apache.org/jira/browse/CONNECTORS-319 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF next > > > The AgentRun command does not clean up its "agent running" lock on ^C. This > means you always have to do a lock clean if you ^C the agents process in a > multi-process environment. I believe that everything else that needs a > shutdown hook has one. -- 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-319) AgentRun command needs a shutdown hook
[ https://issues.apache.org/jira/browse/CONNECTORS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-319: --- Fix Version/s: (was: ManifoldCF 0.4) ManifoldCF next > AgentRun command needs a shutdown hook > -- > > Key: CONNECTORS-319 > URL: https://issues.apache.org/jira/browse/CONNECTORS-319 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Critical > Fix For: ManifoldCF next > > > The AgentRun command does not clean up its "agent running" lock on ^C. This > means you always have to do a lock clean if you ^C the agents process in a > multi-process environment. I believe that everything else that needs a > shutdown hook has one. -- 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-325) Adeguate the content identifier with the Alfresco node reference
[
https://issues.apache.org/jira/browse/CONNECTORS-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-325:
---
Fix Version/s: (was: ManifoldCF 0.5)
ManifoldCF 0.4
> Adeguate the content identifier with the Alfresco node reference
>
>
> Key: CONNECTORS-325
> URL: https://issues.apache.org/jira/browse/CONNECTORS-325
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.4
>Reporter: Piergiorgio Lucidi
>Assignee: Piergiorgio Lucidi
>Priority: Minor
> Fix For: ManifoldCF 0.4
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> The Alfresco connector support only the UUID to identify contents in
> ManifoldCF, but Alfresco uses a different ID for contents.
> The Node Reference is the unique identifier for nodes in Alfresco and I think
> that we have to conform this ID in the connector too.
> A node reference has the following structure:
> {code}
> :///
> {code}
> The store protocol with the store id build a store reference that could be
> considered in the same way we have workspaces in the JCR standard.
--
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-319) AgentRun command needs a shutdown hook
[ https://issues.apache.org/jira/browse/CONNECTORS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-319: --- Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.5 > AgentRun command needs a shutdown hook > -- > > Key: CONNECTORS-319 > URL: https://issues.apache.org/jira/browse/CONNECTORS-319 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > The AgentRun command does not clean up its "agent running" lock on ^C. This > means you always have to do a lock clean if you ^C the agents process in a > multi-process environment. I believe that everything else that needs a > shutdown hook has one. -- 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-314) Combined MySQL and i18n/Japanese contribution
[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-314: --- Affects Version/s: (was: ManifoldCF next) ManifoldCF 0.5 Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.5 > Combined MySQL and i18n/Japanese contribution > - > > Key: CONNECTORS-314 > URL: https://issues.apache.org/jira/browse/CONNECTORS-314 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process, Framework core, Framework > crawler agent >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and > MySQL database support, all in one patch. -- 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-319) AgentRun command needs a shutdown hook
[ https://issues.apache.org/jira/browse/CONNECTORS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-319: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF 0.4 I was wrong about being wrong. The shutdown actually occurs just as I initially thought, so I am moving this back to ManifoldCF 0.4. > AgentRun command needs a shutdown hook > -- > > Key: CONNECTORS-319 > URL: https://issues.apache.org/jira/browse/CONNECTORS-319 > Project: ManifoldCF > Issue Type: Bug > Components: Framework agents process >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.4 > > > The AgentRun command does not clean up its "agent running" lock on ^C. This > means you always have to do a lock clean if you ^C the agents process in a > multi-process environment. I believe that everything else that needs a > shutdown hook has one. -- 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-333) Solr 3.x and 4.x plugins should use best practices in setting up http connections
[ https://issues.apache.org/jira/browse/CONNECTORS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-333: --- Priority: Critical (was: Major) > Solr 3.x and 4.x plugins should use best practices in setting up http > connections > - > > Key: CONNECTORS-333 > URL: https://issues.apache.org/jira/browse/CONNECTORS-333 > Project: ManifoldCF > Issue Type: Bug > Components: Solr-3.x-component, Solr-4.x-component >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Critical > Fix For: ManifoldCF 0.4 > > > The Solr components need to use keep-alive in order to not accumulate handles > in CLOSE_WAIT. -- 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-333) Solr 3.x and 4.x plugins should use best practices in setting up http connections
[ https://issues.apache.org/jira/browse/CONNECTORS-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-333: --- Fix Version/s: (was: ManifoldCF 0.4) ManifoldCF 0.5 > Solr 3.x and 4.x plugins should use best practices in setting up http > connections > - > > Key: CONNECTORS-333 > URL: https://issues.apache.org/jira/browse/CONNECTORS-333 > Project: ManifoldCF > Issue Type: Bug > Components: Solr-3.x-component, Solr-4.x-component >Affects Versions: ManifoldCF 0.4 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Critical > Fix For: ManifoldCF 0.5 > > > The Solr components need to use keep-alive in order to not accumulate handles > in CLOSE_WAIT. -- 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-314) Combined MySQL and i18n/Japanese contribution
[ https://issues.apache.org/jira/browse/CONNECTORS-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-314: --- Resolution: Fixed Status: Resolved (was: Patch Available) The work in this ticket has been completely replaced by tickets CONNECTORS-334, CONNECTORS-335, and CONNECTORS-336. > Combined MySQL and i18n/Japanese contribution > - > > Key: CONNECTORS-314 > URL: https://issues.apache.org/jira/browse/CONNECTORS-314 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process, Framework core, Framework > crawler agent >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright > Labels: I18N, mysql > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-314-20111225.patch, > CONNECTORS-314-doc20111220.patch, CONNECTORS-314.patch, CONNECTORS-314.patch, > connectors.patch, framework.patch > > > Hitoshi Ozawa wishes to contribute i18n support, a Japanese localization, and > MySQL database support, all in one patch. -- 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-338) Localization data in the wrong place
[ https://issues.apache.org/jira/browse/CONNECTORS-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-338: --- Affects Version/s: ManifoldCF 0.5 Fix Version/s: ManifoldCF 0.5 > Localization data in the wrong place > > > Key: CONNECTORS-338 > URL: https://issues.apache.org/jira/browse/CONNECTORS-338 > Project: ManifoldCF > Issue Type: Bug > Components: Framework core >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.5 > > > The localization data for the Crawler UI is currently put in the core jar. > It should really be moved to the ui-core jar. -- 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-346) Testing hierarchy needs work
[ https://issues.apache.org/jira/browse/CONNECTORS-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-346: --- Fix Version/s: ManifoldCF 0.5 Assignee: Karl Wright > Testing hierarchy needs work > > > Key: CONNECTORS-346 > URL: https://issues.apache.org/jira/browse/CONNECTORS-346 > Project: ManifoldCF > Issue Type: Task > Components: Tests >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > The testing hierarchy is in need of some work. Specifically: > - Load tests should be pulled back into the "tests" directory, if possible, > and given a suffix (LT?) which allows Maven to skip them by default. This > will simplify the ant build.xml too. > - Final ant targets (test-dr, load-dr, UI, etc.) need to be regularized. > They all should begin with "test", for one thing. I don't yet have a > proposal though. > - There's a lot of code duplication in the hierarchy and across the different > database base classes. For example, methods that talk with the API appear in > the base class for each database, and could be shared if there was such a > thing as multiple inheritance. Since there isn't we could instead pull these > into their own support class, like HTMLTester does for the UI stuff. -- 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-344) OpenSearchServer connector needs hiddens to work in multi-tab environment
[ https://issues.apache.org/jira/browse/CONNECTORS-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-344: --- Resolution: Fixed Status: Resolved (was: Patch Available) > OpenSearchServer connector needs hiddens to work in multi-tab environment > - > > Key: CONNECTORS-344 > URL: https://issues.apache.org/jira/browse/CONNECTORS-344 > Project: ManifoldCF > Issue Type: Bug > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.4, ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > Attachments: mcf-344-2.patch, mcf-344.patch > > > The OpenSearchServer connector UI loses your data when you click on different > tabs in either the output connector configuration page or job page. It needs > support for hidden data in order to not do this. See other connector > implementations, notably the CMIS connector (which is similar > architecturally) in order to do this right. -- 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-349) Content binary is not correctly read
[ https://issues.apache.org/jira/browse/CONNECTORS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-349: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF 0.4 r1226302 for release branch > Content binary is not correctly read > > > Key: CONNECTORS-349 > URL: https://issues.apache.org/jira/browse/CONNECTORS-349 > Project: ManifoldCF > Issue Type: Bug > Components: Alfresco connector >Affects Versions: ManifoldCF 0.4 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF 0.4 > > Original Estimate: 4h > Remaining Estimate: 4h > > In the Alfresco Connector there is a wrong prefix to find the content > property for a node. > Now I solved this bug, but I have to solve all the conflicts related to the > latest changes in the 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] [Updated] (CONNECTORS-258) pom.xml refers to jars not available in public repositories
[ https://issues.apache.org/jira/browse/CONNECTORS-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-258: --- Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.3 Assignee: Karl Wright > pom.xml refers to jars not available in public repositories > --- > > Key: CONNECTORS-258 > URL: https://issues.apache.org/jira/browse/CONNECTORS-258 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.4 > Environment: all supported platforms >Reporter: Alex Ott >Assignee: Karl Wright >Priority: Minor > Labels: maven > Fix For: ManifoldCF 0.3 > > Attachments: mvn-bootstrap.sh > > > Maven's pom.xmls refers to jars that aren't available in public repositories, > as maven central, apache repository, etc. This includes: > - com.bitmechanic:jdbcpool > - org.hsqldb:hsqldb:jar:2.2.5.6-9-2011 (at maven central only version 2.2.4 > is available right now) > I think, that ManifoldCF should adopt the same approach as other Apache > projects, like Tika, when all needed jars first promoted to public > repositories, and only after that, they are used as dependency... -- 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-318) Make it easier to trace XML parsing errors
[
https://issues.apache.org/jira/browse/CONNECTORS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-318:
---
Affects Version/s: ManifoldCF 0.5
Fix Version/s: ManifoldCF 0.5
Assignee: Karl Wright
Although it's far better to have the Solr connector handle its own diagnostics,
this patch may still be helpful upon occasion, so I recommend committing it.
> Make it easier to trace XML parsing errors
> --
>
> Key: CONNECTORS-318
> URL: https://issues.apache.org/jira/browse/CONNECTORS-318
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Framework core
>Affects Versions: ManifoldCF 0.5
>Reporter: Martin Goldhahn
>Assignee: Karl Wright
>Priority: Minor
> Fix For: ManifoldCF 0.5
>
> Attachments: XMLDoc.java.patch
>
>
> I had a hard time tracking an erroneous response from Solr. All I got was
> something like this:
> {{[Fatal Error] :112:120: The element type "HR" must be terminated by the
> matching end-tag "".}}
> There was no indication what the error was an what component issued the error.
--
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-309) On Canonicalization Tab , Allow regex transforms to modify the URL's for a crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-309: --- Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.5 Assignee: Karl Wright As stated this looks straightforward and will probably fit in the 0.5 timeframe. > On Canonicalization Tab , Allow regex transforms to modify the URL's for a > crawl > > > Key: CONNECTORS-309 > URL: https://issues.apache.org/jira/browse/CONNECTORS-309 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector >Affects Versions: ManifoldCF 0.4 >Reporter: Michael J. Kelleher >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF 0.5 > > > There was not a "Component" for a Job. Canonicalization is part of the Job > definition. > I would like the ability to use a regex to transform a URL (not necessarily > including the hostname and port). Specifically what I would like to use this > for is to remove certain URL request parameters from the URL. -- 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-351) Alfresco Connector documentation must be updated
[ https://issues.apache.org/jira/browse/CONNECTORS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-351: --- Affects Version/s: ManifoldCF 0.5 Fix Version/s: ManifoldCF 0.5 > Alfresco Connector documentation must be updated > > > Key: CONNECTORS-351 > URL: https://issues.apache.org/jira/browse/CONNECTORS-351 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.5 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Fix For: ManifoldCF 0.5 > > Original Estimate: 2h > Remaining Estimate: 2h > > The Alfresco connector documentation must be updated with the new tenant > domain parameter (text and screenshots). -- 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-345) Jetty Configuration Support
[ https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-345: --- Fix Version/s: ManifoldCF 0.5 Assignee: Karl Wright > Jetty Configuration Support > --- > > Key: CONNECTORS-345 > URL: https://issues.apache.org/jira/browse/CONNECTORS-345 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework core >Affects Versions: ManifoldCF 0.4 > Environment: Jetty Configuration >Reporter: Michael J. Kelleher >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > Can the single process example be extended to support Jetty configuration? > 1) jetty.xml > 2) webdefault.xml > 3) OPTIONS= along with their corresponding XML config files, most > importantly the JMX option, Server,ajp,setuid would be nice to have -- 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-317) minor GUI improvement for jcifs connector
[ https://issues.apache.org/jira/browse/CONNECTORS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-317: --- Affects Version/s: ManifoldCF 0.5 Fix Version/s: ManifoldCF 0.5 Assignee: Karl Wright > minor GUI improvement for jcifs connector > - > > Key: CONNECTORS-317 > URL: https://issues.apache.org/jira/browse/CONNECTORS-317 > Project: ManifoldCF > Issue Type: Improvement > Components: JCIFS connector >Affects Versions: ManifoldCF 0.5 >Reporter: Martin Goldhahn >Assignee: Karl Wright >Priority: Trivial > Fix For: ManifoldCF 0.5 > > Attachments: SharedDriveConnector.java.patch, style.css.patch > > > The table on Paths tab (in edit job for jcifs connector) looks strange. > The Add and Delete button should be aligned, i.e. in the first column. -- 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-366) Solr connector should be fully I18N
[ https://issues.apache.org/jira/browse/CONNECTORS-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-366: --- Component/s: (was: Solr-4.x-component) Lucene/SOLR connector > Solr connector should be fully I18N > --- > > Key: CONNECTORS-366 > URL: https://issues.apache.org/jira/browse/CONNECTORS-366 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 0.5 >Reporter: Hitoshi Ozawa >Assignee: Karl Wright >Priority: Minor > Labels: I18N > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-366.patch > > > Should extract out all messages to properties file. -- 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-371) LiveLink connector should have Japanese message properties file
[ https://issues.apache.org/jira/browse/CONNECTORS-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-371: --- Component/s: (was: Lucene/SOLR connector) LiveLink connector Assignee: Karl Wright > LiveLink connector should have Japanese message properties file > --- > > Key: CONNECTORS-371 > URL: https://issues.apache.org/jira/browse/CONNECTORS-371 > Project: ManifoldCF > Issue Type: Improvement > Components: LiveLink connector >Affects Versions: ManifoldCF 0.5 >Reporter: Hitoshi Ozawa >Assignee: Karl Wright > Labels: I18N > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-371.patch > > > LiveLink connector's Japanese message properties file is not fully translated. -- 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-373) Solr connector Japanese message properties file is not fully translated
[ https://issues.apache.org/jira/browse/CONNECTORS-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-373: --- Component/s: (was: Solr-4.x-component) Lucene/SOLR connector > Solr connector Japanese message properties file is not fully translated > --- > > Key: CONNECTORS-373 > URL: https://issues.apache.org/jira/browse/CONNECTORS-373 > Project: ManifoldCF > Issue Type: Improvement > Components: Lucene/SOLR connector >Affects Versions: ManifoldCF 0.5 >Reporter: Hitoshi Ozawa >Assignee: Karl Wright > Labels: I18N > Fix For: ManifoldCF 0.5 > > Attachments: CONNECTORS-373.patch > > > Solr connector's japanese message properties file should be fully translated. -- 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-406) Some ManifoldCF code doesn't use the MultiThreadedHttpConnectionManager
[ https://issues.apache.org/jira/browse/CONNECTORS-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-406: --- Fix Version/s: ManifoldCF 0.5 Summary: Some ManifoldCF code doesn't use the MultiThreadedHttpConnectionManager (was: Some projects don't use the MultiThreadedHttpConnectionManager) > Some ManifoldCF code doesn't use the MultiThreadedHttpConnectionManager > --- > > Key: CONNECTORS-406 > URL: https://issues.apache.org/jira/browse/CONNECTORS-406 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework agents process, OpenSearchServer connector, > Scripting client >Affects Versions: ManifoldCF 0.5 >Reporter: Luca Stancapiano > Fix For: ManifoldCF 0.5 > > > I signal three projects not using the http multithread manager: > mcf-opensearch-connector > pull-agent (tests) > scripting-engine -- 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-412) Velocity params in Open Search Server Connector
[ https://issues.apache.org/jira/browse/CONNECTORS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-412: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Velocity params in Open Search Server Connector > --- > > Key: CONNECTORS-412 > URL: https://issues.apache.org/jira/browse/CONNECTORS-412 > Project: ManifoldCF > Issue Type: Improvement > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.5 > Environment: velocity >Reporter: Luca Stancapiano >Assignee: Karl Wright > Labels: opensearchserver, velocity > Fix For: ManifoldCF 0.5 > > Attachments: manifold-opensearchserver-velocity-patch, > manifold-opensearchserver-velocity-patch > > > I see opensearchserver is the last connector that uses the custom script in > the html pages instead of velocity. I updated it with velocity as for the > other projects. -- 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-413) OpenSearchServer connector hidden tabs use wrong variable variant so escaping is not right
[ https://issues.apache.org/jira/browse/CONNECTORS-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-413: --- Component/s: OpenSearchServer connector Affects Version/s: ManifoldCF 0.5 > OpenSearchServer connector hidden tabs use wrong variable variant so escaping > is not right > -- > > Key: CONNECTORS-413 > URL: https://issues.apache.org/jira/browse/CONNECTORS-413 > Project: ManifoldCF > Issue Type: Bug > Components: OpenSearchServer connector >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > The hidden tabs for the OpenSearchServer connector use the _B variant of > Velocity variables in some places when they should be using the _A variant. -- 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-288) An ElasticSearch connector would be helpful
[ https://issues.apache.org/jira/browse/CONNECTORS-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-288: --- Resolution: Fixed Fix Version/s: (was: ManifoldCF next) ManifoldCF 0.5 Status: Resolved (was: Patch Available) r1299942 > An ElasticSearch connector would be helpful > --- > > Key: CONNECTORS-288 > URL: https://issues.apache.org/jira/browse/CONNECTORS-288 > Project: ManifoldCF > Issue Type: New Feature >Affects Versions: ManifoldCF 0.5 >Reporter: Piergiorgio Lucidi >Assignee: Piergiorgio Lucidi > Labels: elasticsearch > Fix For: ManifoldCF 0.5 > > Attachments: manifold-elasticsearch-patch, > manifold-elasticsearch-patch, manifold-elasticsearch-patch, > manifold-elasticsearch-patch, manifold-elasticsearch-patch, > manifold-elasticsearch-patch, manifold-elasticsearch-patch, > manifold-elasticsearch-velocity-patch, manifoldcf-elasticsearch-project-patct > > Original Estimate: 120h > Remaining Estimate: 120h > > An ElasticSearch connector could be very useful to spread the use of > ManifoldCF -- 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-347) MySQL HopCount test sometimes fails
[
https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-347:
---
Fix Version/s: (was: ManifoldCF 0.5)
ManifoldCF next
> MySQL HopCount test sometimes fails
> ---
>
> Key: CONNECTORS-347
> URL: https://issues.apache.org/jira/browse/CONNECTORS-347
> Project: ManifoldCF
> Issue Type: Bug
> Components: Framework core
>Affects Versions: ManifoldCF 0.5
>Reporter: Karl Wright
>Assignee: Karl Wright
> Fix For: ManifoldCF next
>
>
> The HopcountMySQLIT test sometimes fails complaining that it is expecting to
> see 6 documents but only sees 4.
> {code}
> [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong
> number of documents processed - expected 6, saw 4
> [junit] at
> org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152)
> {code}
> This does not happen on every run.
--
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-345) Jetty Configuration Support
[ https://issues.apache.org/jira/browse/CONNECTORS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-345: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > Jetty Configuration Support > --- > > Key: CONNECTORS-345 > URL: https://issues.apache.org/jira/browse/CONNECTORS-345 > Project: ManifoldCF > Issue Type: Improvement > Components: Framework core >Affects Versions: ManifoldCF 0.4 > Environment: Jetty Configuration >Reporter: Michael J. Kelleher >Assignee: Karl Wright > Fix For: ManifoldCF next > > > Can the single process example be extended to support Jetty configuration? > 1) jetty.xml > 2) webdefault.xml > 3) OPTIONS= along with their corresponding XML config files, most > importantly the JMX option, Server,ajp,setuid would be nice to have -- 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-309) On Canonicalization Tab , Allow regex transforms to modify the URL's for a crawl
[ https://issues.apache.org/jira/browse/CONNECTORS-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-309: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > On Canonicalization Tab , Allow regex transforms to modify the URL's for a > crawl > > > Key: CONNECTORS-309 > URL: https://issues.apache.org/jira/browse/CONNECTORS-309 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector >Affects Versions: ManifoldCF 0.4 >Reporter: Michael J. Kelleher >Assignee: Karl Wright >Priority: Minor > Fix For: ManifoldCF next > > > There was not a "Component" for a Job. Canonicalization is part of the Job > definition. > I would like the ability to use a regex to transform a URL (not necessarily > including the hostname and port). Specifically what I would like to use this > for is to remove certain URL request parameters from the URL. -- 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-317) minor GUI improvement for jcifs connector
[ https://issues.apache.org/jira/browse/CONNECTORS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-317: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > minor GUI improvement for jcifs connector > - > > Key: CONNECTORS-317 > URL: https://issues.apache.org/jira/browse/CONNECTORS-317 > Project: ManifoldCF > Issue Type: Improvement > Components: JCIFS connector >Affects Versions: ManifoldCF 0.5 >Reporter: Martin Goldhahn >Assignee: Karl Wright >Priority: Trivial > Fix For: ManifoldCF next > > Attachments: SharedDriveConnector.java.patch, style.css.patch > > > The table on Paths tab (in edit job for jcifs connector) looks strange. > The Add and Delete button should be aligned, i.e. in the first column. -- 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-423) Elastic Search connector should handle document metadata
[ https://issues.apache.org/jira/browse/CONNECTORS-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-423: --- Component/s: Elastic Search connector > Elastic Search connector should handle document metadata > > > Key: CONNECTORS-423 > URL: https://issues.apache.org/jira/browse/CONNECTORS-423 > Project: ManifoldCF > Issue Type: Improvement > Components: Elastic Search connector >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright > Fix For: ManifoldCF 0.5 > > > The Elastic Search connector does not currently handle metadata, but it > should. -- 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-426) Alfresco test failure
[
https://issues.apache.org/jira/browse/CONNECTORS-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-426:
---
Description:
The Alfresco tests spit out this exception, which looks like it is the result
of a bug in the test itself:
{code}
[junit] 2012-03-14 14:36:08.423:WARN::/alfresco/download/direct/workspace/Sp
acesStore/c262b38f-1e7d-4319-bb39-f0128188b9c8/testdata1.txt
[junit] java.lang.UnsupportedOperationException: Entity deletion by key is n
ot supported
[junit] at org.alfresco.repo.cache.lookup.EntityLookupCache$EntityLookup
CallbackDAOAdaptor.deleteByKey(EntityLookupCache.java:202)
[junit] at org.alfresco.repo.cache.lookup.EntityLookupCache.deleteByKey(
EntityLookupCache.java:639)
[junit] at org.alfresco.repo.domain.node.AbstractNodeDAOImpl.addNodeAspe
cts(AbstractNodeDAOImpl.java:1987)
[junit] at org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProp
erties(DbNodeServiceImpl.java:526)
[junit] at org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProp
erties(DbNodeServiceImpl.java:439)
[junit] at org.alfresco.repo.node.db.DbNodeServiceImpl.addAspect(DbNodeS
erviceImpl.java:736)
[junit] at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown Source)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:592)
[junit] at org.springframework.aop.support.AopUtils.invokeJoinpointUsing
Reflection(AopUtils.java:307)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
invokeJoinpoint(ReflectiveMethodInvocation.java:183)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
proceed(ReflectiveMethodInvocation.java:150)
[junit] at org.alfresco.repo.tenant.MultiTNodeServiceInterceptor.invoke(
MultiTNodeServiceInterceptor.java:104)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
proceed(ReflectiveMethodInvocation.java:172)
[junit] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(J
dkDynamicAopProxy.java:202)
[junit] at $Proxy10.addAspect(Unknown Source)
[junit] at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown Source)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:592)
[junit] at org.alfresco.repo.service.StoreRedirectorProxyFactory$Redirec
torInvocationHandler.invoke(StoreRedirectorProxyFactory.java:215)
[junit] at $Proxy11.addAspect(Unknown Source)
[junit] at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown Source)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:592)
[junit] at org.springframework.aop.support.AopUtils.invokeJoinpointUsing
Reflection(AopUtils.java:307)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
invokeJoinpoint(ReflectiveMethodInvocation.java:183)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
proceed(ReflectiveMethodInvocation.java:150)
[junit] at org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropert
yInterceptor.java:303)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
proceed(ReflectiveMethodInvocation.java:172)
[junit] at org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropert
yInterceptor.java:303)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
proceed(ReflectiveMethodInvocation.java:172)
[junit] at org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invok
e(NodeRefPropertyMethodInterceptor.java:135)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
proceed(ReflectiveMethodInvocation.java:172)
[junit] at org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invok
e(NodeRefPropertyMethodInterceptor.java:135)
[junit] at org.springframework.aop.framework.ReflectiveMethodInvocation.
proceed(ReflectiveMethodInvocation.java:172)
[junit] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(J
dkDynamicAopProxy.java:202)
[junit] at $Proxy10.addAspect(Unknown Source)
[junit] at org.alfresco.repo.configuration.ConfigurableServiceImpl.makeC
onfigurable(ConfigurableServiceImpl.java:51)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcces
sorImpl.java:39)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
hodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:592)
[jira] [Updated] (CONNECTORS-426) Alfresco test exception
[
https://issues.apache.org/jira/browse/CONNECTORS-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-426:
---
Summary: Alfresco test exception (was: Alfresco test failure)
> Alfresco test exception
> ---
>
> Key: CONNECTORS-426
> URL: https://issues.apache.org/jira/browse/CONNECTORS-426
> Project: ManifoldCF
> Issue Type: Bug
> Components: Alfresco connector
>Affects Versions: ManifoldCF 0.5
>Reporter: Karl Wright
>Priority: Minor
> Fix For: ManifoldCF 0.5
>
>
> The Alfresco tests spit out this exception, which looks like it is the result
> of a bug in the test itself:
> {code}
> [junit] 2012-03-14
> 14:36:08.423:WARN::/alfresco/download/direct/workspace/Sp
> acesStore/c262b38f-1e7d-4319-bb39-f0128188b9c8/testdata1.txt
> [junit] java.lang.UnsupportedOperationException: Entity deletion by key
> is n
> ot supported
> [junit] at
> org.alfresco.repo.cache.lookup.EntityLookupCache$EntityLookup
> CallbackDAOAdaptor.deleteByKey(EntityLookupCache.java:202)
> [junit] at
> org.alfresco.repo.cache.lookup.EntityLookupCache.deleteByKey(
> EntityLookupCache.java:639)
> [junit] at
> org.alfresco.repo.domain.node.AbstractNodeDAOImpl.addNodeAspe
> cts(AbstractNodeDAOImpl.java:1987)
> [junit] at
> org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProp
> erties(DbNodeServiceImpl.java:526)
> [junit] at
> org.alfresco.repo.node.db.DbNodeServiceImpl.addAspectsAndProp
> erties(DbNodeServiceImpl.java:439)
> [junit] at
> org.alfresco.repo.node.db.DbNodeServiceImpl.addAspect(DbNodeS
> erviceImpl.java:736)
> [junit] at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown
> Source)
> [junit] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
> hodAccessorImpl.java:25)
> [junit] at java.lang.reflect.Method.invoke(Method.java:592)
> [junit] at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsing
> Reflection(AopUtils.java:307)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:150)
> [junit] at
> org.alfresco.repo.tenant.MultiTNodeServiceInterceptor.invoke(
> MultiTNodeServiceInterceptor.java:104)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> [junit] at
> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(J
> dkDynamicAopProxy.java:202)
> [junit] at $Proxy10.addAspect(Unknown Source)
> [junit] at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown
> Source)
> [junit] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
> hodAccessorImpl.java:25)
> [junit] at java.lang.reflect.Method.invoke(Method.java:592)
> [junit] at
> org.alfresco.repo.service.StoreRedirectorProxyFactory$Redirec
> torInvocationHandler.invoke(StoreRedirectorProxyFactory.java:215)
> [junit] at $Proxy11.addAspect(Unknown Source)
> [junit] at sun.reflect.GeneratedMethodAccessor273.invoke(Unknown
> Source)
> [junit] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMet
> hodAccessorImpl.java:25)
> [junit] at java.lang.reflect.Method.invoke(Method.java:592)
> [junit] at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsing
> Reflection(AopUtils.java:307)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> invokeJoinpoint(ReflectiveMethodInvocation.java:183)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:150)
> [junit] at
> org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropert
> yInterceptor.java:303)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> [junit] at
> org.alfresco.repo.node.MLPropertyInterceptor.invoke(MLPropert
> yInterceptor.java:303)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> [junit] at
> org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invok
> e(NodeRefPropertyMethodInterceptor.java:135)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodInvocation.
> proceed(ReflectiveMethodInvocation.java:172)
> [junit] at
> org.alfresco.repo.node.NodeRefPropertyMethodInterceptor.invok
> e(NodeRefPropertyMethodInterceptor.java:135)
> [junit] at
> org.springframework.aop.framework.ReflectiveMethodI
[jira] [Updated] (CONNECTORS-425) Elastic Search documentation missing images
[ https://issues.apache.org/jira/browse/CONNECTORS-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-425: --- Priority: Major (was: Blocker) Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > Elastic Search documentation missing images > --- > > Key: CONNECTORS-425 > URL: https://issues.apache.org/jira/browse/CONNECTORS-425 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright > Fix For: ManifoldCF next > > > The ElasticSearch documentation refers to images that never actually were > committed. Looking back at the ticket, they were never included in any > uploaded patch either. These are: > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-connection-parameters.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-user.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-job-parameters.PNG. (No context > info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-history-report.PNG. (No context > info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-connection-parameters.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-user.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-job-parameters.PNG. (No context > info available) > [exec] ERROR - Image not found. URI: > cocoon://en_US/images/en_US/elasticsearch-history-report.PNG. (No context > info available) > [exec] X [0] > ja_JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG BROKEN: No > pipeline matched request: ja_ > JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG. > (No context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-user_ja_JP.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-job-parameters_ja_JP.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-history-report_ja_JP.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-connection-parameters_ja_JP.PNG. > (No context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-user_ja_JP.PNG. (No context info > available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-job-parameters_ja_JP.PNG. (No > context info available) > [exec] ERROR - Image not found. URI: > cocoon://ja_JP/images/ja_JP/elasticsearch-history-report_ja_JP.PNG. (No > context info available) -- 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-428) Include license label for IPA fonts
[ https://issues.apache.org/jira/browse/CONNECTORS-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-428: --- Description: The IPA fonts are to be considered Category-B licensed, according to LEGAL-123, so we will need to add mention of them in the licensing materials. See http://www.apache.org/legal/resolved.html#category-b was: The IPA fonts are to be considered Category-B licensed, so we will need to add mention of them in the licensing materials. See http://www.apache.org/legal/resolved.html#category-b > Include license label for IPA fonts > --- > > Key: CONNECTORS-428 > URL: https://issues.apache.org/jira/browse/CONNECTORS-428 > Project: ManifoldCF > Issue Type: Task > Components: Documentation >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.5 > > > The IPA fonts are to be considered Category-B licensed, according to > LEGAL-123, so we will need to add mention of them in the licensing materials. > See http://www.apache.org/legal/resolved.html#category-b -- 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-404) Japanese "how to build and deploy" page out of date
[ https://issues.apache.org/jira/browse/CONNECTORS-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-404: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > Japanese "how to build and deploy" page out of date > --- > > Key: CONNECTORS-404 > URL: https://issues.apache.org/jira/browse/CONNECTORS-404 > Project: ManifoldCF > Issue Type: Bug > Components: Documentation >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Hitoshi Ozawa > Fix For: ManifoldCF next > > > Recent changes to the build target are not reflected in the Japanese version > of "how to build and deploy". -- 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-394) Alt tags in crawler UI navigation are not internationalized
[ https://issues.apache.org/jira/browse/CONNECTORS-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-394: --- Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF next > Alt tags in crawler UI navigation are not internationalized > --- > > Key: CONNECTORS-394 > URL: https://issues.apache.org/jira/browse/CONNECTORS-394 > Project: ManifoldCF > Issue Type: Bug > Components: Framework crawler agent >Affects Versions: ManifoldCF 0.5 >Reporter: Karl Wright >Assignee: Hitoshi Ozawa >Priority: Minor > Fix For: ManifoldCF next > > > The alt tags for all the navigation links in the crawler UI navigation pane > are not internationalized. -- 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-430) An error should be returned if invalid seeds are typed into the seeds list for the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-430: --- Attachment: CONNECTORS-430.patch > An error should be returned if invalid seeds are typed into the seeds list > for the web connector > > > Key: CONNECTORS-430 > URL: https://issues.apache.org/jira/browse/CONNECTORS-430 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3, > ManifoldCF 0.4, ManifoldCF 0.5 >Reporter: Erlend Garåsen >Assignee: Erlend Garåsen >Priority: Minor > Fix For: ManifoldCF 0.6 > > Attachments: CONNECTORS-430.patch, CONNECTORS-430.patch > > > If you create a job for the web connector and enter an invalid URL into the > seeds list, any value is accepted. An error message should be returned to the > user in order to prevent invalid seeds. -- 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-441) Build needs some refactoring on how to handle integration tasks
[ https://issues.apache.org/jira/browse/CONNECTORS-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-441: --- Affects Version/s: ManifoldCF 0.5 Fix Version/s: (was: ManifoldCF 0.6) ManifoldCF 0.5 > Build needs some refactoring on how to handle integration tasks > --- > > Key: CONNECTORS-441 > URL: https://issues.apache.org/jira/browse/CONNECTORS-441 > Project: ManifoldCF > Issue Type: Task > Components: Build >Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > The integration directories for connectors no longer contain the integration > binaries. The binaries are copied twice, once to the integration area, and > then to the dist/integration area. A single copy would make life much easier. -- 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-442) Binary distributions should not include build.xml, pom.xml or common-build.xml
[ https://issues.apache.org/jira/browse/CONNECTORS-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-442: --- Fix Version/s: (was: ManifoldCF 0.6) ManifoldCF 0.5 > Binary distributions should not include build.xml, pom.xml or common-build.xml > -- > > Key: CONNECTORS-442 > URL: https://issues.apache.org/jira/browse/CONNECTORS-442 > Project: ManifoldCF > Issue Type: Bug > Components: Build >Affects Versions: ManifoldCF 0.5, ManifoldCF 0.6 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.5 > > > Since sources are not included, pom.xml, build.xml, and common-build.xml are > useless and confusing in the binary packages. -- 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-449) UI tests broken due to buggy browser simulator
[ https://issues.apache.org/jira/browse/CONNECTORS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-449: --- Affects Version/s: (was: ManifoldCF 0.5) ManifoldCF 0.6 Fix Version/s: (was: ManifoldCF 0.5) ManifoldCF 0.6 > UI tests broken due to buggy browser simulator > -- > > Key: CONNECTORS-449 > URL: https://issues.apache.org/jira/browse/CONNECTORS-449 > Project: ManifoldCF > Issue Type: Bug > Components: Tests >Affects Versions: ManifoldCF 0.6 >Reporter: Karl Wright >Assignee: Karl Wright >Priority: Blocker > Fix For: ManifoldCF 0.6 > > > The UI tests aren't working due to a regression in the browser simulator. -- 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-449) UI tests broken due to buggy browser simulator
[ https://issues.apache.org/jira/browse/CONNECTORS-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-449: --- Priority: Major (was: Blocker) > UI tests broken due to buggy browser simulator > -- > > Key: CONNECTORS-449 > URL: https://issues.apache.org/jira/browse/CONNECTORS-449 > Project: ManifoldCF > Issue Type: Bug > Components: Tests >Affects Versions: ManifoldCF 0.6 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.6 > > > The UI tests aren't working due to a regression in the browser simulator. -- 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-430) An error should be returned if invalid seeds are typed into the seeds list for the web connector
[ https://issues.apache.org/jira/browse/CONNECTORS-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-430: --- Resolution: Fixed Status: Resolved (was: Patch Available) > An error should be returned if invalid seeds are typed into the seeds list > for the web connector > > > Key: CONNECTORS-430 > URL: https://issues.apache.org/jira/browse/CONNECTORS-430 > Project: ManifoldCF > Issue Type: Improvement > Components: Web connector >Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3, > ManifoldCF 0.4, ManifoldCF 0.5 >Reporter: Erlend Garåsen >Assignee: Erlend Garåsen >Priority: Minor > Fix For: ManifoldCF 0.6 > > Attachments: CONNECTORS-430.patch, CONNECTORS-430.patch > > > If you create a job for the web connector and enter an invalid URL into the > seeds list, any value is accepted. An error message should be returned to the > user in order to prevent invalid seeds. -- 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-459) Move to JDK1.6
[ https://issues.apache.org/jira/browse/CONNECTORS-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright updated CONNECTORS-459: --- Description: It turns out that there are a number of dependency upgrades we can't do until we move completely to jdk1.6, such as going to jetty 7, tomcat 7 components, axis 2.x, etc. In addition, certain connectors already require jdk1.6 (the alfresco connector, for instance). Other dependencies must be built by us in order to get a jdk1.5-compatible version. Since jdk1.6 has been end-of-life'd, it may be the time to make this move. was: It turns out that there are a number of dependency upgrades we can't do until we move completely to jdk1.6, such as going to jetty 7, axis 2.x, etc. In addition, certain connectors already require jdk1.6 (the alfresco connector, for instance). Other dependencies must be built by us in order to get a jdk1.5-compatible version. Since jdk1.6 has been end-of-life'd, it may be the time to make this move. > Move to JDK1.6 > -- > > Key: CONNECTORS-459 > URL: https://issues.apache.org/jira/browse/CONNECTORS-459 > Project: ManifoldCF > Issue Type: Improvement > Components: Build >Affects Versions: ManifoldCF 0.6 >Reporter: Karl Wright >Assignee: Karl Wright > Fix For: ManifoldCF 0.6 > > > It turns out that there are a number of dependency upgrades we can't do until > we move completely to jdk1.6, such as going to jetty 7, tomcat 7 components, > axis 2.x, etc. In addition, certain connectors already require jdk1.6 (the > alfresco connector, for instance). Other dependencies must be built by us in > order to get a jdk1.5-compatible version. > Since jdk1.6 has been end-of-life'd, it may be the time to make this move. -- 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-460) ManifoldCF authority service doesn't handle multi-domain environments
[
https://issues.apache.org/jira/browse/CONNECTORS-460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-460:
---
Affects Version/s: ManifoldCF 0.6
ManifoldCF 0.5
ManifoldCF 0.1
ManifoldCF 0.2
ManifoldCF 0.3
ManifoldCF 0.4
Fix Version/s: ManifoldCF 0.6
Assignee: Karl Wright
> ManifoldCF authority service doesn't handle multi-domain environments
> -
>
> Key: CONNECTORS-460
> URL: https://issues.apache.org/jira/browse/CONNECTORS-460
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Active Directory authority, Authority Service
>Affects Versions: ManifoldCF 0.1, ManifoldCF 0.2, ManifoldCF 0.3,
> ManifoldCF 0.4, ManifoldCF 0.5, ManifoldCF 0.6
> Environment: Two Active Directory domains: {{internal.com}} and
> {{external.com}}
> I'm indexing a Sharepoint site, where that site has permissions set
> from_both_domains
>Reporter: Colin Anderson
>Assignee: Karl Wright
> Labels: active-directory, authorization, security
> Fix For: ManifoldCF 0.6
>
>
> The ManifoldCF authority service doesn't handle multi-domain environments.
> The authority service returns a list of SIDs for the specified user, from all
> available ManifoldCF authorities, for example:
> {{TOKEN:InternalAD:S-1-5-21-1234567890-1234567890-1234567890-1234}}
> Note that the SID is prefixed with the name of the ManifoldCF authority.
> Here is my setup:
> Output connector: Solr
> Authority connector1: Active Directory ({{internal.com}} domain), named
> {{InternalAD}}
> Authority connector2: Active Directory ({{external.com}} domain), named
> {{ExternalAD}}
> Repository connector: Sharepoint
> If I set the Sharepoint repository connector to use the authority 'None
> (Global Authority)', then {{allow_token_document}} will contain SIDs that are
> _not_ prefixed with any authority name, for example:
> {{S-1-5-21-1234567890-1234567890-1234567890-1234}}
> It is therefore not possible to get any search results, because the authority
> service tokens will not match the stored tokens (because they _are_ prefixed
> with authority names).
> If I set the Sharepoint repository connector to use one of the AD authorities
> 'InternalAD', then {{allow_token_document}} will contain SIDs that are
> prefixed with 'InternalAD', for example:
> {{TOKEN:InternalAD:S-1-5-21-1234567890-1234567890-1234567890-1234}}
> However, the prefix is _always_ 'InternalAD', even if the user/group actually
> belongs to the {{external.com}} domain. Therefore it is not possible for
> users in the {{external.com}} domain to get any search results, because the
> authority service tokens will not match the stored tokens.
> In essence, there seems to be a mismatch between the tokens that the
> authority service outputs, and those that repository connectors output.
> Perhaps one solution would be to use the authority 'None (Global Authority)',
> and modify the authority service to take an extra query parameter that
> prevents it from prefixing SIDs with the authority name.
--
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-347) MySQL HopCount test sometimes fails
[
https://issues.apache.org/jira/browse/CONNECTORS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-347:
---
Affects Version/s: ManifoldCF 0.6
Fix Version/s: (was: ManifoldCF next)
ManifoldCF 0.6
> MySQL HopCount test sometimes fails
> ---
>
> Key: CONNECTORS-347
> URL: https://issues.apache.org/jira/browse/CONNECTORS-347
> 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
>
>
> The HopcountMySQLIT test sometimes fails complaining that it is expecting to
> see 6 documents but only sees 4.
> {code}
> [junit] org.apache.manifoldcf.core.interfaces.ManifoldCFException: Wrong
> number of documents processed - expected 6, saw 4
> [junit] at
> org.apache.manifoldcf.filesystem_tests.HopcountMySQLIT.hopcountCheck(HopcountMySQLIT.java:152)
> {code}
> This does not happen on every run.
--
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
