|
From: David G. <dg...@co...> - 2003-09-30 19:48:37
|
This is an odd one, that's for sure. The first thing I would suggest trying is the default documentation pipeline. CD to your Babeldoc directory and try this: build\bin\babeldoc process -p documentation -f readme\userguide.xml -a "style=html" It's right out of the quickstart-en.txt file in the Babeldoc directory, so you may want to refer to it if you have any problems. Let us know if you can create the documentation. Thanks, David On Tuesday 30 September 2003 12:37 pm, Qin Ding wrote: > David: > > c:\qin is the template that Bruce gave to me. I actually ran both places to > see if there was any differences. Of course each time when I switch between > these two directories, I first changed the BABELDOC_USER to point to the > one I was running under. > > Alas, there is no difference in the results when running cmd and command. > No difference in c:\babeltest or c:\qin. Seems to me that babeldoc can see > the dummy file and can see the test-pipeline, but in the > test-pipeline.properties, somehow it could not recognize the entryStage. > Is there a way I can debug through the code to figure out where it fails. > How can I set it up to do the debugging? Thanks. > > 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, "McDonald, Bruce" @cox.net> > <Bru...@ba...> cc: Babeldoc Developer List > 09/30/03 02:09 <bab...@li...> PM > Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. > Please Help > > > > > > Hi Qin, > > Your dump below shows you starting in the c:\babeldoc-bin-1.2.0-RC1\bin > directory. For the template that I sent you, you need to start from the > c:\qin directory (assuming that's where you installed the zip file I sent). > > Also, I think you mentioned that you run on Windows NT. You may want to > try > changing the long pathnames to mangled paths to see if that makes any > difference. I haven't run NT in years, but I thought that NT provided two > command shells: command.com and cmd.exe. As I recall, cmd.exe allows long > > path names and command.com prefers mangled names. Just a thought... > > > David > > On Tuesday 30 September 2003 8:44 am, Qin Ding wrote: > > Bruce and David: > > > > I downloaded the latest the version (babeldoc-bin-1.2.0-RC1) and modified > > the env BABELDOC_HOME to point to c:\babeldoc-bin-1.2.0-RC1. Started a > > new > > > command shell and re-ran the test: > > C:\babeldoc-bin-1.2.0-RC1\bin>babeldoc process -p test-pipeline -f c: > > \qin\dummy.txt > > > > I got the same error: > > <2003-09-30 10:35:19,670> ERROR [main] : [PipelineFeeder.process] > > com.babeldoc.core.pipeline.PipelineException: PipelineStage: entryStage > > not > > > found > > at > > com.babeldoc.core.pipeline.PipelineStageFactory.getEntryStageName(Unknown > > Source) > > at com.babeldoc.core.pipeline.PipelineFactory.process(Unknown > > Source) > > > at > > com.babeldoc.core.pipeline.PipelineFactoryFactory.process(Unknown > > > Source) > > at > > com.babeldoc.core.pipeline.feeder.SynchronousFeeder.process(Unknown > > Source) > > > at com.babeldoc.core.pipeline.feeder.FeederFactory.process(Unknown > > Source) > > at > > com.babeldoc.core.pipeline.command.PipelineFeeder.process(Unknown > > > Source) > > at > > com.babeldoc.core.pipeline.command.PipelineFeeder.execute(Unknown > > > Source) > > at com.babeldoc.core.BabeldocCommand.executeCommand(Unknown Source) > > at com.babeldoc.core.BabeldocCommand.<init>(Unknown Source) > > at com.babeldoc.core.pipeline.command.PipelineFeeder.<init>(Unknown > > Source) > > at com.babeldoc.core.pipeline.command.PipelineFeeder.main(Unknown > > Source) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 > > >9) at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp > > >l.java:25) at java.lang.reflect.Method.invoke(Method.java:324) > > at com.babeldoc.core.Main.handleCommand(Unknown Source) > > at com.babeldoc.core.Main.main(Unknown Source) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 > > >9) at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp > > >l.java:25) at java.lang.reflect.Method.invoke(Method.java:324) > > at com.babeldoc.init.Main.runBabeldocMain(Unknown Source) > > at com.babeldoc.init.Main.main(Unknown Source) > > > > > > Here is the modified setenv.bat file: > > 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); > > > > > > Here is the error: > > > > <2003-09-26 11:05:11,960> INFO [Thread-1] : Processing document... > > <2003-09-26 11:05:11,960> ERROR [Thread-1] : [AsynchronousFeeder$1.run] > > com.babeldoc.core.pipeline.PipelineException: PipelineStage: entryStage > > not > > > foun > > d > > at > > com.babeldoc.core.pipeline.PipelineStageFactory.getEntryStageName(Unk > > nown Source) > > at com.babeldoc.core.pipeline.PipelineFactory.process(Unknown > > Source) > > at > > com.babeldoc.core.pipeline.PipelineFactoryFactory.process(Unknown Sou > > rce) > > at > > com.babeldoc.core.pipeline.feeder.SynchronousFeeder.process(Unknown S > > ource) > > at > > com.babeldoc.core.pipeline.feeder.AsynchronousFeeder.actuallyProcess( > > Unknown Source) > > at > > com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown So > > urce) > > at > > EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown So > > urce) > > at java.lang.Thread.run(Thread.java:536) > > > > > > 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] > > 09/26/03 11:39 Questions. Please Help > > > > AM > > > > > > > > > > > > > > > > Huh?!??! > > > > I dont understand the issue here. > > > > Somewhere in your pipeline definition file, place the line: > > > > entryStage=<<some pipeline stage name>> > > > > Where the entryStage is pointing to the first pipeline stage in your > > pipeline. > > > > regards, > > Bruce. > > > > > > -----Original Message----- > > From: Qin Ding [mailto:qd...@cs...] > > Sent: Friday, September 26, 2003 12:14 PM > > To: David Glick > > Cc: Babeldoc Developer List > > Subject: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help > > > > > > > > David: > > > > I don't have the Unix-to-Windows converter program; but I retyped the > > file > > > into wordpad and saved as text document. However, it is no possitive > > effect. It still gives the same error, that is, entryStage not found. > > I > > > then copied the first line from src > > example/scripting/pipeline/scannerxml.properties. Again, no use. The same > > error occured no matter what I did. Seems like the application could not > > recognize the "entryStage". By the way, I am using version > > bin-1.1.9-dev. > > > Any idea? > > > > 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. > > --------------------------------------------------------------------------- > > >------------- > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > 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 -- David Glick Transmit Consulting, Inc 619-475-4052 dg...@tr... |