Menu
▾
▴
babeldoc-devel — Babeldoc developer list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(14) |
Mar
(107) |
Apr
(211) |
May
(93) |
Jun
(158) |
Jul
(159) |
Aug
(368) |
Sep
(188) |
Oct
(151) |
Nov
(115) |
Dec
(98) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(25) |
Feb
|
Mar
(33) |
Apr
(28) |
May
(116) |
Jun
(2) |
Jul
(117) |
Aug
(19) |
Sep
(9) |
Oct
(2) |
Nov
|
Dec
(4) |
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(9) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
(22) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(267) |
Sep
|
Oct
|
Nov
(6) |
Dec
(512) |
| 2008 |
Jan
(187) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael A. <mic...@ze...> - 2003-10-04 16:37:05
|
PS: How do you build the html docs from the XML? I can't find an ant rule. |
|
From: Michael A. <mic...@ze...> - 2003-10-04 16:26:58
|
Hi, What's the preferred form for patches? I added regex filtering for the Mail scanner on the From, To and Subject fields (I saw it in the list of requirements), and updated the docs. I've got the output of a cvs diff -c in a file. Can I send the file in? BTW, what o people use to edit the docs? I started using jEdit, but it's pretty ugly. Are there any plug-ins to jEdit that I can use to do it properly? Or perhaps my settings are bad. Cheers... MikeA |
|
From: Bruce M. <br...@mc...> - 2003-10-04 00:53:16
|
You need to import your class into the javascript. Please read the
documentation found at the Mozilla/Rhino/JS site (use google to find the
URL).
On Friday 03 October 2003 01:33 pm, Qin Ding wrote:
> David and Bruce:
>
> I put the my validation jar into c:\qin\lib foder and set CLASSPATH=c:
> \qin\lib\myvalidation.jar;%CLASSPATH%. Re-ran the pipeline. Still got the
> error for not finding the class. I built a small app to verify
> myvalidation.jar using the same classpath. It finds the
> TestManager.validation without the problem. So the problem seems at the my
> script. Here is my script:
> initialize.script=\
> longlegs.core.filevalidation.TestManager.validate(document.get
> ("file_name"),\
> document.getInputStream());\
>
> 1. Internally, when this script is received, how does ScriptingStage class
> do to start search the external jar?
> 2. I don't think the external application stage will help me because our
> validation jar is not an "application"; and it only takes either
> java.io.File or java.io.InputStream.
> 3. If I can not make it work using Scripting stage, I am think just modify
> the directory scanner to include the call to my validation routine after it
> picks up the file there. Can I do that by extending the DirectoryScanner?
> Once again, if I extend the class, where should I deploy it?
> 4. There are lots of directories with the numbers as their names. What are
> those directories? Does the system perge them eventually?
>
> <2003-10-03 09:59:55,637> INFO [main] : PipelineStage name: initialize
> <2003-10-03 09:59:56,108> ERROR [main] :
> [DefaultPipelineStageErrorHandler.handlePipelineStageError] PipelineStage
> name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
> Script processing failed
> <2003-10-03 09:59:56,108> ERROR [main] : [PipelineFeeder.process]
> com.babeldoc.core.pipeline.PipelineException: Script processing failed
> at
> com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> Source)
> at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> Source)
> at
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPipe
>lineStage(Unknown Source)
> at
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(Unk
>nown Source)
> at com.babeldoc.core.pipeline.PipelineStageFactory.process(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)
> Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal Error:
> ReferenceError: "longlegs" is not defined.
> at
> org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> Source)
> at org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
> Source)
> at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> at org.apache.bsf.BSFManager$6.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.bsf.BSFManager.exec(Unknown Source)
> ... 27 more
>
>
> ---------------------------------------------------------------------------
>-------------
>
> 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
|
|
From: Qin D. <qd...@cs...> - 2003-10-03 17:34:38
|
David and Bruce:
I put the my validation jar into c:\qin\lib foder and set CLASSPATH=c:
\qin\lib\myvalidation.jar;%CLASSPATH%. Re-ran the pipeline. Still got the
error for not finding the class. I built a small app to verify
myvalidation.jar using the same classpath. It finds the
TestManager.validation without the problem. So the problem seems at the my
script. Here is my script:
initialize.script=\
longlegs.core.filevalidation.TestManager.validate(document.get
("file_name"),\
document.getInputStream());\
1. Internally, when this script is received, how does ScriptingStage class
do to start search the external jar?
2. I don't think the external application stage will help me because our
validation jar is not an "application"; and it only takes either
java.io.File or java.io.InputStream.
3. If I can not make it work using Scripting stage, I am think just modify
the directory scanner to include the call to my validation routine after it
picks up the file there. Can I do that by extending the DirectoryScanner?
Once again, if I extend the class, where should I deploy it?
4. There are lots of directories with the numbers as their names. What are
those directories? Does the system perge them eventually?
<2003-10-03 09:59:55,637> INFO [main] : PipelineStage name: initialize
<2003-10-03 09:59:56,108> ERROR [main] :
[DefaultPipelineStageErrorHandler.handlePipelineStageError] PipelineStage
name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
Script processing failed
<2003-10-03 09:59:56,108> ERROR [main] : [PipelineFeeder.process]
com.babeldoc.core.pipeline.PipelineException: Script processing failed
at
com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
Source)
at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
Source)
at
com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPipelineStage(Unknown
Source)
at
com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(Unknown
Source)
at com.babeldoc.core.pipeline.PipelineStageFactory.process(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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)
Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal Error:
ReferenceError: "longlegs" is not defined.
at
org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
Source)
at org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
Source)
at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
at org.apache.bsf.BSFManager$6.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.bsf.BSFManager.exec(Unknown Source)
... 27 more
----------------------------------------------------------------------------------------
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.
----------------------------------------------------------------------------------------
|
|
From: Dejan K. <dej...@nb...> - 2003-10-03 14:41:50
|
Hi all, In current Babeldoc implementation there is many limitations (you knew that, right!). On of them is that documents and pipelines cannot "comunicate". That is - there is no way to know what happened with one documents what another documents is processing. And sometimes you need to know it. One idea that I had and discussed with Bruce today is having attributes of differnet scopes. Currently, you only can use attributes that are local to document. We could introduce "pipeline scope" for attributes local to particular pipeline and "global scope" for attributes that are global to all pipelines... The issues here are: - syntax - implementation -... I guess the implemenation should not be a problem since we could use Map fileds (for example in PipelineFactory class...). global scope could be some static field. Any ideas? Toughts? Dejan P.S. Oh yes, this should be aimed to 1.4 release (and 1.3 dev version). |
Update of /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker
In directory sc8-pr-cvs1:/tmp/cvs-serv9441/modules/scanner/src/com/babeldoc/scanner/worker
Modified Files:
FtpScanner.java DirectoryScanner.java NullScanner.java
SqlScanner.java ExternalApplicationScanner.java
HttpScanner.java
Log Message:
Fixing CVS tags
Index: FtpScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/FtpScanner.java,v
retrieving revision 1.22
retrieving revision 1.23
diff -C2 -d -r1.22 -r1.23
*** FtpScanner.java 30 Sep 2003 14:36:37 -0000 1.22
--- FtpScanner.java 3 Oct 2003 13:08:40 -0000 1.23
***************
*** 60,64 ****
*
* $Header$
! * $DateTime$
* $Author$
*
--- 60,64 ----
*
* $Header$
! * $Date$
* $Author$
*
***************
*** 87,91 ****
import com.babeldoc.core.option.ConfigOption;
import com.babeldoc.core.option.IConfigOptionType;
- import com.babeldoc.core.option.ValueListConfigOptionType;
import com.babeldoc.core.pipeline.PipelineDocument;
import com.babeldoc.scanner.ScannerConfigurationException;
--- 87,90 ----
***************
*** 99,103 ****
*
* @author dejank
! * @version 1.0
*/
public class FtpScanner extends ScannerWorker {
--- 98,102 ----
*
* @author dejank
! * @version $Revision$
*/
public class FtpScanner extends ScannerWorker {
Index: DirectoryScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/DirectoryScanner.java,v
retrieving revision 1.22
retrieving revision 1.23
diff -C2 -d -r1.22 -r1.23
*** DirectoryScanner.java 24 Sep 2003 14:26:29 -0000 1.22
--- DirectoryScanner.java 3 Oct 2003 13:08:40 -0000 1.23
***************
*** 90,94 ****
*
* @author Bmcdonald, Dejan Krsmanovic
! * @version 1.0
*/
public class DirectoryScanner extends ScannerWorker {
--- 90,94 ----
*
* @author Bmcdonald, Dejan Krsmanovic
! * @version $Revision$
*/
public class DirectoryScanner extends ScannerWorker {
Index: NullScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/NullScanner.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** NullScanner.java 12 Sep 2003 01:09:17 -0000 1.3
--- NullScanner.java 3 Oct 2003 13:08:40 -0000 1.4
***************
*** 15,19 ****
*
* @author bmcdonald
! * @version 1.1
*/
public class NullScanner extends ScannerWorker {
--- 15,19 ----
*
* @author bmcdonald
! * @version $Revision$
*/
public class NullScanner extends ScannerWorker {
Index: SqlScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/SqlScanner.java,v
retrieving revision 1.15
retrieving revision 1.16
diff -C2 -d -r1.15 -r1.16
*** SqlScanner.java 1 Oct 2003 08:33:35 -0000 1.15
--- SqlScanner.java 3 Oct 2003 13:08:40 -0000 1.16
***************
*** 100,104 ****
*
* @author dejank
! * @version 1.0
*/
public class SqlScanner extends ScannerWorker {
--- 100,104 ----
*
* @author dejank
! * @version $Revision$
*/
public class SqlScanner extends ScannerWorker {
Index: ExternalApplicationScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/ExternalApplicationScanner.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** ExternalApplicationScanner.java 17 Sep 2003 22:13:20 -0000 1.8
--- ExternalApplicationScanner.java 3 Oct 2003 13:08:40 -0000 1.9
***************
*** 87,92 ****
* produce any standard output, the scanner does not process the message.
*
! * @author Bmcdonald, Dejan Krsmanovic
! * @version 1.1
*/
public class ExternalApplicationScanner extends ScannerWorker {
--- 87,92 ----
* produce any standard output, the scanner does not process the message.
*
! * @author Bmcdonald
! * @version $Revision$
*/
public class ExternalApplicationScanner extends ScannerWorker {
Index: HttpScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/HttpScanner.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** HttpScanner.java 5 Sep 2003 13:28:29 -0000 1.6
--- HttpScanner.java 3 Oct 2003 13:08:40 -0000 1.7
***************
*** 60,64 ****
*
* $Header$
! * $DateTime$
* $Author$
*
--- 60,64 ----
*
* $Header$
! * $Date$
* $Author$
*
***************
*** 98,102 ****
*
* @author bmcdonald
! * @version 1.1
*/
public class HttpScanner extends ScannerWorker {
--- 98,102 ----
*
* @author bmcdonald
! * @version $Revision$
*/
public class HttpScanner extends ScannerWorker {
|
|
From: <de...@us...> - 2003-10-03 13:05:48
|
Update of /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker
In directory sc8-pr-cvs1:/tmp/cvs-serv9019/modules/scanner/src/com/babeldoc/scanner/worker
Modified Files:
MailboxScanner.java
Log Message:
Fixed few bugs that can occur if connection unsuccessfull
Index: MailboxScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/MailboxScanner.java,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -d -r1.27 -r1.28
*** MailboxScanner.java 1 Oct 2003 12:23:42 -0000 1.27
--- MailboxScanner.java 3 Oct 2003 13:05:45 -0000 1.28
***************
*** 60,64 ****
*
* $Header$
! * $DateTime$
* $Author$
*
--- 60,64 ----
*
* $Header$
! * $Date$
* $Author$
*
***************
*** 98,102 ****
*
* @author Bruce McDonald, Dejan Krsmanovic
! * @version 1.0
*/
public class MailboxScanner extends ScannerWorker {
--- 98,102 ----
*
* @author Bruce McDonald, Dejan Krsmanovic
! * @version $Revision$
*/
public class MailboxScanner extends ScannerWorker {
***************
*** 148,163 ****
Properties props = new Properties();
session = Session.getInstance(props, null);
! store = session.getStore(protocol);
store.connect(host, username, password);
folder = store.getFolder(folder_);
folder.open(Folder.READ_WRITE);
-
Message[] messages = folder.getMessages();
-
for (int i = 0; i < messages.length; i++) {
processMessage(messages[i]);
deleteMessage(messages[i]);
! }
! } catch (Exception x) {
throw new ScannerException(
I18n.get("scanner.MailboxScanner.error.scanning"),
--- 148,161 ----
Properties props = new Properties();
session = Session.getInstance(props, null);
! store = session.getStore(protocol);
store.connect(host, username, password);
folder = store.getFolder(folder_);
folder.open(Folder.READ_WRITE);
Message[] messages = folder.getMessages();
for (int i = 0; i < messages.length; i++) {
processMessage(messages[i]);
deleteMessage(messages[i]);
! }
! } catch (Exception x) {
throw new ScannerException(
I18n.get("scanner.MailboxScanner.error.scanning"),
***************
*** 165,172 ****
} finally {
try {
! if (folder.isOpen()) {
folder.close(true);
}
! store.close();
} catch (Exception e) {
getLog().logError("Error closing store and folder", e);
--- 163,172 ----
} finally {
try {
! if (folder != null && folder.isOpen()) {
folder.close(true);
}
! if (store != null) {
! store.close();
! }
} catch (Exception e) {
getLog().logError("Error closing store and folder", e);
***************
*** 327,331 ****
//TODO: This should be done more clever then this
attrs.put("contentType", "text/plain");
!
//feed document
this.enqueue(data, attrs);
--- 327,331 ----
//TODO: This should be done more clever then this
attrs.put("contentType", "text/plain");
! attrs.put(ScannerWorker.FILE_NAME_KEY, originalMessage.getSubject());
//feed document
this.enqueue(data, attrs);
***************
*** 335,338 ****
--- 335,339 ----
if (getFrom.equalsIgnoreCase(ATTACHMENT)) {
StringBuffer message = getMailContent(part);
+ attrs.put(ScannerWorker.FILE_NAME_KEY, part.getFileName());
this.enqueue(message.toString().getBytes(), attrs);
}
|
|
From: McDonald, B. <Bru...@ba...> - 2003-10-03 04:32:23
|
Qin,
The ExternalApplicationStage is available for calling external applications or script files from a pipeline. The pipeline provides the document contents to the script/program via the STDIN stream.
For more details please look at the user guide and the source code.
Bruce.
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Thursday, October 02, 2003 1:21 PM
To: David Glick
Cc: bab...@li...
Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
Thank, David. I'll talk to you tomorrow.
Yes, the validate(String fileName, InputStream is) in TestManager is static
method.
Bruce: What should I do in order for my jar visible to the scripting code.
Right now, I just drop it into %BABELDOC_HOME%/lib directory along with all
the jars that BabelDoc depends on.
David, I don't follow what you said about batch file and
externalApplication Stage. I'll try to see if there are some examples and
talk to you later. Thank you.
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" <qd...@cs...>
@cox.net> cc: bab...@li...
Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user]
10/02/03 12:06 Questions. Please Help
PM
Hi Qin,
Please see my responses below:
On Thursday 02 October 2003 9:12 am, Qin Ding wrote:
> David:
> I see what you did. However, what I try to achieve is different. After
the
> scanner picks up the file, I believe that original file is wrapped up
into
> babeldoc's internal document. Now all I want to do is to get that file
out
> from the document wrapper so that I can pass it to my validation routine.
> The question I have is:
>
> Do you have a method like this:
> document.getFile("file_name") which should return java.io.File
>
Nope. The best you can do is take document.get("file_name"), which will
return the file name as a String, and use it to instantiate your own File
class.
> I saw babeldoc has a method: document.getInputStream(). Does this
> inputStream represent the original file?
>
I haven't used this one, but I'm guessing that it represents the internal
document. If you haven't changed the original document through some type
of
transformation, then it should represent the original file.
> Why when I do the following (pass the file name and file's Inputstream to
> my validation routine), I got TestManager not defined error? The class is
> in %babeldoc_home%/lib directory?
>
> initialize.script=\
> longlegs.core.filevalidation.TestManager.validate(document.get
> ("file_name"),\ document.getInputStream());\
>
Is validate() a static method? If not, you'll need to instantiate the
TestManager class first. Also, I'm not sure if simply placing the class
into
the %babeldoc_home%/lib directory is sufficient. You may need to put it
into
the CLASSPATH, as well. Perhaps Bruce can comment on this?
> May I give you a call? I guess I am not very good to make myself
> understood in writing. I appreciated it very much.
>
I'm happy to talk to you, however I'm leaving the office for most of the
day
in a minute. You may want to consider an alternative way to get this going
for now:
1. Create a batch file that you can run from the command line, passing the
name of a file, that will run your validation routine.
2. Use the ExternalApplication stage to run your batch file. Be sure to
set
the pipeInResponse attribute to true.
3. The output of the external program will placed in an attribute called
ExternalApplicationResponse. From there, you can place it into the main
document, test it, slice it, dice it, etc.
Hope this helps. If not, I'll be available later this evening or tomorrow.
David
> 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"
> <qd...@cs...> @cox.net> cc:
> bab...@li... Subject: Re: [Babeldoc-devel] Re:
> [Babeldoc-user] 10/02/03 10:59 Questions. Please Help AM
>
>
>
>
>
>
> Oops! I told an untruth. You CAN use imports in Javascript, as you've
> done.
> Remember this when you trust what I say... :-)
>
> David
>
> On Thursday 02 October 2003 8:50 am, David Glick wrote:
> > Hi Qin,
> >
> > Here's a stage that I use to load values from a properties file. You
> > should be able to do something similar in your case:
> >
> > ######
> > # Get the next document ID
> > ######
> > get-next-doc-id.stageType=Scripting
> > get-next-doc-id.nextStage=perl-post-doc
> > get-next-doc-id.failOnError=true
> > get-next-doc-id.language=javascript
> > get-next-doc-id.script=\
> > var document_id;\
> > var propertiesFile = new
> > java.io.File(${document.get("merchant_properties")});\
> > var properties = new java.util.Properties();\
> > if (propertiesFile.exists()) {properties.load(new
> > java.io.FileInputStream(propertiesFile));}\
> > document_id = properties.getProperty("next_document_id", "10001");\
> > document_id++;\
> > properties.setProperty("next_document_id", document_id);\
> > properties.store(new
java.io.FileOutputStream(propertiesFile),null);\
> > document.put("document_id", document_id);
> >
> > Note that you cannot import in Javascript. This is why you have to use
>
> the
>
> > fully-qualified class name.
> >
> >
> > Hope this helps,
> >
> > David
> >
> > On Thursday 02 October 2003 8:19 am, Qin Ding wrote:
> > > David, Good morning:
> > >
> > > I checked the scripting examples. I did not see any examples that
>
> shows
>
> > > how I can extract the original file as type java.io.File. The closest
>
> one
>
> > > is md5 example, which shows how to get Inputstream out of the
document.
>
> I
>
> > > assume this is the inputstream of the original file. So, I changed my
> > > script like this:
> > > initialize.script=\
> > > importClass(Packages.longlegs.core.filevalidation.TestManager);\
> > > TestManager.validate(document.get("file_name"),
> > > document.getInputStream());\
> > >
> > > I deployed my file validation jar into babeldoc/lib directory, of
>
> course.
>
> > > When I ran the pipeline, I got this error stating my TestManager is
not
> > > defined.
> > >
> > > <2003-10-02 09:57:37,517> INFO [main] : PipelineStage name:
>
> initialize
>
> > > <2003-10-02 09:57:37,978> ERROR [main] :
> > > [DefaultPipelineStageErrorHandler.handlePipelineStageError]
>
> PipelineStage
>
> > > name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
> > > Script processing failed
> > > <2003-10-02 09:57:37,978> ERROR [main] : [PipelineFeeder.process]
> > > com.babeldoc.core.pipeline.PipelineException: Script processing
failed
> > > at
> > >
com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> > > Source)
> > > at
com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> > > Source)
> > > at
>
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPi
>
> > >pe lineStage(Unknown Source)
> > > at
>
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(U
>
> > >nk nown Source)
> > > at
>
> com.babeldoc.core.pipeline.PipelineStageFactory.process(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(DelegatingMethodAccessorI
>
> > >mp 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(DelegatingMethodAccessorI
>
> > >mp 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)
> > > Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal
>
> Error:
> > > ReferenceError: "TestManager" is not defined.
> > > at
> > >
org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> > > Source)
> > > at
>
> org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
>
> > > Source)
> > > at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> > > at org.apache.bsf.BSFManager$6.run(Unknown Source)
> > > at java.security.AccessController.doPrivileged(Native Method)
> > > at org.apache.bsf.BSFManager.exec(Unknown Source)
> > > ... 27 more
>
> -------------------------------------------------------------------------
>
> > >-- -------------
> > >
> > > 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
-------------------------------------------------------
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
|
|
From: Qin D. <qd...@cs...> - 2003-10-02 17:22:51
|
Thank, David. I'll talk to you tomorrow.
Yes, the validate(String fileName, InputStream is) in TestManager is static
method.
Bruce: What should I do in order for my jar visible to the scripting code.
Right now, I just drop it into %BABELDOC_HOME%/lib directory along with all
the jars that BabelDoc depends on.
David, I don't follow what you said about batch file and
externalApplication Stage. I'll try to see if there are some examples and
talk to you later. Thank you.
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" <qd...@cs...>
@cox.net> cc: bab...@li...
Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user]
10/02/03 12:06 Questions. Please Help
PM
Hi Qin,
Please see my responses below:
On Thursday 02 October 2003 9:12 am, Qin Ding wrote:
> David:
> I see what you did. However, what I try to achieve is different. After
the
> scanner picks up the file, I believe that original file is wrapped up
into
> babeldoc's internal document. Now all I want to do is to get that file
out
> from the document wrapper so that I can pass it to my validation routine.
> The question I have is:
>
> Do you have a method like this:
> document.getFile("file_name") which should return java.io.File
>
Nope. The best you can do is take document.get("file_name"), which will
return the file name as a String, and use it to instantiate your own File
class.
> I saw babeldoc has a method: document.getInputStream(). Does this
> inputStream represent the original file?
>
I haven't used this one, but I'm guessing that it represents the internal
document. If you haven't changed the original document through some type
of
transformation, then it should represent the original file.
> Why when I do the following (pass the file name and file's Inputstream to
> my validation routine), I got TestManager not defined error? The class is
> in %babeldoc_home%/lib directory?
>
> initialize.script=\
> longlegs.core.filevalidation.TestManager.validate(document.get
> ("file_name"),\ document.getInputStream());\
>
Is validate() a static method? If not, you'll need to instantiate the
TestManager class first. Also, I'm not sure if simply placing the class
into
the %babeldoc_home%/lib directory is sufficient. You may need to put it
into
the CLASSPATH, as well. Perhaps Bruce can comment on this?
> May I give you a call? I guess I am not very good to make myself
> understood in writing. I appreciated it very much.
>
I'm happy to talk to you, however I'm leaving the office for most of the
day
in a minute. You may want to consider an alternative way to get this going
for now:
1. Create a batch file that you can run from the command line, passing the
name of a file, that will run your validation routine.
2. Use the ExternalApplication stage to run your batch file. Be sure to
set
the pipeInResponse attribute to true.
3. The output of the external program will placed in an attribute called
ExternalApplicationResponse. From there, you can place it into the main
document, test it, slice it, dice it, etc.
Hope this helps. If not, I'll be available later this evening or tomorrow.
David
> 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"
> <qd...@cs...> @cox.net> cc:
> bab...@li... Subject: Re: [Babeldoc-devel] Re:
> [Babeldoc-user] 10/02/03 10:59 Questions. Please Help AM
>
>
>
>
>
>
> Oops! I told an untruth. You CAN use imports in Javascript, as you've
> done.
> Remember this when you trust what I say... :-)
>
> David
>
> On Thursday 02 October 2003 8:50 am, David Glick wrote:
> > Hi Qin,
> >
> > Here's a stage that I use to load values from a properties file. You
> > should be able to do something similar in your case:
> >
> > ######
> > # Get the next document ID
> > ######
> > get-next-doc-id.stageType=Scripting
> > get-next-doc-id.nextStage=perl-post-doc
> > get-next-doc-id.failOnError=true
> > get-next-doc-id.language=javascript
> > get-next-doc-id.script=\
> > var document_id;\
> > var propertiesFile = new
> > java.io.File(${document.get("merchant_properties")});\
> > var properties = new java.util.Properties();\
> > if (propertiesFile.exists()) {properties.load(new
> > java.io.FileInputStream(propertiesFile));}\
> > document_id = properties.getProperty("next_document_id", "10001");\
> > document_id++;\
> > properties.setProperty("next_document_id", document_id);\
> > properties.store(new
java.io.FileOutputStream(propertiesFile),null);\
> > document.put("document_id", document_id);
> >
> > Note that you cannot import in Javascript. This is why you have to use
>
> the
>
> > fully-qualified class name.
> >
> >
> > Hope this helps,
> >
> > David
> >
> > On Thursday 02 October 2003 8:19 am, Qin Ding wrote:
> > > David, Good morning:
> > >
> > > I checked the scripting examples. I did not see any examples that
>
> shows
>
> > > how I can extract the original file as type java.io.File. The closest
>
> one
>
> > > is md5 example, which shows how to get Inputstream out of the
document.
>
> I
>
> > > assume this is the inputstream of the original file. So, I changed my
> > > script like this:
> > > initialize.script=\
> > > importClass(Packages.longlegs.core.filevalidation.TestManager);\
> > > TestManager.validate(document.get("file_name"),
> > > document.getInputStream());\
> > >
> > > I deployed my file validation jar into babeldoc/lib directory, of
>
> course.
>
> > > When I ran the pipeline, I got this error stating my TestManager is
not
> > > defined.
> > >
> > > <2003-10-02 09:57:37,517> INFO [main] : PipelineStage name:
>
> initialize
>
> > > <2003-10-02 09:57:37,978> ERROR [main] :
> > > [DefaultPipelineStageErrorHandler.handlePipelineStageError]
>
> PipelineStage
>
> > > name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
> > > Script processing failed
> > > <2003-10-02 09:57:37,978> ERROR [main] : [PipelineFeeder.process]
> > > com.babeldoc.core.pipeline.PipelineException: Script processing
failed
> > > at
> > >
com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> > > Source)
> > > at
com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> > > Source)
> > > at
>
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPi
>
> > >pe lineStage(Unknown Source)
> > > at
>
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(U
>
> > >nk nown Source)
> > > at
>
> com.babeldoc.core.pipeline.PipelineStageFactory.process(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(DelegatingMethodAccessorI
>
> > >mp 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(DelegatingMethodAccessorI
>
> > >mp 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)
> > > Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal
>
> Error:
> > > ReferenceError: "TestManager" is not defined.
> > > at
> > >
org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> > > Source)
> > > at
>
> org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
>
> > > Source)
> > > at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> > > at org.apache.bsf.BSFManager$6.run(Unknown Source)
> > > at java.security.AccessController.doPrivileged(Native Method)
> > > at org.apache.bsf.BSFManager.exec(Unknown Source)
> > > ... 27 more
>
> -------------------------------------------------------------------------
>
> > >-- -------------
> > >
> > > 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: David G. <dg...@co...> - 2003-10-02 17:01:52
|
Hi Qin,
Please see my responses below:
On Thursday 02 October 2003 9:12 am, Qin Ding wrote:
> David:
> I see what you did. However, what I try to achieve is different. After the
> scanner picks up the file, I believe that original file is wrapped up into
> babeldoc's internal document. Now all I want to do is to get that file out
> from the document wrapper so that I can pass it to my validation routine.
> The question I have is:
>
> Do you have a method like this:
> document.getFile("file_name") which should return java.io.File
>
Nope. The best you can do is take document.get("file_name"), which will
return the file name as a String, and use it to instantiate your own File
class.
> I saw babeldoc has a method: document.getInputStream(). Does this
> inputStream represent the original file?
>
I haven't used this one, but I'm guessing that it represents the internal
document. If you haven't changed the original document through some type of
transformation, then it should represent the original file.
> Why when I do the following (pass the file name and file's Inputstream to
> my validation routine), I got TestManager not defined error? The class is
> in %babeldoc_home%/lib directory?
>
> initialize.script=\
> longlegs.core.filevalidation.TestManager.validate(document.get
> ("file_name"),\ document.getInputStream());\
>
Is validate() a static method? If not, you'll need to instantiate the
TestManager class first. Also, I'm not sure if simply placing the class into
the %babeldoc_home%/lib directory is sufficient. You may need to put it into
the CLASSPATH, as well. Perhaps Bruce can comment on this?
> May I give you a call? I guess I am not very good to make myself
> understood in writing. I appreciated it very much.
>
I'm happy to talk to you, however I'm leaving the office for most of the day
in a minute. You may want to consider an alternative way to get this going
for now:
1. Create a batch file that you can run from the command line, passing the
name of a file, that will run your validation routine.
2. Use the ExternalApplication stage to run your batch file. Be sure to set
the pipeInResponse attribute to true.
3. The output of the external program will placed in an attribute called
ExternalApplicationResponse. From there, you can place it into the main
document, test it, slice it, dice it, etc.
Hope this helps. If not, I'll be available later this evening or tomorrow.
David
> 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"
> <qd...@cs...> @cox.net> cc:
> bab...@li... Subject: Re: [Babeldoc-devel] Re:
> [Babeldoc-user] 10/02/03 10:59 Questions. Please Help AM
>
>
>
>
>
>
> Oops! I told an untruth. You CAN use imports in Javascript, as you've
> done.
> Remember this when you trust what I say... :-)
>
> David
>
> On Thursday 02 October 2003 8:50 am, David Glick wrote:
> > Hi Qin,
> >
> > Here's a stage that I use to load values from a properties file. You
> > should be able to do something similar in your case:
> >
> > ######
> > # Get the next document ID
> > ######
> > get-next-doc-id.stageType=Scripting
> > get-next-doc-id.nextStage=perl-post-doc
> > get-next-doc-id.failOnError=true
> > get-next-doc-id.language=javascript
> > get-next-doc-id.script=\
> > var document_id;\
> > var propertiesFile = new
> > java.io.File(${document.get("merchant_properties")});\
> > var properties = new java.util.Properties();\
> > if (propertiesFile.exists()) {properties.load(new
> > java.io.FileInputStream(propertiesFile));}\
> > document_id = properties.getProperty("next_document_id", "10001");\
> > document_id++;\
> > properties.setProperty("next_document_id", document_id);\
> > properties.store(new java.io.FileOutputStream(propertiesFile),null);\
> > document.put("document_id", document_id);
> >
> > Note that you cannot import in Javascript. This is why you have to use
>
> the
>
> > fully-qualified class name.
> >
> >
> > Hope this helps,
> >
> > David
> >
> > On Thursday 02 October 2003 8:19 am, Qin Ding wrote:
> > > David, Good morning:
> > >
> > > I checked the scripting examples. I did not see any examples that
>
> shows
>
> > > how I can extract the original file as type java.io.File. The closest
>
> one
>
> > > is md5 example, which shows how to get Inputstream out of the document.
>
> I
>
> > > assume this is the inputstream of the original file. So, I changed my
> > > script like this:
> > > initialize.script=\
> > > importClass(Packages.longlegs.core.filevalidation.TestManager);\
> > > TestManager.validate(document.get("file_name"),
> > > document.getInputStream());\
> > >
> > > I deployed my file validation jar into babeldoc/lib directory, of
>
> course.
>
> > > When I ran the pipeline, I got this error stating my TestManager is not
> > > defined.
> > >
> > > <2003-10-02 09:57:37,517> INFO [main] : PipelineStage name:
>
> initialize
>
> > > <2003-10-02 09:57:37,978> ERROR [main] :
> > > [DefaultPipelineStageErrorHandler.handlePipelineStageError]
>
> PipelineStage
>
> > > name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
> > > Script processing failed
> > > <2003-10-02 09:57:37,978> ERROR [main] : [PipelineFeeder.process]
> > > com.babeldoc.core.pipeline.PipelineException: Script processing failed
> > > at
> > > com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> > > Source)
> > > at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> > > Source)
> > > at
>
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPi
>
> > >pe lineStage(Unknown Source)
> > > at
>
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(U
>
> > >nk nown Source)
> > > at
>
> com.babeldoc.core.pipeline.PipelineStageFactory.process(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(DelegatingMethodAccessorI
>
> > >mp 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(DelegatingMethodAccessorI
>
> > >mp 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)
> > > Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal
>
> Error:
> > > ReferenceError: "TestManager" is not defined.
> > > at
> > > org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> > > Source)
> > > at
>
> org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
>
> > > Source)
> > > at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> > > at org.apache.bsf.BSFManager$6.run(Unknown Source)
> > > at java.security.AccessController.doPrivileged(Native Method)
> > > at org.apache.bsf.BSFManager.exec(Unknown Source)
> > > ... 27 more
>
> -------------------------------------------------------------------------
>
> > >-- -------------
> > >
> > > 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: Qin D. <qd...@cs...> - 2003-10-02 16:13:35
|
David:
I see what you did. However, what I try to achieve is different. After the
scanner picks up the file, I believe that original file is wrapped up into
babeldoc's internal document. Now all I want to do is to get that file out
from the document wrapper so that I can pass it to my validation routine.
The question I have is:
Do you have a method like this:
document.getFile("file_name") which should return java.io.File
I saw babeldoc has a method: document.getInputStream(). Does this
inputStream represent the original file?
Why when I do the following (pass the file name and file's Inputstream to
my validation routine), I got TestManager not defined error? The class is
in %babeldoc_home%/lib directory?
initialize.script=\
longlegs.core.filevalidation.TestManager.validate(document.get
("file_name"),\ document.getInputStream());\
May I give you a call? I guess I am not very good to make myself
understood in writing. I appreciated it 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.
----------------------------------------------------------------------------------------
David Glick
<dglick To: "Qin Ding" <qd...@cs...>
@cox.net> cc: bab...@li...
Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user]
10/02/03 10:59 Questions. Please Help
AM
Oops! I told an untruth. You CAN use imports in Javascript, as you've
done.
Remember this when you trust what I say... :-)
David
On Thursday 02 October 2003 8:50 am, David Glick wrote:
> Hi Qin,
>
> Here's a stage that I use to load values from a properties file. You
> should be able to do something similar in your case:
>
> ######
> # Get the next document ID
> ######
> get-next-doc-id.stageType=Scripting
> get-next-doc-id.nextStage=perl-post-doc
> get-next-doc-id.failOnError=true
> get-next-doc-id.language=javascript
> get-next-doc-id.script=\
> var document_id;\
> var propertiesFile = new
> java.io.File(${document.get("merchant_properties")});\
> var properties = new java.util.Properties();\
> if (propertiesFile.exists()) {properties.load(new
> java.io.FileInputStream(propertiesFile));}\
> document_id = properties.getProperty("next_document_id", "10001");\
> document_id++;\
> properties.setProperty("next_document_id", document_id);\
> properties.store(new java.io.FileOutputStream(propertiesFile),null);\
> document.put("document_id", document_id);
>
> Note that you cannot import in Javascript. This is why you have to use
the
> fully-qualified class name.
>
>
> Hope this helps,
>
> David
>
> On Thursday 02 October 2003 8:19 am, Qin Ding wrote:
> > David, Good morning:
> >
> > I checked the scripting examples. I did not see any examples that
shows
> > how I can extract the original file as type java.io.File. The closest
one
> > is md5 example, which shows how to get Inputstream out of the document.
I
> > assume this is the inputstream of the original file. So, I changed my
> > script like this:
> > initialize.script=\
> > importClass(Packages.longlegs.core.filevalidation.TestManager);\
> > TestManager.validate(document.get("file_name"),
> > document.getInputStream());\
> >
> > I deployed my file validation jar into babeldoc/lib directory, of
course.
> >
> > When I ran the pipeline, I got this error stating my TestManager is not
> > defined.
> >
> > <2003-10-02 09:57:37,517> INFO [main] : PipelineStage name:
initialize
> > <2003-10-02 09:57:37,978> ERROR [main] :
> > [DefaultPipelineStageErrorHandler.handlePipelineStageError]
PipelineStage
> > name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
> > Script processing failed
> > <2003-10-02 09:57:37,978> ERROR [main] : [PipelineFeeder.process]
> > com.babeldoc.core.pipeline.PipelineException: Script processing failed
> > at
> > com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> > Source)
> > at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> > Source)
> > at
> >
com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPi
> >pe lineStage(Unknown Source)
> > at
> >
com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(U
> >nk nown Source)
> > at
com.babeldoc.core.pipeline.PipelineStageFactory.process(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(DelegatingMethodAccessorI
> >mp 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(DelegatingMethodAccessorI
> >mp 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)
> > Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal
Error:
> > ReferenceError: "TestManager" is not defined.
> > at
> > org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> > Source)
> > at
org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
> > Source)
> > at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> > at org.apache.bsf.BSFManager$6.run(Unknown Source)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at org.apache.bsf.BSFManager.exec(Unknown Source)
> > ... 27 more
> >
> >
> >
-------------------------------------------------------------------------
> >-- -------------
> >
> > 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: David G. <dg...@co...> - 2003-10-02 15:55:19
|
Oops! I told an untruth. You CAN use imports in Javascript, as you've done.
Remember this when you trust what I say... :-)
David
On Thursday 02 October 2003 8:50 am, David Glick wrote:
> Hi Qin,
>
> Here's a stage that I use to load values from a properties file. You
> should be able to do something similar in your case:
>
> ######
> # Get the next document ID
> ######
> get-next-doc-id.stageType=Scripting
> get-next-doc-id.nextStage=perl-post-doc
> get-next-doc-id.failOnError=true
> get-next-doc-id.language=javascript
> get-next-doc-id.script=\
> var document_id;\
> var propertiesFile = new
> java.io.File(${document.get("merchant_properties")});\
> var properties = new java.util.Properties();\
> if (propertiesFile.exists()) {properties.load(new
> java.io.FileInputStream(propertiesFile));}\
> document_id = properties.getProperty("next_document_id", "10001");\
> document_id++;\
> properties.setProperty("next_document_id", document_id);\
> properties.store(new java.io.FileOutputStream(propertiesFile),null);\
> document.put("document_id", document_id);
>
> Note that you cannot import in Javascript. This is why you have to use the
> fully-qualified class name.
>
>
> Hope this helps,
>
> David
>
> On Thursday 02 October 2003 8:19 am, Qin Ding wrote:
> > David, Good morning:
> >
> > I checked the scripting examples. I did not see any examples that shows
> > how I can extract the original file as type java.io.File. The closest one
> > is md5 example, which shows how to get Inputstream out of the document. I
> > assume this is the inputstream of the original file. So, I changed my
> > script like this:
> > initialize.script=\
> > importClass(Packages.longlegs.core.filevalidation.TestManager);\
> > TestManager.validate(document.get("file_name"),
> > document.getInputStream());\
> >
> > I deployed my file validation jar into babeldoc/lib directory, of course.
> >
> > When I ran the pipeline, I got this error stating my TestManager is not
> > defined.
> >
> > <2003-10-02 09:57:37,517> INFO [main] : PipelineStage name: initialize
> > <2003-10-02 09:57:37,978> ERROR [main] :
> > [DefaultPipelineStageErrorHandler.handlePipelineStageError] PipelineStage
> > name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
> > Script processing failed
> > <2003-10-02 09:57:37,978> ERROR [main] : [PipelineFeeder.process]
> > com.babeldoc.core.pipeline.PipelineException: Script processing failed
> > at
> > com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> > Source)
> > at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> > Source)
> > at
> > com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPi
> >pe lineStage(Unknown Source)
> > at
> > com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(U
> >nk nown Source)
> > at com.babeldoc.core.pipeline.PipelineStageFactory.process(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(DelegatingMethodAccessorI
> >mp 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(DelegatingMethodAccessorI
> >mp 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)
> > Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal Error:
> > ReferenceError: "TestManager" is not defined.
> > at
> > org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> > Source)
> > at org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
> > Source)
> > at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> > at org.apache.bsf.BSFManager$6.run(Unknown Source)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at org.apache.bsf.BSFManager.exec(Unknown Source)
> > ... 27 more
> >
> >
> > -------------------------------------------------------------------------
> >-- -------------
> >
> > 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: David G. <dg...@co...> - 2003-10-02 15:46:00
|
Hi Qin,
Here's a stage that I use to load values from a properties file. You should
be able to do something similar in your case:
######
# Get the next document ID
######
get-next-doc-id.stageType=Scripting
get-next-doc-id.nextStage=perl-post-doc
get-next-doc-id.failOnError=true
get-next-doc-id.language=javascript
get-next-doc-id.script=\
var document_id;\
var propertiesFile = new
java.io.File(${document.get("merchant_properties")});\
var properties = new java.util.Properties();\
if (propertiesFile.exists()) {properties.load(new
java.io.FileInputStream(propertiesFile));}\
document_id = properties.getProperty("next_document_id", "10001");\
document_id++;\
properties.setProperty("next_document_id", document_id);\
properties.store(new java.io.FileOutputStream(propertiesFile),null);\
document.put("document_id", document_id);
Note that you cannot import in Javascript. This is why you have to use the
fully-qualified class name.
Hope this helps,
David
On Thursday 02 October 2003 8:19 am, Qin Ding wrote:
> David, Good morning:
>
> I checked the scripting examples. I did not see any examples that shows
> how I can extract the original file as type java.io.File. The closest one
> is md5 example, which shows how to get Inputstream out of the document. I
> assume this is the inputstream of the original file. So, I changed my
> script like this:
> initialize.script=\
> importClass(Packages.longlegs.core.filevalidation.TestManager);\
> TestManager.validate(document.get("file_name"),
> document.getInputStream());\
>
> I deployed my file validation jar into babeldoc/lib directory, of course.
>
> When I ran the pipeline, I got this error stating my TestManager is not
> defined.
>
> <2003-10-02 09:57:37,517> INFO [main] : PipelineStage name: initialize
> <2003-10-02 09:57:37,978> ERROR [main] :
> [DefaultPipelineStageErrorHandler.handlePipelineStageError] PipelineStage
> name: initialize Error: com.babeldoc.core.pipeline.PipelineException:
> Script processing failed
> <2003-10-02 09:57:37,978> ERROR [main] : [PipelineFeeder.process]
> com.babeldoc.core.pipeline.PipelineException: Script processing failed
> at
> com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> Source)
> at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> Source)
> at
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPipe
>lineStage(Unknown Source)
> at
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(Unk
>nown Source)
> at com.babeldoc.core.pipeline.PipelineStageFactory.process(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)
> Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal Error:
> ReferenceError: "TestManager" is not defined.
> at
> org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> Source)
> at org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
> Source)
> at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> at org.apache.bsf.BSFManager$6.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.bsf.BSFManager.exec(Unknown Source)
> ... 27 more
>
>
> ---------------------------------------------------------------------------
>-------------
>
> 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: Dejan K. <dej...@nb...> - 2003-10-02 09:04:18
|
Hi all, Bruce and I yesterday talked on how to make Babeldoc web site better. I think it should be more opened for users who want to contribute by writing new documents, user guides, examples..as well as enhancing existing one. What could help here is adding some Wiki pages that can be edited by users So we need some software (open source of course) to support this. Any ideas? What do you think about coWiki (http://www.develnet.org/) which is used for example on http://www.hibernate.org? There are also http://www.jspwiki.org, http://tikiwiki.org and other What about CMS? In my company we have used OpenCMS so we have some expirience with it. Any other idea? Also if there are interest on having forum I am also developer on mvnForum (www.mvnforum.com) project which is Jsp/Servlet forum software so I can help with it. Bruce, since web site is hosted at your place you are the only person who can tell if this is OK or not. I already said that I could help you with setting up on this but this cannot be done without you. Dejan P.S. I have also talked with web designer from my company and she agreed to help us. Babeldoc already helped her and saved here time with updating website so it is time for pay off ;) |
|
From: Dejan K. <dej...@nb...> - 2003-10-02 07:38:20
|
What about using existing module mechanism but separate core from non-core modules? Maybe we could even split some modules on more pieces. For example, current conversion module contains both flat to xml conversions and conversions from excel to xml files. Now, I guess not all users will need to use both - I think it should be possible to let them choose which modules they want to use.... No need to download all 12 MB or more (Babeldoc is growing every day) if they want to use some simple stages that would need only 2-3 MB! When I am talking about core modules I mean on those modules that are used more frequently and that are used by other modules. IMO we should agree on which parts of Babeldoc should be "core". Not all classes from current core module should remain there. Also, I think some classes from other modules should be packaged into "core" distribution. My idea was to make new SF project wich would contain babeldoc modules. That is - pipeline stages, scanner worker implementations, maybe even journal implementations... The point is that Babeldoc has very basic architecture that could be applied in many different contexts (For example in my company we plan to use Babeldoc for exchanging documents with banks (I work in Central Bank) and we are also using it for updating our website with exchange rates etc..). We already have pipeline stages that does so many different things and there are more and more users with some great ideas asking if we need some piece of code they write. If we create separate SF project we could grant CVS rigths to everyone who has some interesing idea and code. And these "plugins" should be released separately from the core distribution. So when user needs FO conversion he could download FO module with all necessary liraries and classes. Dejan ----- Original Message ----- From: "Bruce McDonald" <br...@mc...> To: <bab...@li...> Sent: Thursday, October 02, 2003 6:08 AM Subject: [Babeldoc-devel] Babeldoc 1.2 Happenings > Hello all! > > Babeldoc 1.2 is coming up. Thank you to all those who made this a great > release. Babeldoc is both deeper and wider in all its areas. Nothing has > been untouched. From multitasking to the new scanner to the modular build. > Things that need work are J2EE, GUI and web (Just as ask Bill Harrelson: > keep talking Bill, we can make this work and get Babeldoc running better). > Thanks to Qin who came with a pipeline configuration that obviously breaks > Babeldoc (Qin's arrangement was that the current working directory contained > the BABELDOC_USER directory with all the configuration files - investigation > is required here - I volunteer, suggestions/patches welcomed). > > Just keep coming with the work - its been great working with you all. > > Dejan and I were talking today about opening up the modules. We recognize > that Babeldoc needs to get bigger than the standard set of modules that it > comes with. The issue is then how to manage the creation of modules (think > plugins going forward). Creating and managing modules should be a simple and > straightforward. This includes how and where Babeldoc module source code > gets stored. Personally I envisage a command that would download or > otherwise locate and retrieve a Babeldoc module for building or running. > (this implies some kind of registry: UDDI?) How are you developing using > Babeldoc and how do you think that we should be developing with Babeldoc in > the future? > > regards, > Bruce. > > > ------------------------------------------------------- > 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 |
|
From: Bruce M. <br...@mc...> - 2003-10-02 04:08:48
|
Hello all! Babeldoc 1.2 is coming up. Thank you to all those who made this a great release. Babeldoc is both deeper and wider in all its areas. Nothing has been untouched. From multitasking to the new scanner to the modular build. Things that need work are J2EE, GUI and web (Just as ask Bill Harrelson: keep talking Bill, we can make this work and get Babeldoc running better). Thanks to Qin who came with a pipeline configuration that obviously breaks Babeldoc (Qin's arrangement was that the current working directory contained the BABELDOC_USER directory with all the configuration files - investigation is required here - I volunteer, suggestions/patches welcomed). Just keep coming with the work - its been great working with you all. Dejan and I were talking today about opening up the modules. We recognize that Babeldoc needs to get bigger than the standard set of modules that it comes with. The issue is then how to manage the creation of modules (think plugins going forward). Creating and managing modules should be a simple and straightforward. This includes how and where Babeldoc module source code gets stored. Personally I envisage a command that would download or otherwise locate and retrieve a Babeldoc module for building or running. (this implies some kind of registry: UDDI?) How are you developing using Babeldoc and how do you think that we should be developing with Babeldoc in the future? regards, Bruce. |
|
From: Bruce M. <br...@mc...> - 2003-10-02 03:37:58
|
Ok, Someone has an issue here. Don't know who relies on this email address (looks kinda bogus to me) but its bouncing. You need to do some work on this. Maybe some worm message - dont know - I use Linux and its not affecting KMail. regards, Bruce. |
|
From: McDonald, B. <Bru...@ba...> - 2003-10-02 02:21:44
|
Its just the name of the file.
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Wednesday, October 01, 2003 4:01 PM
To: McDonald, Bruce
Cc: Babeldoc Developer List; David Glick
Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
Bruce and David:
Now I am in business thanks to both of you very much.
initialize.script=\
java.lang.System.out.println(document.get("file_name"));\
java.io.File file = new java.io.File(document.get("file_name"));\
TestManager.validate(file);\
When I call document.get("file_name"), I get just a string name of the
document. Is it true? Does this name reference to the original document
that I passed in via -f Aftermarket.dat? Seems to me it is just a name but
no reference to the file.
Do we have something like this:
java.io.File file = document.getFile(document.get("file_name"));
So I can pass that File into my validation routine. Please advise. 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.
----------------------------------------------------------------------------------------
"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
1. Download babeldoc 1.2.0-RC1 into the directory c:\babeldoc (or
somewhere)
2. Set your BABELDOC_HOME= ... this directory
3. echo %BABELDOC_HOME% - make sure that this is correct.
4. cd %BABELDOC_HOME% - you should be in the babeldoc directory.
5. run this: bin\babeldoc - you should see babeldoc version
6. run this: bin\babeldoc process -p test -f test/quickstart/stats.xml
7. Check the file: stats.html
8. run this: bin\babeldoc process -p documentation
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
|
|
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
|
|
From: McDonald, B. <Bru...@ba...> - 2003-10-01 20:43:56
|
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
|
|
From: David G. <dg...@co...> - 2003-10-01 20:38:43
|
You're assignment statements won't work. Don't forget that a script stage
uses Javascript, not Java. You'll need to use something like:
var fileName = document.get("file_name");\
etc.
If you're not familiar with Javascript, you may want to look through some of
the examples in Babeldoc. They do some pretty cool things!
David
On Wednesday 01 October 2003 1:28 pm, Qin Ding wrote:
> David: Thank you. The problem is BABELDOC_USER has to point to the root
> directory c:\qin (not c:\qin\config). Bruce asked me to move all the
> subdirectores under config to c:\qin. Everything runs smoothly like water.
>
> Now, David:
>
> Is there a way to get original file out? Something like this:
>
> String fileName = document.get("file_name");\
> File file = document.getFile(fileName);\
>
> So, I can call my Testmanager.validate(file); I want the original file
> document out and then pass it to my routin. How do you do that? Please
> advise.
>
> By the way, when I run the following script:
> initialize.script=\
> java.io.File file = new java.io.File(fileName);\
>
> I got this error:
>
> <2003-10-01 15:10:37,683> ERROR [main] : [PipelineFeeder.process]
> com.babeldoc.core.pipeline.PipelineException: Script processing failed
> at
> com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
> Source)
> at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
> Source)
> at
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPipe
>lineStage(Unknown Source)
> at
> com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(Unk
>nown Source)
> at com.babeldoc.core.pipeline.PipelineStageFactory.process(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)
> Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal Error:
> SyntaxError: missing ; before statement (<BABELDOC>; )
> at
> org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
> Source)
> at org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
> Source)
> at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
> at org.apache.bsf.BSFManager$6.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.apache.bsf.BSFManager.exec(Unknown Source)
> ... 27 more
>
>
>
> ---------------------------------------------------------------------------
>-------------
>
> 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
> 10/01/03 03:24 <bab...@li...> PM
> Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions.
> Please Help
>
>
>
>
>
> Hi Qin,
>
> Congratulations on getting up! What was the problem with the c:\qin
> directory?
>
> Regarding your question, I'm not sure I understand what you're asking. The
>
> document.get("file_name") returns the name of the document as passed on the
>
> command line with the -f parameter. I assume it also is the name of the
> file
> found by the scanner, but I don't use it this way so I can't say for sure.
>
> The initialize.script stage in your example looks like it will properly
> instantiate the File class for you. Is it not working?
>
>
> David
>
> On Wednesday 01 October 2003 1:01 pm, Qin Ding wrote:
> > Bruce and David:
> >
> > Now I am in business thanks to both of you very much.
> >
> > initialize.script=\
> > java.lang.System.out.println(document.get("file_name"));\
> > java.io.File file = new java.io.File(document.get("file_name"));\
> > TestManager.validate(file);\
> >
> > When I call document.get("file_name"), I get just a string name of the
> > document. Is it true? Does this name reference to the original document
> > that I passed in via -f Aftermarket.dat? Seems to me it is just a name
>
> but
>
> > no reference to the file.
> >
> > Do we have something like this:
> > java.io.File file = document.getFile(document.get("file_name"));
> >
> > So I can pass that File into my validation routine. Please advise.
>
> 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.
>
> ---------------------------------------------------------------------------
>
> >-------------
> >
> >
> >
> >
> >
> > "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
>
> > 1. Download babeldoc 1.2.0-RC1 into the directory c:\babeldoc (or
> > somewhere)
> > 2. Set your BABELDOC_HOME= ... this directory
> > 3. echo %BABELDOC_HOME% - make sure that this is correct.
> > 4. cd %BABELDOC_HOME% - you should be in the babeldoc directory.
> > 5. run this: bin\babeldoc - you should see babeldoc version
> > 6. run this: bin\babeldoc process -p test -f test/quickstart/stats.xml
> > 7. Check the file: stats.html
> > 8. run this: bin\babeldoc process -p documentation
> >
> > 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: Qin D. <qd...@cs...> - 2003-10-01 20:30:22
|
David: Thank you. The problem is BABELDOC_USER has to point to the root
directory c:\qin (not c:\qin\config). Bruce asked me to move all the
subdirectores under config to c:\qin. Everything runs smoothly like water.
Now, David:
Is there a way to get original file out? Something like this:
String fileName = document.get("file_name");\
File file = document.getFile(fileName);\
So, I can call my Testmanager.validate(file); I want the original file
document out and then pass it to my routin. How do you do that? Please
advise.
By the way, when I run the following script:
initialize.script=\
java.io.File file = new java.io.File(fileName);\
I got this error:
<2003-10-01 15:10:37,683> ERROR [main] : [PipelineFeeder.process]
com.babeldoc.core.pipeline.PipelineException: Script processing failed
at
com.babeldoc.core.pipeline.stage.ScriptingPipelineStage.process(Unknown
Source)
at com.babeldoc.core.pipeline.PipelineStage.processStage(Unknown
Source)
at
com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.processPipelineStage(Unknown
Source)
at
com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor.process(Unknown
Source)
at com.babeldoc.core.pipeline.PipelineStageFactory.process(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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)
Caused by: org.apache.bsf.BSFException: JavaScript Error: Internal Error:
SyntaxError: missing ; before statement (<BABELDOC>; )
at
org.apache.bsf.engines.javascript.JavaScriptEngine.handleError(Unknown
Source)
at org.apache.bsf.engines.javascript.JavaScriptEngine.eval(Unknown
Source)
at org.apache.bsf.util.BSFEngineImpl.exec(Unknown Source)
at org.apache.bsf.BSFManager$6.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.bsf.BSFManager.exec(Unknown Source)
... 27 more
----------------------------------------------------------------------------------------
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
10/01/03 03:24 <bab...@li...>
PM Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user]
Questions. Please Help
Hi Qin,
Congratulations on getting up! What was the problem with the c:\qin
directory?
Regarding your question, I'm not sure I understand what you're asking. The
document.get("file_name") returns the name of the document as passed on the
command line with the -f parameter. I assume it also is the name of the
file
found by the scanner, but I don't use it this way so I can't say for sure.
The initialize.script stage in your example looks like it will properly
instantiate the File class for you. Is it not working?
David
On Wednesday 01 October 2003 1:01 pm, Qin Ding wrote:
> Bruce and David:
>
> Now I am in business thanks to both of you very much.
>
> initialize.script=\
> java.lang.System.out.println(document.get("file_name"));\
> java.io.File file = new java.io.File(document.get("file_name"));\
> TestManager.validate(file);\
>
> When I call document.get("file_name"), I get just a string name of the
> document. Is it true? Does this name reference to the original document
> that I passed in via -f Aftermarket.dat? Seems to me it is just a name
but
> no reference to the file.
>
> Do we have something like this:
> java.io.File file = document.getFile(document.get("file_name"));
>
> So I can pass that File into my validation routine. Please advise.
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.
>
---------------------------------------------------------------------------
>-------------
>
>
>
>
>
> "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
> 1. Download babeldoc 1.2.0-RC1 into the directory c:\babeldoc (or
> somewhere)
> 2. Set your BABELDOC_HOME= ... this directory
> 3. echo %BABELDOC_HOME% - make sure that this is correct.
> 4. cd %BABELDOC_HOME% - you should be in the babeldoc directory.
> 5. run this: bin\babeldoc - you should see babeldoc version
> 6. run this: bin\babeldoc process -p test -f test/quickstart/stats.xml
> 7. Check the file: stats.html
> 8. run this: bin\babeldoc process -p documentation
>
> 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
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: McDonald, B. <Bru...@ba...> - 2003-10-01 20:28:04
|
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)
3. cd %BABELDOC_USER% (confirm this)
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.
8. Now list the pipeline stages: "babeldoc pipeline -L 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
|
|
From: McDonald, B. <Bru...@ba...> - 2003-10-01 20:28:00
|
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
1. Download babeldoc 1.2.0-RC1 into the directory c:\babeldoc (or somewhere)
2. Set your BABELDOC_HOME= ... this directory
3. echo %BABELDOC_HOME% - make sure that this is correct.
4. cd %BABELDOC_HOME% - you should be in the babeldoc directory.
5. run this: bin\babeldoc - you should see babeldoc version
6. run this: bin\babeldoc process -p test -f test/quickstart/stats.xml
7. Check the file: stats.html
8. run this: bin\babeldoc process -p documentation
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
|
|
From: McDonald, B. <Bru...@ba...> - 2003-10-01 20:27:54
|
I use it on windows, linux, aix.
-----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
|
2 messages has been excluded from this view by a project administrator.
