Menu
▾
▴
RE: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
|
From: McDonald, B. <Bru...@ba...> - 2003-10-01 21:11:59
|
Yes,
It works that means that there is something wrong with the way your configuration is working. Can you do the following:
1. move the qin\config\* to the qin directory and change the BABELDOC_USER to reflect this. Does this fix it?
2. move the pipeline-test.properties file to the directory pipeline (which used to be in config) - change the
pipeline/config.properties file to reflect this change.
3 Let me know
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Wednesday, October 01, 2003 2:18 PM
To: McDonald, Bruce
Cc: Babeldoc Developer List; David Glick
Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
Bruce:
The result is
C:\btest1>babeldoc process -p btest -f dummy.txt
<2003-10-01 13:15:42,538> INFO [main] : PipelineStage name: entry
Wow! Does it mean it works yet? I can't wait!
Qin
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
"McDonald,
Bruce" To: Qin Ding/ASD/CSC@CSC
<Bruce.McDonald cc: Babeldoc Developer List
@bankofamerica.c <bab...@li...>, David Glick
om> <dg...@co...>
Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user]
10/01/03 12:46 Questions. Please Help
PM
That last statement should be:
babeldoc pipeline -L btest
Now lets run something through the pipeline
babeldoc process -p btest -f dummy.txt
where dummy.txt is any small file.
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Wednesday, October 01, 2003 1:40 PM
To: McDonald, Bruce
Cc: Babeldoc Developer List; David Glick
Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
Bruece: Please see the results below and also the directory layout.
(See attached file: btest1.zip)
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
"McDonald,
Bruce" To: Qin
Ding/ASD/CSC@CSC
<Bruce.McDonald cc: Babeldoc Developer
List
@bankofamerica.c
<bab...@li...>, David Glick
om> <dg...@co...>
Subject: RE:
[Babeldoc-devel] Re: [Babeldoc-user]
10/01/03 11:44 Questions. Please Help
AM
Ok, so all of the tests passed fine. Your problems aren't as terminal as I
thought.
Now I want you to create a very simple pipeline. Do it in a new directory
(not in the c:\Qin directory).
0. setup your path: set PATH=%BABELDOC_HOME%\bin;%PATH% (confirm babeldoc
runs)
1. Create new directory: c:\btest1
2. Set BABELDOC_USER=c:\btest1 (confirm this)
BABELDOC_HOME=c:\babeldoc
BABELDOC_USER=c:\btest1
3. cd %BABELDOC_USER% (confirm this)
C:\>cd %BABELDOC_USER%
C:\btest1>
4. mkdir pipeline
5. create the file c:\btest1\pipeline\config.properties :
----cut here----
btest.type=simple
btest.configFile=pipeline/btest
----cut here----
6. Create the file c:\btest1\pipeline\btest.properties
----cut here----
entryStage=entry
entry.stageType=Null
entry.nextStage=null
----cut here----
7. Confirm that this pipeline exists: "babeldoc pipeline -Q" You should
see your pipeline listed.
C:\btest1>babeldoc pipeline -Q
test-xml, entry stage: entry
documentation, entry stage: attrdefault
btest, entry stage: entry
test, entry stage: entry
8. Now list the pipeline stages: "babeldoc pipeline -L nlpe1_rpt"
C:\btest1>babeldoc pipeline -L nlpe1_rpt
<2003-10-01 12:33:13,172> ERROR [main] :
[PipelineCommand.getPipelineStageFacto
ry] Possibly invalid pipeline stage: nlpe1_rpt
Plz report back.
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Wednesday, October 01, 2003 12:24 PM
To: McDonald, Bruce
Cc: Babeldoc Developer List; David Glick
Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
Bruce:
See the results below please:
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
"McDonald,
Bruce" To: Qin
Ding/ASD/CSC@CSC
<Bruce.McDonald cc: Babeldoc Developer
List
@bankofamerica.c
<bab...@li...>, David Glick
om> <dg...@co...>
Subject: RE:
[Babeldoc-devel] Re: [Babeldoc-user]
10/01/03 10:40 Questions. Please Help
AM
Qin,
I want to start from scratch with this.
Do the following and report back plz:
0. Make sure that JDK is installed and at least 1.4.1 : java -fullversion
C:\>java -fullversion
java full version "1.4.1_03-b02"
1. Download babeldoc 1.2.0-RC1 into the directory c:\babeldoc (or
somewhere)
in c:\babeldoc
2. Set your BABELDOC_HOME= ... this directory
BABELDOC_HOME=c:\babeldoc
BABELDOC_USER=c:\qin\config
HOMEDRIVE=H:
HOMEPATH=\
JAVA_HOME=D:\j2sdk1.4.1_03
3. echo %BABELDOC_HOME% - make sure that this is correct.
C:\>echo %BABELDOC_HOME%
c:\babeldoc
4. cd %BABELDOC_HOME% - you should be in the babeldoc directory.
C:\>cd %BABELDOC_HOME%
C:\babeldoc>
5. run this: bin\babeldoc - you should see babeldoc version
C:\babeldoc\bin>babeldoc
Usage: babeldoc <command>
where command must be one of:
xls2xml, scanmon, setupwiz, addstagewiz, lightconfig, sqlload, pipeline,
setentr
ywiz, journal, process, journalbrowser, flat2xml, scanner, guiprocess,
pipelineb
uilder, module, babelfish.
Babeldoc 1.2.0-RC1 Copyright (C) 2002 Bruce McDonald, Dejan Krsmanovic, et
al.
Babeldoc comes with ABSOLUTELY NO WARRANTY;
This is free software, and you are welcome to redistribute
it under certain conditions
6. run this: bin\babeldoc process -p test -f test/quickstart/stats.xml
C:\babeldoc\bin>babeldoc process -p test -f test/quickstart/stats.xml
<2003-10-01 11:16:31,245> INFO [main] : PipelineStage name: entry
<2003-10-01 11:16:31,555> INFO [main] : PipelineStage name: transform
<2003-10-01 11:16:32,667> INFO [main] : PipelineStage name: choose
<2003-10-01 11:16:32,717> INFO [main] : PipelineStage name: writer
7. Check the file: stats.html
The stats.html is in bin directory
<HTML>
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<TITLE>1998
Major League Baseball Statistics
</TITLE>
</HEAD>
<BODY>
<H1>1998
Major League Baseball Statistics
</H1>
<H2 ALIGN="CENTER">American League</H2>
.....
8. run this: bin\babeldoc process -p documentation
C:\babeldoc\bin>babeldoc process -p documentation
<2003-10-01 11:21:57,544> INFO [main] : PipelineStage name: attrdefault
<2003-10-01 11:21:58,015> INFO [main] : PipelineStage name: callstages
<2003-10-01 11:21:58,015> INFO [main] : PipelineStage name: stagexml
<2003-10-01 11:21:58,586> INFO [main] : PipelineStage name: stagexform
<2003-10-01 11:21:59,687> INFO [main] : PipelineStage name: stagewriter
<2003-10-01 11:21:59,727> INFO [main] : PipelineStage name: callscanners
<2003-10-01 11:21:59,727> INFO [main] : PipelineStage name: scannerxml
<2003-10-01 11:21:59,887> INFO [main] : PipelineStage name:
scannertransform
<2003-10-01 11:22:00,098> INFO [main] : PipelineStage name: scannerwriter
<2003-10-01 11:22:00,118> INFO [main] : PipelineStage name:
callprocessors
<2003-10-01 11:22:00,118> INFO [main] : PipelineStage name: processorxml
<2003-10-01 11:22:00,258> INFO [main] : PipelineStage name:
processortransform
<2003-10-01 11:22:00,338> INFO [main] : PipelineStage name:
processorwriter
<2003-10-01 11:22:00,358> INFO [main] : PipelineStage name: loaduserguide
<2003-10-01 11:22:00,408> INFO [main] : PipelineStage name:
callgenerateug
<2003-10-01 11:22:00,418> INFO [main] : PipelineStage name: basename
<2003-10-01 11:22:00,438> INFO [main] : PipelineStage name: templatize
<2003-10-01 11:22:00,488> INFO [main] : PipelineStage name: choose
<2003-10-01 11:22:00,518> INFO [main] : PipelineStage name: transform
<2003-10-01 11:22:20,277> INFO [main] : PipelineStage name: writer
<2003-10-01 11:22:20,317> INFO [main] : PipelineStage name: loaddevguide
<2003-10-01 11:22:20,327> INFO [main] : PipelineStage name:
callgeneratedg
<2003-10-01 11:22:20,327> INFO [main] : PipelineStage name: basename
<2003-10-01 11:22:20,347> INFO [main] : PipelineStage name: templatize
<2003-10-01 11:22:20,367> INFO [main] : PipelineStage name: choose
<2003-10-01 11:22:20,367> INFO [main] : PipelineStage name: transform
<2003-10-01 11:22:25,454> INFO [main] : PipelineStage name: writer
Report back plz
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Wednesday, October 01, 2003 11:29 AM
To: McDonald, Bruce
Cc: Babeldoc Developer List; David Glick
Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
Bruce and David:
At home (XP), I tried to do the same thing (download the babeldoc, set it
up using your directory template and babeldoc_home and babeldoc_user. I got
the exact same error: entryStage not found. I asked a friend of mine
outside from this company this morning to do the same thing at his pc (NT),
he reported to me with the same error just a moment ago. How could that
be?!
David: at home I even tried different version of jvm from 1.4.1_01, and
1.4.1_02. No difference.
Is there a way I can ask the system to output more debug infomation like
changing log4j log level from error to debug? I guess that's too easy.
Otherwise, I need to add the debugging statements in "setupConfigData" of
SimplePipelineStageResolver class? Let me download the source code, and
add the debugging code, recompile the source and ran our test again. I
will let you know the result.
If anyone out there other thatn Bruce using babeldoc on windows, please let
me know how on earth you did that so successfully. I am very anxious to
make it work. Thank you very much.
Qin
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
"McDonald,
Bruce" To: Qin Ding
<qd...@cs...>, David Glick
<Bruce.McDonald <dg...@co...>
@bankofamerica.c cc: Babeldoc Developer
List
om>
<bab...@li...>
Subject: RE:
[Babeldoc-devel] Re: [Babeldoc-user]
10/01/03 08:15 Questions. Please Help
AM
Qin,
It looks like you will have to actually debug this yourself since no-one
else is experiencing this error. Please look at the code in the
SimplePipelineStageResolver. Place debuging statements in the
setupConfigData to view what is going on.
regards,
Bruce.
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Tuesday, September 30, 2003 6:01 PM
To: David Glick
Cc: Babeldoc Developer List; McDonald, Bruce
Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
David:
1 After changed test-pipeline.configFile=c:/qin/test/test-pipeline, still
got the same error;
2. I don't understand what you want "try renaming the 'test-pipeline'
directory to 'testpipe'". There is no directory by the name of
test-pipeline. Can I call you if you don't mind? It would be easier for
us to go through this?
Qin
----------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit written
agreement or government initiative expressly permitting the use of e-mail
for such purpose.
----------------------------------------------------------------------------------------
David Glick
<dglick To: Qin
Ding/ASD/CSC@CSC
@cox.net> cc: Babeldoc Developer
List
<bab...@li...>, "McDonald,
09/30/03 04:47 Bruce"
<Bru...@ba...>
PM Subject: Re:
[Babeldoc-devel] Re: [Babeldoc-user]
Questions. Please Help
Try changing test-pipeline.configFile to c:/qin/test/test-pipeline. If
that
doesn't work, try renaming the 'test-pipeline' directory to 'testpipe',
change the test-pipeline.configFile=c:/qin/test/testpipe, and try to run it
again.
David
On Tuesday 30 September 2003 2:33 pm, Qin Ding wrote:
> David:
>
> Here it is:
>
> test-pipeline.type=simple
> test-pipeline.configFile=test/test-pipeline
>
>
>
---------------------------------------------------------------------------
>-------------
>
> This is a PRIVATE message. If you are not the intended recipient, please
> delete without copying and kindly advise us by e-mail of the mistake in
> delivery. NOTE: Regardless of content, this e-mail shall not operate to
> bind CSC to any order or other contract unless pursuant to explicit
written
> agreement or government initiative expressly permitting the use of e-mail
> for such purpose.
>
---------------------------------------------------------------------------
>-------------
>
>
>
>
>
> David Glick
> <dglick To: Qin
> Ding/ASD/CSC@CSC @cox.net> cc: Babeldoc Developer
List
> <bab...@li...>, "McDonald, 09/30/03 04:34
> Bruce" <Bru...@ba...> PM
Subject:
> Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
>
>
>
>
>
> Okay, if you can now run the documentation pipeline, either we're getting
> somewhere, or else you have a bunch of problems that we need to fix, one
at
> a
> time. Let's get rolling...
>
> Is this still your configuration:
>
> --- setenv.bat ---
> set BABELDOC_HOME=c:\babeldoc
> set BABELDOC_USER=c:\qin\config
> set JAVA_HOME=D:\j2sdk1.4.1_03
> set PATH=%BABELDOC_HOME%\bin;%JAVA_HOME%\bin;%PATH%
>
> --- test-pipeline.properties ---
> entryStage=initialize
> initialize.stageType=Scripting
> initialize.nextStage=null
> initialize.failOnError=true
> initialize.language=javascript
> initialize.script=\
> java.io.File file = new java.io.File(document.get("file_name"));\
> TestManager.validate(file);
>
> If so, then please also post c:\qin\config\pipeline\config.properties.
>
>
> David
>
> On Tuesday 30 September 2003 2:14 pm, Qin Ding wrote:
> > > > > set BABELDOC_HOME=c:\babeldoc-bin-1.2.0-RC1
> > > > > set BABELDOC_USER=c:\qin\config
> > > > > set JAVA_HOME=D:\j2sdk1.4.1_03
> > > > >
> > > > > set PATH=%BABELDOC_HOME%\bin;%JAVA_HOME%\bin;%PATH%
> > > > >
> > > > > Please see the attached the qin.zip file.(See attached file:
>
> qin.zip)
>
> > > > > This is a PRIVATE message. If you are not the intended recipient,
> > >
> > > please
> > >
> > > > > delete without copying and kindly advise us by e-mail of the
>
> mistake
>
> > in
> >
> > > > > delivery. NOTE: Regardless of content, this e-mail shall not
>
> operate
>
> > to
> >
> > > > > bind CSC to any order or other contract unless pursuant to
explicit
> > > >
> > > > written
> > > >
> > > > > agreement or government initiative expressly permitting the use
of
> > >
> > > e-mail
> > >
> > > > > for such purpose.
>
>
---------------------------------------------------------------------------
>
> > > > >-------------
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > "McDonald,
> > > > > Bruce" To: Qin
> > > > > Ding/ASD/CSC@CSC <Bruce.McDonald cc: Babeldoc
>
> Developer
>
> > > > List
> > > >
> > > > > @bankofamerica.c <bab...@li...>,
> >
> > David
> >
> > > > > Glick om> <dg...@co...>
> > > > > Subject: RE:
> > > > > [Babeldoc-devel] Re: [Babeldoc-user] 09/29/03 10:31
> > >
> > > Questions.
> > >
> > > > > Please Help AM
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Download the latest version and try again - I suspect your
> >
> > installation
> >
> > > > is
> > > >
> > > > > broken.
> > > > >
> > > > > -----Original Message-----
> > > > > From: Qin Ding [mailto:qd...@cs...]
> > > > > Sent: Friday, September 26, 2003 1:10 PM
> > > > > To: McDonald, Bruce
> > > > > Cc: Babeldoc Developer List; David Glick
> > > > > Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user] Questions.
Please
> > >
> > > Help
> > >
> > > > > Bruce:
> > > > >
> > > > > This is the test-pipeline.properties:
> > > > >
> > > > > entryStage=initialize
> > > > >
> > > > > initialize.stageType=Scripting
> > > > > initialize.nextStage=null
> > > > > initialize.failOnError=true
> > > > > initialize.language=javascript
> > > > > initialize.script=\
> > > > > java.io.File file = new java.io.File(document.get
("file_name"));
>
> \
>
> > > > > TestManager.validate(file);
--
David Glick
619-475-4052
dg...@co...
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Babeldoc-devel mailing list
Bab...@li...
https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Babeldoc-devel mailing list
Bab...@li...
https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
|
