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-08 19:42:04
|
Hi, Dejan, Why was this stuff not carried from 1.0 into 1.2? I'd like to have a go at reimplementing it, but I need to know if it's just a case of reimplementing the functionality as it stands in 1.0, or changing it to accomodate some or other requirement. Cheers... MikeA On Wed, 2003-10-08 at 15:44, Dejan Krsmanovic wrote: > Not that these methods I mentioned are currently not in ScannerWorker. > Please check 1.0 branch to see how is that working. I am also hoping that > David will modify his implementation to be compatible with 1.0 release! > > Dejan > ----- Original Message ----- > From: "Michael Ansley" <mic...@ze...> > To: "Babeldoc Developer List" <bab...@li...> > Sent: Wednesday, October 08, 2003 4:41 PM > Subject: Re: [Babeldoc-devel] Scanners and filters... > > > > Hi, Dejan, > > > > I'll get the mailbox scanner done over the next day or two. Just need > > to look at how the ScannerWorker does things. > > > > Cheers... > > > > > > MikeA > > > > PS: Anybody know how to get around Sourceforge's "end of file" cvs > > problem? I seem to be getting it all the time at the moment. > > > > > > On Wed, 2003-10-08 at 15:13, Dejan Krsmanovic wrote: > > > Michael, David, all, > > > since I have discovered that some parts of code that existed in 1.0 > version > > > of Babeldoc I cannot apply your patches right now. The problem is that > > > mailscanner should use some methods from scanner worker class - that > is - > > > methods for storing filters and checking if some entry can matches given > > > filter. > > > > > > Now, David could you check CVS branch 1_0 to see how it was implemented > in > > > 1.0 and see if it you can implement it like that? The idea is that you > > > should have different filters. For example in MailScanner there could be > > > filters for subject, e-mail address etc, etc. I see that your > implementation > > > use the list of filters to check if some entry could be accepted. It is > OK > > > to have more than one filter but you should also be able to make > difference > > > between them... > > > > > > Michael I can apply you patch, but what I would like to see is that > > > MailboxScanner uses methods from Scanner worker (addFilter in intialize > and > > > acceptEntry(filterName) in doScan method). > > > > > > I could do this by myself but currenty I am pretty bussy with other > > > (non-babeldoc) stuff so I am not sure when I can do it... > > > > > > > > > Thanks, > > > Dejan > > > > > > > > > > > > > > > ------------------------------------------------------- > > > 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 > > > > > ------------------------------------------------------- > 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-08 15:10:41
|
Bruce: I guess I have to wait until you release the the patch. From here, I could not connect to cvs.sourceforge.net from here within the fire wall of the company. How soon do you think the latest code in cvs can be released? 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, David Glick <dg...@co...> <Bruce.McDonald cc: bab...@li... @bankofamerica.c Subject: RE: [Babeldoc-devel] Re: [Babeldoc-user] om> Questions. Please Help 10/07/03 03:28 PM 1. Use the code in CVS. 2. Use the dummy journal: Create journal/config.properties - with single line: journalType=dummy -----Original Message----- From: Qin Ding [mailto:qd...@cs...] Sent: Tuesday, October 07, 2003 3:38 PM To: David Glick Cc: bab...@li... Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help David and Bruce: Let me report back to you all I have done to try to solve the Velocity issue. I modified the my validation routine to use VelocityEngine instead of Velocity. That way, I can start a new instance of Velocity. Now, my velocity works, although it still has hard time to find the resource file (vm file). Right now, I just hard coded the vm file. I run command line, as you see it works: C:\DADDY-~1>babeldoc process -p validation-pipeline -f c: \daddy-longlegs\Aftermarket.dat <2003-10-07 14:19:18,307> INFO [main] : PipelineStage name: initialize 2003-10-07 14:19:19,469|INFO |filevalidation.TestManager|Start processing Aftermarket 2003-10-07 14:19:19,729|INFO |filevalidation.TestManager|Processed Aftermarket[24 rows] in 0 second(s) Please help me with the following two questions: 1. But when I use the scanner to run the same file, I got this error. Basically, when document.get("file_name") failed. It returns null value. I remembered that Bruce mentioned that he just fixed this problem. Can I download the patch? Or what should I do to fix it myself for the time being? 2. I remember I have asked this question: What should I do with those ever-growing folders under %BABELDOC_HOME%. Is there a way to purge them if necessary? What would happen if I manually remove them? I just want to know how to manage the filesystem which seems growing very fast. These are the errors when running scanner: 2003-10-07 14:24:04,248|ERROR|filevalidation.TestManager|AD0028771065554644248:longlegs.core.filevalidation.utils.FileValidationException: java.lang.Exception: null is null value at longlegs.core.filevalidation.utils.ExceptionUtil.createFileValidationException(Unknown Source) at longlegs.core.filevalidation.TestManager.validate(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 org.mozilla.javascript.NativeJavaMethod.call(Unknown Source) at org.mozilla.javascript.ScriptRuntime.call(Unknown Source) at org.mozilla.javascript.gen.c1.call(Unknown Source) at org.mozilla.javascript.gen.c1.exec(Unknown Source) at org.mozilla.javascript.Context.evaluateReader(Unknown Source) at org.mozilla.javascript.Context.evaluateString(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) 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.AsynchronousFeeder.actuallyProcess(Unknown Source) at com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown Source) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:536) Caused by: java.lang.Exception: null is null value ... 28 more 2003-10-07 14:24:04,289|ERROR|pipeline.DefaultPipelineStageErrorHandler|[DefaultPipelineStageErrorHandler.handlePipelineStageError] PipelineStage name: initialize Error: com.babeldoc.core.pipeline.PipelineException: Script processing failed2003-10-07 14:24:04,299|ERROR|feeder.AsynchronousFeeder|[AsynchronousFeeder$1.run] 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.AsynchronousFeeder.actuallyProcess(Unknown Source) at com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown Source) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:536) Caused by: org.apache.bsf.BSFException: JavaScript Error: longlegs.core.filevalidation.utils.FileValidationException: java.lang.Exception: null is null value 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) ... 12 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: Dejan K. <dej...@nb...> - 2003-10-08 14:44:58
|
Not that these methods I mentioned are currently not in ScannerWorker. Please check 1.0 branch to see how is that working. I am also hoping that David will modify his implementation to be compatible with 1.0 release! Dejan ----- Original Message ----- From: "Michael Ansley" <mic...@ze...> To: "Babeldoc Developer List" <bab...@li...> Sent: Wednesday, October 08, 2003 4:41 PM Subject: Re: [Babeldoc-devel] Scanners and filters... > Hi, Dejan, > > I'll get the mailbox scanner done over the next day or two. Just need > to look at how the ScannerWorker does things. > > Cheers... > > > MikeA > > PS: Anybody know how to get around Sourceforge's "end of file" cvs > problem? I seem to be getting it all the time at the moment. > > > On Wed, 2003-10-08 at 15:13, Dejan Krsmanovic wrote: > > Michael, David, all, > > since I have discovered that some parts of code that existed in 1.0 version > > of Babeldoc I cannot apply your patches right now. The problem is that > > mailscanner should use some methods from scanner worker class - that is - > > methods for storing filters and checking if some entry can matches given > > filter. > > > > Now, David could you check CVS branch 1_0 to see how it was implemented in > > 1.0 and see if it you can implement it like that? The idea is that you > > should have different filters. For example in MailScanner there could be > > filters for subject, e-mail address etc, etc. I see that your implementation > > use the list of filters to check if some entry could be accepted. It is OK > > to have more than one filter but you should also be able to make difference > > between them... > > > > Michael I can apply you patch, but what I would like to see is that > > MailboxScanner uses methods from Scanner worker (addFilter in intialize and > > acceptEntry(filterName) in doScan method). > > > > I could do this by myself but currenty I am pretty bussy with other > > (non-babeldoc) stuff so I am not sure when I can do it... > > > > > > Thanks, > > Dejan > > > > > > > > > > ------------------------------------------------------- > > 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: Michael A. <mic...@ze...> - 2003-10-08 14:41:11
|
Hi, Dejan, I'll get the mailbox scanner done over the next day or two. Just need to look at how the ScannerWorker does things. Cheers... MikeA PS: Anybody know how to get around Sourceforge's "end of file" cvs problem? I seem to be getting it all the time at the moment. On Wed, 2003-10-08 at 15:13, Dejan Krsmanovic wrote: > Michael, David, all, > since I have discovered that some parts of code that existed in 1.0 version > of Babeldoc I cannot apply your patches right now. The problem is that > mailscanner should use some methods from scanner worker class - that is - > methods for storing filters and checking if some entry can matches given > filter. > > Now, David could you check CVS branch 1_0 to see how it was implemented in > 1.0 and see if it you can implement it like that? The idea is that you > should have different filters. For example in MailScanner there could be > filters for subject, e-mail address etc, etc. I see that your implementation > use the list of filters to check if some entry could be accepted. It is OK > to have more than one filter but you should also be able to make difference > between them... > > Michael I can apply you patch, but what I would like to see is that > MailboxScanner uses methods from Scanner worker (addFilter in intialize and > acceptEntry(filterName) in doScan method). > > I could do this by myself but currenty I am pretty bussy with other > (non-babeldoc) stuff so I am not sure when I can do it... > > > Thanks, > Dejan > > > > > ------------------------------------------------------- > 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: Dejan K. <dej...@nb...> - 2003-10-08 14:14:33
|
Michael, David, all, since I have discovered that some parts of code that existed in 1.0 version of Babeldoc I cannot apply your patches right now. The problem is that mailscanner should use some methods from scanner worker class - that is - methods for storing filters and checking if some entry can matches given filter. Now, David could you check CVS branch 1_0 to see how it was implemented in 1.0 and see if it you can implement it like that? The idea is that you should have different filters. For example in MailScanner there could be filters for subject, e-mail address etc, etc. I see that your implementation use the list of filters to check if some entry could be accepted. It is OK to have more than one filter but you should also be able to make difference between them... Michael I can apply you patch, but what I would like to see is that MailboxScanner uses methods from Scanner worker (addFilter in intialize and acceptEntry(filterName) in doScan method). I could do this by myself but currenty I am pretty bussy with other (non-babeldoc) stuff so I am not sure when I can do it... Thanks, Dejan |
|
From: David K. <dav...@al...> - 2003-10-08 14:03:51
|
Dejan Krsmanovic wrote: > Hi David, Hi Dejan! > I have just realized that filtering is not implemented > in new scanner version. It was implemented in 1.0 > release but since I have rewrote whole scanner for 1.1 > I obivioulsy forgot to implement it. > Have you checked if your code looks like code in 1.0? I'm afraid not. I had no clue this was present earlier, so I just went ahead and did it. Wasn't much code, anyway... > I will review your code as soon as possible. And > don't worry, mine implementation has also required 1.4 > since it used java.util.regex package. There are some > other pieces of Babeldoc that require it... Ok, that's good to know for future work. > Dejan > P.S. Are you sure you don't want to become commiter? Heh, yeah, for the time being. But don't close the door. (You fixed the filename problem in the scanner, I see. Good, then I can scrap my own fix that I just did for it. :-) ) Regards, David |
|
From: David K. <dav...@al...> - 2003-10-08 14:02:57
|
Hi Bruce! McDonald, Bruce wrote: > What about your threading issues? Unresolved, I'm afraid. Because of current deadlines I'm forced to run single-threaded for a little while, until I can return to that particular issue. I have read quite a lot of the code but am unable to find the culprit. I have seen some other peculiar behaviors related to multithreaded execution as well, though. E.g sometimes multiple instances of PipelineStageFactory and/or PipelineStageResolver are created, depending on timing issues. Those can be resolved through some synchronizing in selected spots, but they do point me to believe that there might be more fundamental issues related to multithreaded execution within Babeldoc that may require more minds peering inside the code. Other than that, I'm happy! ;-) I have one small additional change to the DirectoryScanner that I needed for my current work: In a late pipeline stage I need to know where the scanner moved the original scanned file, in order to move a different, but related, file to the same location. The change consists of a document attribute, called "done_dir" which is set by the DirectoryScanner at the same time as the scan_path and file_name attributes. If this change is useful I can submit a patch for that too? I did one more thing, but I just saw that Dejan fixed it: The file_name problem in the scanner. He beat me to it! :-) /David |
|
From: Michael A. <mic...@ze...> - 2003-10-08 13:54:42
|
OK, so for all of you that chewed glass while going through my original patch, apologies for the coding, it was pretty crap. I have cleaned it up, and will post a patch just as soon as Sourceforge cvs stops giving me "end of file" messages. Still light on javadoc, but much easier to read. Cheers... MikeA |
|
From: <de...@us...> - 2003-10-08 13:39:14
|
Update of /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker
In directory sc8-pr-cvs1:/tmp/cvs-serv27801/modules/scanner/src/com/babeldoc/scanner/worker
Modified Files:
DirectoryScanner.java
Log Message:
Fixed filename problem
Index: DirectoryScanner.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/DirectoryScanner.java,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -d -r1.23 -r1.24
*** DirectoryScanner.java 3 Oct 2003 13:08:40 -0000 1.23
--- DirectoryScanner.java 8 Oct 2003 13:39:07 -0000 1.24
***************
*** 305,309 ****
PipelineDocument.getMimeTypeForFile(file.getName())),
new NameValuePair(SCAN_DATE_KEY, Long.toString(modified)),
! new NameValuePair(SCAN_PATH_KEY, file.getCanonicalPath())});
} finally {
fis.close();
--- 305,310 ----
PipelineDocument.getMimeTypeForFile(file.getName())),
new NameValuePair(SCAN_DATE_KEY, Long.toString(modified)),
! new NameValuePair(SCAN_PATH_KEY, file.getCanonicalPath()),
! new NameValuePair(FILE_NAME_KEY, file.getName())});
} finally {
fis.close();
|
|
From: Dejan K. <dej...@ya...> - 2003-10-08 13:19:13
|
Hi David,
I have just realized that filtering is not implemented
in new scanner version. It was implemented in 1.0
release but since I have rewrote whole scanner for 1.1
I obivioulsy forgot to implement it.
Have you checked if your code looks like code in 1.0?
I will review your code as soon as possible. And
don't worry, mine implementation has also required 1.4
since it used java.util.regex package. There are some
other pieces of Babeldoc that require it...
Dejan
P.S. Are you sure you don't want to become commiter?
--- David Kinnvall <dav...@al...> wrote:
> Hi people,
>
> I noticed that the filtering in DirectoryScanner,
> and the
> underlying ScannerWorker, was not actually
> implemented, and
> since I needed it I added some code that seems to
> work:
>
> ScannerWorker:
> - Added a private List of filters
> - Did the TODO in addFilter to feed the above List
> - Added a private method checkFilter(filter, string)
> - Added code to acceptEntry that checks the supplied
> string against the supplied filter and any already
> configured filters in the above List
>
> DirectoryScanner:
> - Added a private String for the (configured) filter
> - Added code to get the filter string if configured
> - Added code to acceptFile to use the configured
> filter
> and actually do some filtering using the code now
> in
> ScannerWorker
> .
> If filters are present, the string matches if it
> matches
> The logic is: If no filter is specified and no
> filters
> are present in the List, the string matches,
> regardless
> any of the filters. If a filter is also supplied in
> the
> method call, that filter is also checked, but only
> if it
> is not already present in the List.
>
> I have tested all changes and they seem to work, and
> they
> are fully backwards compatible, i.e no changes need
> to be
> done to existing configurations - they work as
> before.
>
> Example configuration snippet for a
> DirectoryScanner:
>
> <scanner-name>.filter=.*\.xml
>
> The above filter (obviously) matches files named
> *.xml and
> nothing else. It uses the regular expression support
> in the
> String class. So that might require 1.4-level Java
> support?
>
> Patch attached. Please review, and apply if correct
> && useful.
>
> Regards,
>
> David Kinnvall
> > Index: com/babeldoc/scanner/ScannerWorker.java
>
===================================================================
> RCS file:
>
/cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/ScannerWorker.java,v
> retrieving revision 1.27
> diff -u -r1.27 ScannerWorker.java
> --- com/babeldoc/scanner/ScannerWorker.java 30 Sep
> 2003 14:37:21 -0000 1.27
> +++ com/babeldoc/scanner/ScannerWorker.java 8 Oct
> 2003 09:54:26 -0000
> @@ -65,6 +65,9 @@
> */
> package com.babeldoc.scanner;
>
> +import java.util.ArrayList;
> +import java.util.Iterator;
> +import java.util.List;
> import java.util.Map;
> import java.util.HashMap;
>
> @@ -114,6 +117,18 @@
> /** must the documents be submitted as binaries
> */
> private boolean binary;
>
> + /** List of filters to apply to document names.
> + * If there are any filters at least one must
> + * match for each document to be processed. If
> + * no filters are present every document will
> + * be processed. Note: An additional filter can
> + * also be provided manually through the method
> + * acceptEntry, and that filter, if specified,
> + * will be check in addition to the configured
> + * ones.
> + */
> + private List filters = new ArrayList();
> +
> public static final String SCANNER_KEY =
> "scanner";
> public static final String SCAN_DATE_KEY =
> "scan_date";
> public static final String SCAN_PATH_KEY =
> "scan_path";
> @@ -214,7 +229,11 @@
> }
>
> /**
> - * Does this worker accept this entry
> + * Does this worker accept this entry? The string
> + * is matched against the specified filter as
> well
> + * as against any already configured filters. The
> + * matching will result in true if any match is
> + * found or if there are no filters.
> *
> * @param filter filter string
> * @param string name to be filtered
> @@ -222,16 +241,63 @@
> * @return true if accepted - false otherwise
> */
> public boolean acceptEntry(String filter, String
> string) {
> - return true;
> + if(filters.isEmpty() && (filter == null ||
> filter == "")) {
> + return true;
> + } else {
> + if(!filters.isEmpty()) {
> + Iterator i = filters.iterator();
> + while(i.hasNext()) {
> + if(checkFilter((String)i.next(),
> string)) {
> + return true;
> + }
> + }
> + }
> + if(filter != null && filter != "") {
> + // Don't check filter again, if it's in
> filters.
> + if(filters.isEmpty() ||
> !filters.contains(filter)) {
> + if(checkFilter(filter, string)) {
> + return true;
> + }
> + }
> + }
> + return false;
> + }
> + }
> +
> + /**
> + * Check a filter against a string. If the filter
> is
> + * empty it is considered a match. If both are
> not
> + * empty and the string matches the regular
> expression
> + * of the filter it is considered a match.
> Otherwise
> + * it is considered NOT to be a match.
> + *
> + * @param filter Filter string to match string
> against
> + * @param string String to match against filter
> string
> + * @return boolean True if string matches filter
> + */
> + private boolean checkFilter(String filter, String
> string) {
> + if(filter == null || filter == "") {
> + return true;
> + } else {
> + if(string.matches(filter)) {
> + return true;
> + } else {
> + return false;
> + }
> + }
> }
>
> /**
> - * Add a filter
> + * Add a filter, unless it is already present.
> *
> * @param filter to be added
> */
> public void addFilter(String filter) {
> - //TODO: Implement this
> + synchronized(filters) {
> + if(filter != null &&
> !filters.contains(filter)) {
> + filters.add(filter);
> + }
> + }
> }
>
> /**
> Index:
> com/babeldoc/scanner/worker/DirectoryScanner.java
>
===================================================================
> RCS file:
>
/cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker/DirectoryScanner.java,v
> retrieving revision 1.23
> diff -u -r1.23 DirectoryScanner.java
> ---
> com/babeldoc/scanner/worker/DirectoryScanner.java 3
> Oct 2003 13:08:40 -0000 1.23
> +++
> com/babeldoc/scanner/worker/DirectoryScanner.java 8
> Oct 2003 09:54:26 -0000
> @@ -119,6 +119,15 @@
> */
> private int minimumFileAge = 0;
>
> + /** Filename filter, as regular expression, to
> apply
> + * to all scanned files. If not defined it
> will have
> + * no effect, i.e all files will match. If
> defined,
> + * only files matching the regular expression
> will
> + * be processed.
> + */
> + private String filter = null;
> +
> +
> /**
> * This method will scan for new documents. It
> will queue documents by
> * itself, so it will return null no matter how
> many documents found!
> @@ -179,14 +188,21 @@
> + getMinimumFileAge() + " ms");
> }
>
> - //Add filename filter if exist
> - addFilter(FILTER_FILENAME);
> +
>
setFilter(this.getInfo().getStrValue(FILTER_FILENAME));
> +
> + if(getFilter() != null && getFilter() !=
> "") {
> +
> LogService.getInstance().logInfo("Filename filter: "
> + + getFilter());
> + addFilter(getFilter());
> + }
> +
> }
>
> /**
> * release the held resource. Do nothing - no
> held resources.
> */
> public void relinquishResources() {
> + // noop
> }
>
> /**
> @@ -321,7 +337,7 @@
>
=== message truncated ===
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
|
|
From: David K. <dav...@al...> - 2003-10-08 10:14:24
|
Hi people, I noticed that the filtering in DirectoryScanner, and the underlying ScannerWorker, was not actually implemented, and since I needed it I added some code that seems to work: ScannerWorker: - Added a private List of filters - Did the TODO in addFilter to feed the above List - Added a private method checkFilter(filter, string) - Added code to acceptEntry that checks the supplied string against the supplied filter and any already configured filters in the above List DirectoryScanner: - Added a private String for the (configured) filter - Added code to get the filter string if configured - Added code to acceptFile to use the configured filter and actually do some filtering using the code now in ScannerWorker The logic is: If no filter is specified and no filters are present in the List, the string matches, regardless. If filters are present, the string matches if it matches any of the filters. If a filter is also supplied in the method call, that filter is also checked, but only if it is not already present in the List. I have tested all changes and they seem to work, and they are fully backwards compatible, i.e no changes need to be done to existing configurations - they work as before. Example configuration snippet for a DirectoryScanner: <scanner-name>.filter=.*\.xml The above filter (obviously) matches files named *.xml and nothing else. It uses the regular expression support in the String class. So that might require 1.4-level Java support? Patch attached. Please review, and apply if correct && useful. Regards, David Kinnvall |
|
From: McDonald, B. <Bru...@ba...> - 2003-10-07 22:15:53
|
1. Use the code in CVS.
2. Use the dummy journal: Create journal/config.properties - with single line: journalType=dummy
-----Original Message-----
From: Qin Ding [mailto:qd...@cs...]
Sent: Tuesday, October 07, 2003 3:38 PM
To: David Glick
Cc: bab...@li...
Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
David and Bruce:
Let me report back to you all I have done to try to solve the Velocity
issue.
I modified the my validation routine to use VelocityEngine instead of
Velocity. That way, I can start a new instance of Velocity. Now, my
velocity works, although it still has hard time to find the resource file
(vm file). Right now, I just hard coded the vm file.
I run command line, as you see it works:
C:\DADDY-~1>babeldoc process -p validation-pipeline -f c:
\daddy-longlegs\Aftermarket.dat
<2003-10-07 14:19:18,307> INFO [main] : PipelineStage name: initialize
2003-10-07 14:19:19,469|INFO |filevalidation.TestManager|Start processing
Aftermarket
2003-10-07 14:19:19,729|INFO |filevalidation.TestManager|Processed
Aftermarket[24 rows] in 0 second(s)
Please help me with the following two questions:
1. But when I use the scanner to run the same file, I got this error.
Basically, when document.get("file_name") failed. It returns null value.
I remembered that Bruce mentioned that he just fixed this problem. Can I
download the patch? Or what should I do to fix it myself for the time
being?
2. I remember I have asked this question:
What should I do with those ever-growing folders under %BABELDOC_HOME%. Is
there a way to purge them if necessary? What would happen if I manually
remove them? I just want to know how to manage the filesystem which seems
growing very fast.
These are the errors when running scanner:
2003-10-07
14:24:04,248|ERROR|filevalidation.TestManager|AD0028771065554644248:longlegs.core.filevalidation.utils.FileValidationException:
java.lang.Exception: null is null value
at
longlegs.core.filevalidation.utils.ExceptionUtil.createFileValidationException(Unknown
Source)
at longlegs.core.filevalidation.TestManager.validate(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 org.mozilla.javascript.NativeJavaMethod.call(Unknown Source)
at org.mozilla.javascript.ScriptRuntime.call(Unknown Source)
at org.mozilla.javascript.gen.c1.call(Unknown Source)
at org.mozilla.javascript.gen.c1.exec(Unknown Source)
at org.mozilla.javascript.Context.evaluateReader(Unknown Source)
at org.mozilla.javascript.Context.evaluateString(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)
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.AsynchronousFeeder.actuallyProcess(Unknown
Source)
at com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown
Source)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.lang.Exception: null is null value
... 28 more
2003-10-07
14:24:04,289|ERROR|pipeline.DefaultPipelineStageErrorHandler|[DefaultPipelineStageErrorHandler.handlePipelineStageError]
PipelineStage name: initialize Error:
com.babeldoc.core.pipeline.PipelineException: Script processing
failed2003-10-07
14:24:04,299|ERROR|feeder.AsynchronousFeeder|[AsynchronousFeeder$1.run]
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.AsynchronousFeeder.actuallyProcess(Unknown
Source)
at com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown
Source)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:536)
Caused by: org.apache.bsf.BSFException: JavaScript Error:
longlegs.core.filevalidation.utils.FileValidationException:
java.lang.Exception: null is null value
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)
... 12 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: Michael A. <mic...@ze...> - 2003-10-07 21:43:42
|
Hi, Attached file is the result of a cvs diff -c. It'll probably need some clearing out before it's usable, but I'm sure anybody who uses it will be able to figure out what needs to be done. This patch adds three parameters to the mailbox scanner: fromFilter, toFilter and subjectFilter. The values for these parameters are expected to be regular expressions, so don't just type a value in and expect it to work; it won't. To find the matching rules, please refer to: http://java.sun.com/j2se/1.4.2/docs/api/index.html, which details the regex rules that will be used. As one would expect, setting values for these parameters results in the scanner only processing messages that meet the filtering requirements. Have fun, any issues, let me know. Cheers... MikeA On Tue, 2003-10-07 at 17:40, McDonald, Bruce wrote: > Point 1. Agreed. > > Point 2. That depends. There is not process that will gobble up your tags... However note that the process that takes the message.properties text may place it in an element for which it is not a valid child. That being said, docbook seems to allow such free range that you are probably ok. My thinking is: Do the change, rebuild (to get the messages.properties into the jar files) and then generate the documentation - check. > > When are we going to see your code? :) > > Bruce. > > PS. Interested in CVS access? > > -----Original Message----- > From: Michael Ansley [mailto:mic...@ze...] > Sent: Tuesday, October 07, 2003 12:35 PM > To: McDonald, Bruce > Subject: RE: [Babeldoc-devel] Patches > > > Hi, Bruce, > > Yes, I have a similar disposition. It looks fairly good though, so I'll > give it a try. > > What's the deal with putting DocBook tags into the messages.properties > file? I wanted to put some markup into the Mailscanner documentation, > but the source for the scanner documentation seems to be the > messages.prperties file, which is a flat file, and I'm concerned that > other processes that use the file may hooch over the markup. Can I > markup in the messages.properties file? > > Cheers... > > > MikeA > > > On Tue, 2003-10-07 at 16:21, McDonald, Bruce wrote: > > Mike, > > > > I dont have this information anymore. There are others out there. Try this: > > > > http://www.conglomerate.org/ > > > > (I have to hold my nose to use Gnome applications :) > > > > -----Original Message----- > > From: Michael Ansley [mailto:mic...@ze...] > > Sent: Monday, October 06, 2003 3:39 PM > > To: McDonald, Bruce > > Cc: bab...@li... > > Subject: RE: [Babeldoc-devel] Patches > > > > > > Hi, Bruce, > > > > Any chance you can send me your OO XML filter configuration? I'm not > > sure that I'm getting it right. > > > > Cheers... > > > > > > MikeA > > > > > > > > On Mon, 2003-10-06 at 14:36, McDonald, Bruce wrote: > > > You should be able to download them from www.openoffice.org. This is a fantastic office suite - this is what I use to read word and excel files - also some of the Babeldoc documentation is written in this format. > > > > > > -----Original Message----- > > > From: Michael Ansley [mailto:mic...@ze...] > > > Sent: Sunday, October 05, 2003 5:57 PM > > > To: bab...@li... > > > Subject: Re: [Babeldoc-devel] Patches > > > > > > > > > Hi, Dejan, > > > > > > Thanks. I forgot about that. I figured out to change the > > > messages.properties file, as the babeldoc pipeline to create the docs > > > seems to draw the info from there. It seems that you have to do a > > > "build.sh dist" for it to be carried through. Anyway, it seems to work > > > out. > > > Any idea on where I can get OO rpms? I would prefer to stay with rpms, > > > if I can. > > > > > > Cheers... > > > > > > > > > MikeA > > > > > > > > > On Sun, 2003-10-05 at 13:13, Dejan Krsmanovic wrote: > > > > OpenOffice 1.1 supports DocBook format. This week has > > > > been released 1.1 final version. Note that you don't > > > > need to use docbook if you just want to describe new > > > > options in MailboxScanner. Just put them in ConfigInfo > > > > object in MailboxScanner class. Take a look at how > > > > existing options are described. This object is used > > > > for config options validation and for generating > > > > documentation (one day it could be used for gui tools, > > > > too!). > > > > > > > > Dejan > > > > --- Bruce McDonald <br...@mc...> wrote: > > > > > Michael, > > > > > > > > > > Patches can be sent as unified diffs or as a > > > > > complete file. Your choice. > > > > > > > > > > As for editing the docs, I use vi :) But there are > > > > > a number of XML editors > > > > > that can do the job directly on the DocBook code. > > > > > Ask the list (I guess you > > > > > have) > > > > > > > > > > Bruce. > > > > > > > > > > On Saturday 04 October 2003 12:26 pm, Michael Ansley > > > > > wrote: > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > 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 > > > > > > > > > > > > __________________________________ > > > > Do you Yahoo!? > > > > The New Yahoo! Shopping - with improved product search > > > > http://shopping.yahoo.com > > > > > > > > > > > > ------------------------------------------------------- > > > > 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: Qin D. <qd...@cs...> - 2003-10-07 19:39:25
|
David and Bruce:
Let me report back to you all I have done to try to solve the Velocity
issue.
I modified the my validation routine to use VelocityEngine instead of
Velocity. That way, I can start a new instance of Velocity. Now, my
velocity works, although it still has hard time to find the resource file
(vm file). Right now, I just hard coded the vm file.
I run command line, as you see it works:
C:\DADDY-~1>babeldoc process -p validation-pipeline -f c:
\daddy-longlegs\Aftermarket.dat
<2003-10-07 14:19:18,307> INFO [main] : PipelineStage name: initialize
2003-10-07 14:19:19,469|INFO |filevalidation.TestManager|Start processing
Aftermarket
2003-10-07 14:19:19,729|INFO |filevalidation.TestManager|Processed
Aftermarket[24 rows] in 0 second(s)
Please help me with the following two questions:
1. But when I use the scanner to run the same file, I got this error.
Basically, when document.get("file_name") failed. It returns null value.
I remembered that Bruce mentioned that he just fixed this problem. Can I
download the patch? Or what should I do to fix it myself for the time
being?
2. I remember I have asked this question:
What should I do with those ever-growing folders under %BABELDOC_HOME%. Is
there a way to purge them if necessary? What would happen if I manually
remove them? I just want to know how to manage the filesystem which seems
growing very fast.
These are the errors when running scanner:
2003-10-07
14:24:04,248|ERROR|filevalidation.TestManager|AD0028771065554644248:longlegs.core.filevalidation.utils.FileValidationException:
java.lang.Exception: null is null value
at
longlegs.core.filevalidation.utils.ExceptionUtil.createFileValidationException(Unknown
Source)
at longlegs.core.filevalidation.TestManager.validate(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 org.mozilla.javascript.NativeJavaMethod.call(Unknown Source)
at org.mozilla.javascript.ScriptRuntime.call(Unknown Source)
at org.mozilla.javascript.gen.c1.call(Unknown Source)
at org.mozilla.javascript.gen.c1.exec(Unknown Source)
at org.mozilla.javascript.Context.evaluateReader(Unknown Source)
at org.mozilla.javascript.Context.evaluateString(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)
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.AsynchronousFeeder.actuallyProcess(Unknown
Source)
at com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown
Source)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.lang.Exception: null is null value
... 28 more
2003-10-07
14:24:04,289|ERROR|pipeline.DefaultPipelineStageErrorHandler|[DefaultPipelineStageErrorHandler.handlePipelineStageError]
PipelineStage name: initialize Error:
com.babeldoc.core.pipeline.PipelineException: Script processing
failed2003-10-07
14:24:04,299|ERROR|feeder.AsynchronousFeeder|[AsynchronousFeeder$1.run]
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.AsynchronousFeeder.actuallyProcess(Unknown
Source)
at com.babeldoc.core.pipeline.feeder.AsynchronousFeeder$1.run(Unknown
Source)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:536)
Caused by: org.apache.bsf.BSFException: JavaScript Error:
longlegs.core.filevalidation.utils.FileValidationException:
java.lang.Exception: null is null value
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)
... 12 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: McDonald, B. <Bru...@ba...> - 2003-10-07 13:16:29
|
And I will refer you to the source code and to the Velocity web site.
-----Original Message-----
From: David Glick [mailto:dg...@co...]
Sent: Tuesday, October 07, 2003 12:44 AM
To: Qin Ding; Bruce McDonald
Cc: bab...@li...
Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help
Hi Qin,
Since I only know the bare minimum of Velocity, I'll let Master Bruce field
this one.
David
On Monday 06 October 2003 3:36 pm, Qin Ding wrote:
> Bruce and David:
>
> I don't need to create a lib folder of my own and then set classpath to it.
> I finally found out that I just have to put my jar into %babeldoc_home%/lib
> directory. The problem that babeldoc did not find my jar before is
> because the way that script imports the classes. Now, I fixed the scripts
> and the babeldoc finds my jar and starts validationg the file. It is very
> good.
>
> However, another problem. In my validation routine, I use Velocity to
> generate a validation report. Now, for some unknown reasons, my Velocity
> could not start. See the following error trace. I put my debug statement
> in my validation routine. The problem is right at initializing the
> VelocityEngine. I checked the Velocity documents, there are two ways to
> initialize the Velocity: Singleton and non-Singleton. Singleton means only
> one instance of Velocity per JVM allowed. I guess when I tried to
> initialize my velocity, the scripting does not like it.
>
> Is there a reason that the babeldoc only allows Singleton Velocity? Can we
> change it to none-singleton? Where is in Babeldoc that Velocity is first
> initialized? Maybe I can try to change it to none-singleton and see if it
> makes any diffrerence.
>
> Please let me know, I am pretty close to get this thing work. The only
> thing that needs to fix is the initialize the velocity.
>
> Thank you.
>
> 2003-10-06 17:07:55,668|DEBUG|filevalidation.TestManager|Enter
> logErrors2003-10-06 17:07:55,668|DEBUG|filevalidation.TestManager|Enter
> logErrorDetails2003-10-06 17:07:55,668|INFO
>
> |filevalidation.TestManager|Processed Aftermarket[24 rows] in 0
>
> second(s)2003-10-06
>
> 17:07:55,728|ERROR|pipeline.DefaultPipelineStageErrorHandler|[DefaultPipeli
>neStageErrorHandler.handlePipelineStageError] PipelineStage name:
> initialize Error: com.babeldoc.core.pipeline.PipelineException: Script
> processing failed2003-10-06
> 17:07:55,728|ERROR|command.PipelineFeeder|[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:
> java.lang.ExceptionInInitializerError
> 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.
> ---------------------------------------------------------------------------
>-------------
>
>
>
>
>
> Bruce McDonald
> <bruce To: Qin
> Ding/ASD/CSC@CSC, David Glick <dg...@co...> @mcdonald-family cc:
> bab...@li... .com> Subject:
> Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help 10/03/03
> 07:53
> PM
>
>
>
>
>
>
> 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
--
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: David G. <dg...@co...> - 2003-10-07 04:40:25
|
Hi Qin,
Since I only know the bare minimum of Velocity, I'll let Master Bruce field
this one.
David
On Monday 06 October 2003 3:36 pm, Qin Ding wrote:
> Bruce and David:
>
> I don't need to create a lib folder of my own and then set classpath to it.
> I finally found out that I just have to put my jar into %babeldoc_home%/lib
> directory. The problem that babeldoc did not find my jar before is
> because the way that script imports the classes. Now, I fixed the scripts
> and the babeldoc finds my jar and starts validationg the file. It is very
> good.
>
> However, another problem. In my validation routine, I use Velocity to
> generate a validation report. Now, for some unknown reasons, my Velocity
> could not start. See the following error trace. I put my debug statement
> in my validation routine. The problem is right at initializing the
> VelocityEngine. I checked the Velocity documents, there are two ways to
> initialize the Velocity: Singleton and non-Singleton. Singleton means only
> one instance of Velocity per JVM allowed. I guess when I tried to
> initialize my velocity, the scripting does not like it.
>
> Is there a reason that the babeldoc only allows Singleton Velocity? Can we
> change it to none-singleton? Where is in Babeldoc that Velocity is first
> initialized? Maybe I can try to change it to none-singleton and see if it
> makes any diffrerence.
>
> Please let me know, I am pretty close to get this thing work. The only
> thing that needs to fix is the initialize the velocity.
>
> Thank you.
>
> 2003-10-06 17:07:55,668|DEBUG|filevalidation.TestManager|Enter
> logErrors2003-10-06 17:07:55,668|DEBUG|filevalidation.TestManager|Enter
> logErrorDetails2003-10-06 17:07:55,668|INFO
>
> |filevalidation.TestManager|Processed Aftermarket[24 rows] in 0
>
> second(s)2003-10-06
>
> 17:07:55,728|ERROR|pipeline.DefaultPipelineStageErrorHandler|[DefaultPipeli
>neStageErrorHandler.handlePipelineStageError] PipelineStage name:
> initialize Error: com.babeldoc.core.pipeline.PipelineException: Script
> processing failed2003-10-06
> 17:07:55,728|ERROR|command.PipelineFeeder|[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:
> java.lang.ExceptionInInitializerError
> 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.
> ---------------------------------------------------------------------------
>-------------
>
>
>
>
>
> Bruce McDonald
> <bruce To: Qin
> Ding/ASD/CSC@CSC, David Glick <dg...@co...> @mcdonald-family cc:
> bab...@li... .com> Subject:
> Re: [Babeldoc-devel] Re: [Babeldoc-user] Questions. Please Help 10/03/03
> 07:53
> PM
>
>
>
>
>
>
> 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
--
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...
|
|
From: Qin D. <qd...@cs...> - 2003-10-06 22:38:11
|
Bruce and David:
I don't need to create a lib folder of my own and then set classpath to it.
I finally found out that I just have to put my jar into %babeldoc_home%/lib
directory. The problem that babeldoc did not find my jar before is
because the way that script imports the classes. Now, I fixed the scripts
and the babeldoc finds my jar and starts validationg the file. It is very
good.
However, another problem. In my validation routine, I use Velocity to
generate a validation report. Now, for some unknown reasons, my Velocity
could not start. See the following error trace. I put my debug statement
in my validation routine. The problem is right at initializing the
VelocityEngine. I checked the Velocity documents, there are two ways to
initialize the Velocity: Singleton and non-Singleton. Singleton means only
one instance of Velocity per JVM allowed. I guess when I tried to
initialize my velocity, the scripting does not like it.
Is there a reason that the babeldoc only allows Singleton Velocity? Can we
change it to none-singleton? Where is in Babeldoc that Velocity is first
initialized? Maybe I can try to change it to none-singleton and see if it
makes any diffrerence.
Please let me know, I am pretty close to get this thing work. The only
thing that needs to fix is the initialize the velocity.
Thank you.
2003-10-06 17:07:55,668|DEBUG|filevalidation.TestManager|Enter
logErrors2003-10-06 17:07:55,668|DEBUG|filevalidation.TestManager|Enter
logErrorDetails2003-10-06 17:07:55,668|INFO
|filevalidation.TestManager|Processed Aftermarket[24 rows] in 0
second(s)2003-10-06
17:07:55,728|ERROR|pipeline.DefaultPipelineStageErrorHandler|[DefaultPipelineStageErrorHandler.handlePipelineStageError]
PipelineStage name:
initialize Error: com.babeldoc.core.pipeline.PipelineException: Script
processing failed2003-10-06
17:07:55,728|ERROR|command.PipelineFeeder|[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:
java.lang.ExceptionInInitializerError
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.
----------------------------------------------------------------------------------------
Bruce McDonald
<bruce To: Qin Ding/ASD/CSC@CSC, David Glick <dg...@co...>
@mcdonald-family cc: bab...@li...
.com> Subject: Re: [Babeldoc-devel] Re: [Babeldoc-user]
Questions. Please Help
10/03/03 07:53
PM
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: Michael A. <mic...@ze...> - 2003-10-06 19:39:03
|
Hi, Bruce, Any chance you can send me your OO XML filter configuration? I'm not sure that I'm getting it right. Cheers... MikeA On Mon, 2003-10-06 at 14:36, McDonald, Bruce wrote: > You should be able to download them from www.openoffice.org. This is a fantastic office suite - this is what I use to read word and excel files - also some of the Babeldoc documentation is written in this format. > > -----Original Message----- > From: Michael Ansley [mailto:mic...@ze...] > Sent: Sunday, October 05, 2003 5:57 PM > To: bab...@li... > Subject: Re: [Babeldoc-devel] Patches > > > Hi, Dejan, > > Thanks. I forgot about that. I figured out to change the > messages.properties file, as the babeldoc pipeline to create the docs > seems to draw the info from there. It seems that you have to do a > "build.sh dist" for it to be carried through. Anyway, it seems to work > out. > Any idea on where I can get OO rpms? I would prefer to stay with rpms, > if I can. > > Cheers... > > > MikeA > > > On Sun, 2003-10-05 at 13:13, Dejan Krsmanovic wrote: > > OpenOffice 1.1 supports DocBook format. This week has > > been released 1.1 final version. Note that you don't > > need to use docbook if you just want to describe new > > options in MailboxScanner. Just put them in ConfigInfo > > object in MailboxScanner class. Take a look at how > > existing options are described. This object is used > > for config options validation and for generating > > documentation (one day it could be used for gui tools, > > too!). > > > > Dejan > > --- Bruce McDonald <br...@mc...> wrote: > > > Michael, > > > > > > Patches can be sent as unified diffs or as a > > > complete file. Your choice. > > > > > > As for editing the docs, I use vi :) But there are > > > a number of XML editors > > > that can do the job directly on the DocBook code. > > > Ask the list (I guess you > > > have) > > > > > > Bruce. > > > > > > On Saturday 04 October 2003 12:26 pm, Michael Ansley > > > wrote: > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > 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 > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Shopping - with improved product search > > http://shopping.yahoo.com > > > > > > ------------------------------------------------------- > > 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-06 13:38:40
|
You should be able to download them from www.openoffice.org. This is a fantastic office suite - this is what I use to read word and excel files - also some of the Babeldoc documentation is written in this format. -----Original Message----- From: Michael Ansley [mailto:mic...@ze...] Sent: Sunday, October 05, 2003 5:57 PM To: bab...@li... Subject: Re: [Babeldoc-devel] Patches Hi, Dejan, Thanks. I forgot about that. I figured out to change the messages.properties file, as the babeldoc pipeline to create the docs seems to draw the info from there. It seems that you have to do a "build.sh dist" for it to be carried through. Anyway, it seems to work out. Any idea on where I can get OO rpms? I would prefer to stay with rpms, if I can. Cheers... MikeA On Sun, 2003-10-05 at 13:13, Dejan Krsmanovic wrote: > OpenOffice 1.1 supports DocBook format. This week has > been released 1.1 final version. Note that you don't > need to use docbook if you just want to describe new > options in MailboxScanner. Just put them in ConfigInfo > object in MailboxScanner class. Take a look at how > existing options are described. This object is used > for config options validation and for generating > documentation (one day it could be used for gui tools, > too!). > > Dejan > --- Bruce McDonald <br...@mc...> wrote: > > Michael, > > > > Patches can be sent as unified diffs or as a > > complete file. Your choice. > > > > As for editing the docs, I use vi :) But there are > > a number of XML editors > > that can do the job directly on the DocBook code. > > Ask the list (I guess you > > have) > > > > Bruce. > > > > On Saturday 04 October 2003 12:26 pm, Michael Ansley > > wrote: > > > 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 > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > 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 > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Shopping - with improved product search > http://shopping.yahoo.com > > > ------------------------------------------------------- > 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: Dejan K. <dej...@nb...> - 2003-10-06 07:02:37
|
I don't know. I have downloaded and installed only Windows version. Dejan ----- Original Message ----- From: "Michael Ansley" <mic...@ze...> To: <bab...@li...> Sent: Sunday, October 05, 2003 11:57 PM Subject: Re: [Babeldoc-devel] Patches > Hi, Dejan, > > Thanks. I forgot about that. I figured out to change the > messages.properties file, as the babeldoc pipeline to create the docs > seems to draw the info from there. It seems that you have to do a > "build.sh dist" for it to be carried through. Anyway, it seems to work > out. > Any idea on where I can get OO rpms? I would prefer to stay with rpms, > if I can. > > Cheers... > > > MikeA > > > On Sun, 2003-10-05 at 13:13, Dejan Krsmanovic wrote: > > OpenOffice 1.1 supports DocBook format. This week has > > been released 1.1 final version. Note that you don't > > need to use docbook if you just want to describe new > > options in MailboxScanner. Just put them in ConfigInfo > > object in MailboxScanner class. Take a look at how > > existing options are described. This object is used > > for config options validation and for generating > > documentation (one day it could be used for gui tools, > > too!). > > > > Dejan > > --- Bruce McDonald <br...@mc...> wrote: > > > Michael, > > > > > > Patches can be sent as unified diffs or as a > > > complete file. Your choice. > > > > > > As for editing the docs, I use vi :) But there are > > > a number of XML editors > > > that can do the job directly on the DocBook code. > > > Ask the list (I guess you > > > have) > > > > > > Bruce. > > > > > > On Saturday 04 October 2003 12:26 pm, Michael Ansley > > > wrote: > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > 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 > > > > > > __________________________________ > > Do you Yahoo!? > > The New Yahoo! Shopping - with improved product search > > http://shopping.yahoo.com > > > > > > ------------------------------------------------------- > > 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: Michael A. <mic...@ze...> - 2003-10-05 21:57:21
|
Hi, Dejan, Thanks. I forgot about that. I figured out to change the messages.properties file, as the babeldoc pipeline to create the docs seems to draw the info from there. It seems that you have to do a "build.sh dist" for it to be carried through. Anyway, it seems to work out. Any idea on where I can get OO rpms? I would prefer to stay with rpms, if I can. Cheers... MikeA On Sun, 2003-10-05 at 13:13, Dejan Krsmanovic wrote: > OpenOffice 1.1 supports DocBook format. This week has > been released 1.1 final version. Note that you don't > need to use docbook if you just want to describe new > options in MailboxScanner. Just put them in ConfigInfo > object in MailboxScanner class. Take a look at how > existing options are described. This object is used > for config options validation and for generating > documentation (one day it could be used for gui tools, > too!). > > Dejan > --- Bruce McDonald <br...@mc...> wrote: > > Michael, > > > > Patches can be sent as unified diffs or as a > > complete file. Your choice. > > > > As for editing the docs, I use vi :) But there are > > a number of XML editors > > that can do the job directly on the DocBook code. > > Ask the list (I guess you > > have) > > > > Bruce. > > > > On Saturday 04 October 2003 12:26 pm, Michael Ansley > > wrote: > > > 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 > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > 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 > > > __________________________________ > Do you Yahoo!? > The New Yahoo! Shopping - with improved product search > http://shopping.yahoo.com > > > ------------------------------------------------------- > 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: Dejan K. <dej...@ya...> - 2003-10-05 12:13:36
|
OpenOffice 1.1 supports DocBook format. This week has been released 1.1 final version. Note that you don't need to use docbook if you just want to describe new options in MailboxScanner. Just put them in ConfigInfo object in MailboxScanner class. Take a look at how existing options are described. This object is used for config options validation and for generating documentation (one day it could be used for gui tools, too!). Dejan --- Bruce McDonald <br...@mc...> wrote: > Michael, > > Patches can be sent as unified diffs or as a > complete file. Your choice. > > As for editing the docs, I use vi :) But there are > a number of XML editors > that can do the job directly on the DocBook code. > Ask the list (I guess you > have) > > Bruce. > > On Saturday 04 October 2003 12:26 pm, Michael Ansley > wrote: > > 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 > > > > > > > > > > > > > ------------------------------------------------------- > > 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 __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com |
|
From: Michael A. <mic...@ze...> - 2003-10-04 21:35:22
|
Thanks, Bruce. On Sat, 2003-10-04 at 22:03, Bruce McDonald wrote: > Michael, > > You dont (there isnt a rule - yet...). To build the babeldoc documentation, > do the following: > > 1. build babeldoc. > 2. run babeldoc: babeldoc process -p documentation > > This assumes that the bin/babeldoc script is in the path. > > regards, > Bruce. > > On Saturday 04 October 2003 12:37 pm, Michael Ansley wrote: > > PS: How do you build the html docs from the XML? I can't find an ant > > rule. > > > > > > > > > > ------------------------------------------------------- > > 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: Bruce M. <br...@mc...> - 2003-10-04 21:05:17
|
Michael, Patches can be sent as unified diffs or as a complete file. Your choice. As for editing the docs, I use vi :) But there are a number of XML editors that can do the job directly on the DocBook code. Ask the list (I guess you have) Bruce. On Saturday 04 October 2003 12:26 pm, Michael Ansley wrote: > 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 > > > > > > ------------------------------------------------------- > 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-04 21:03:51
|
Michael, You dont (there isnt a rule - yet...). To build the babeldoc documentation, do the following: 1. build babeldoc. 2. run babeldoc: babeldoc process -p documentation This assumes that the bin/babeldoc script is in the path. regards, Bruce. On Saturday 04 October 2003 12:37 pm, Michael Ansley wrote: > PS: How do you build the html docs from the XML? I can't find an ant > rule. > > > > > ------------------------------------------------------- > 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 |