Menu

Problem running scanner

Help
Edmond Yau
2004-02-23
2004-03-19
  • Edmond Yau

    Edmond Yau - 2004-02-23

    I'm having difficulties making the scanner run.

    I've tried the example, as well as my own attempt and each time I get the following error:

    Warning: JAVA_HOME environment variable is not set.
      If babeldoc fails because sun.* classes could not be found
      you will need to set the JAVA_HOME environment variable
      to the installation directory of java.

    <2004-02-23 16:51:12,640> INFO  [main] :  Initializing workers:
    <2004-02-23 16:51:12,640> INFO  [main] :  No configured workers found!
    <2004-02-23 16:51:12,640> INFO  [main] :  Stopping feeder
    <2004-02-23 16:51:13,140> INFO  [shutdown] :  Stopping feeder

    I am using the following line to invoke it:
    babeldoc scanner -s E:\Babeldoc\babeldoc=bin-1.2.0\examples\scanner\config.properties

    where the path is the path to the config file in the example.

    Any suggestions?

    Cheers,
        Ed

     
    • Sherman Wood

      Sherman Wood - 2004-02-23

      Have you run through the steps outlined in the user guide?

      http://www.babeldoc.com

      In left hand nav:

      Documentation
      User Guide

      In content pane:
      Running the examples

      Sherman

       
    • Edmond Yau

      Edmond Yau - 2004-02-23

      Yes - set all my environmental variables as instructed.

      Example 1.1 runs fine and I get the results.

      But Examples 1.2 and 1.3 dont give me anything useful.

      1.2 gives me the following:

      Warning: JAVA_HOME environment variable is not set.
        If babeldoc fails because sun.* classes could not be found
        you will need to set the JAVA_HOME environment variable
        to the installation directory of java.

      <2004-02-23 17:16:47,484> ERROR [main] :  [PipelineCommand.doConfig] Invalid data for pipeline stage: test.extract

      I'm not sure why BabelDoc is complaining about JAVA_HOME, as it is set!

      Ed

       
      • Sherman Wood

        Sherman Wood - 2004-02-23

        test.extract does not exist - it is just an example.

        JAVA_HOME missing is weird, if the other examples are working.

        Try the examples. They are a bit old, but should work and give you a flavor.

        Sherman

         
    • Edmond Yau

      Edmond Yau - 2004-02-24

      I've tried running through the examples, and they work fine.

      I've also managed to run the flatfile examples, but still no luck on running the scanner...

      This is what is in config.properties:

      "directory.type=directory
      directory.period=10000
      directory.inDirectory=E:\BabelDoc\babeldoc-bin-1.2.0\examples\scanner\tmp\in
      directory.doneDirectory=E:\BabelDoc\babeldoc-bin-1.2.0\examples\scanner\tmp\out
      directory.pipeline=test"

      I've tried taking off the .properties the end of the command, having absolute directory paths, tried version 1.2.1 but same result. What am I doing wrong? 

       
    • Edmond Yau

      Edmond Yau - 2004-03-19

      I'm still experiencing difficulties with the directory scanner.  The pipeline that is named in config file works, but I am being told that there are no configured workers.  Can someone help by sending me an example of a working directory scanner application / suggestions for debugging this?

      Here is the scanner config file:

      "me.type = directory
      me.period = 1000
      me.inDirectory = /tmp/in
      me.doneDirectory = /tmp/done
      me.pipeLine = ats"

      Here is the output:
      "<2004-03-19 14:07:26,296> INFO  [main] :  Initializing workers:
      <2004-03-19 14:07:26,296> INFO  [main] :  No configured workers found!
      <2004-03-19 14:07:26,296> INFO  [main] :  Stopping feeder
      <2004-03-19 14:07:26,828> INFO  [shutdown] :  Stopping feeder
      "

       
    • Santiago Begué

      Santiago Begué - 2004-03-19

      in your $BABELDOC_HOME or your $BABELDOC_USER directory:
      # mkdir scanner
      create file scanner/config.properties and in this file put "exact matching":
      me.type=directory
      me.period=1000
      me.inDirectory=/tmp/in
      me.doneDirectory=/tmp/done
      me.pipeline=ats

      remark: is pipeline, not pipeLine.

       
    • Edmond Yau

      Edmond Yau - 2004-03-19

      Many thanks for that prompt answer!

      It was the mistyped "pipeline" that was causing all the problems...

      It now works perfectly.

      Regards
        Ed

       

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.