Thanks Karl,
I'm happy to be the guinea pig and will be happy to continue to be for any
proprietary repos to which I have access.
I'm having a problem that I am hesitant to reply with as I feel like I should
be able to figure it out on my own. I am attempting to build the retrieved
source on my home dev station (Windows). I do not have Forrest installed, but
based on my experience thus far, I think it should not be necessary for the
framework and connectors.
The core-deps and deps make without error.
I am getting the error listed below when I build, Apologies if this is obvious.
compile-crawler-ui:
BUILD FAILEDC:\apache-manifoldcf-2.0\build.xml:173: The following error
occurred while executing this
line:C:\apache-manifoldcf-2.0\framework\build.xml:325:
org.apache.jasper.JasperException: The -uriroot option must specify a
pre-existing directory at org.apache.jasper.JspC.execute(JspC.java:718)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483) at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154) at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at
sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483) at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348) at
org.apache.tools.ant.Target.execute(Target.java:435) at
org.apache.tools.ant.Target.performTasks(Target.java:456) at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at
org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:441) at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292) at
sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483) at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348) at
org.apache.tools.ant.Target.execute(Target.java:435) at
org.apache.tools.ant.Target.performTasks(Target.java:456) at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393) at
org.apache.tools.ant.Project.executeTarget(Project.java:1364) at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.apache.tools.ant.Main.runBuild(Main.java:851) at
org.apache.tools.ant.Main.startAnt(Main.java:235) at
org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at
org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Total time: 15 seconds
On Sunday, January 25, 2015 4:19 AM, Karl Wright <[email protected]>
wrote:
Hi Guy,
I've updated the release branches also -- that would be
https://svn.apache.org/repos/asf/manifoldcf/branches/release-1.8-branch and
https://svn.apache.org/repos/asf/manifoldcf/branches/release-2.0-branch .
Please check out the branch you are using and build from there, and let me know
what happens.
I apologize for the broken code; MCF 1.8/2.0 revised most connectors
completely, but we were not in a position to exercise proprietary connectors
ourselves due to the fact that we had no working instances here. So thanks for
being the guinea pig. ;-)
Karl
On Sun, Jan 25, 2015 at 6:43 AM, Karl Wright <[email protected]> wrote:
Hi Guy,
This looks like it was broken during the MCF 1.8 release cycle. I've created
CONNECTORS-1151 to track this; hope to have a patch for you shortly.
Thanks,
Karl
On Sun, Jan 25, 2015 at 5:10 AM, Guy Sperry <[email protected]> wrote:
I am unable to get the FileNet connector to process documents. I was able to
compile the repository connection. The filenet-registry and filenet-server
processes run correctly. I am able to create a repository connection. I can
create a job successfully. The class and index information are retrieved
properly. I have distilled the job down to a class with a single document and I
am only retrieving the Id and DocumentTitle fields. When the job runs I
consistently get the error: "String index out of range: -1". I have downloaded
the source code and traced the error. It seems that the function is expecting a
comma in the identifier that is not there.
I am connecting to FileNet P8 5.1 using the CEWS40MTOM service URL. My output
is going to Solr 4.10.3.
Please let me know if you have any ideas on how I can get this to work or if
there is any further information I can provide.
Relevant Log Entries: .DEBUG 2015-01-24 23:16:19,924 (Startup thread) -
FileNet: Inside addSeedDocumentsDEBUG 2015-01-24 23:16:20,064 (Startup thread)
- FileNet: Seeding with identifier
'{E8B8CFA6-CEE4-4204-BCD8-49DF19A7F468}'DEBUG 2015-01-24 23:16:21,544 (Worker
thread '1') - FileNet: Inside processDocumentsDEBUG 2015-01-24 23:16:21,560
(Worker thread '1') - Filenet: Getting version for identifier
'{E8B8CFA6-CEE4-4204-BCD8-49DF19A7F468}'FATAL 2015-01-24 23:16:21,560 (Worker
thread '1') - Error tossed: String index out of range:
-1java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at
java.lang.String.substring(Unknown Source) at
org.apache.manifoldcf.crawler.connectors.filenet.FilenetConnector.processDocuments(FilenetConnector.java:1136)
at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:379)
Thanks
Guy Sperry
