Menu
▾
▴
babeldoc-devel — Babeldoc developer list
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(14) |
Mar
(107) |
Apr
(211) |
May
(93) |
Jun
(158) |
Jul
(159) |
Aug
(368) |
Sep
(188) |
Oct
(151) |
Nov
(115) |
Dec
(98) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(25) |
Feb
|
Mar
(33) |
Apr
(28) |
May
(116) |
Jun
(2) |
Jul
(117) |
Aug
(19) |
Sep
(9) |
Oct
(2) |
Nov
|
Dec
(4) |
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(9) |
Dec
|
| 2006 |
Jan
|
Feb
|
Mar
(22) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(267) |
Sep
|
Oct
|
Nov
(6) |
Dec
(512) |
| 2008 |
Jan
(187) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(6) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ek...@ba...> - 2003-05-14 12:31:05
|
I'm not sure if this is the best way to do it (or even if it will work),
but if you were to do this in two steps:
Step 1: Use SqlEnrich to get the data value that you want out of your DBMS
and into your document
Step 2: Use XslTransform to perform an XSL transformation on your XML, but
include in the transformation script some Velocity scripting that
references the data value that you retrieved in Step 1. Alternatively,
maybe scripting that references the document can allow you to call the
"get" method on the document? If you're not able to access the document
directly from your scripting, you may be able to access it via the
Stage.getDocument( ).
I'm sorry I can't be more certain of a complete answer for you, but maybe
this will take you a bit further or inspire others to correct my
recommendation.
Erik
Sent by: bab...@li...
To: <bab...@li...>
cc:
Subject: [Babeldoc-devel] Advice needed on inserting SQL results back into
documents
I am working with Ken Geis on getting BabelDoc up and running in our
product.
As we are going through understanding BDoc, and seeing how we can use it,
I am stuck on something which seems like it should be a standard thing to
do.
We have XML documents running through the pipelines, and have a need to
include the results of a SQL query back into the XML itself. For example,
we have the name of an item:
<ITEM>
<NAME>An item name</NAME>
</ITEM>
We have a static data table that relates an item name to a code:
CODE table
ID | CODE | NAME |
1 | 25 | An item name |
We need to execute:
Select code from Code where name = $name
We need the result:
<ITEM>
<CODE>25</CODE>
<NAME>An item name</NAME>
</ITEM>
The xslt-velocity-sql example in BDoc 1.0 RC5 sort of looks like the way
to go, but:
- VariableProcessor.executeSqlSelect has been moved to VelocitySqlContext
and seems incomplete (initialize is not called anywhere)
- I think I want to embed the SQL in the XSL, not in the underlying
document. The example has the SQL in the document.
I know about SqlEnrich, but I need the data in the document itself for
downstream processing, not in the BabelDoc attributes.
Does anyone in BabelDoc land have any advice?
Thanks!
Sherman Wood
GalenWorks LLC
415 516-4894
________________________________________________________________________
The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: Dejan K. <dej...@nb...> - 2003-05-14 07:24:36
|
I have fixed some bugs in generating documentation for pipeline stages and scanners. However, I have noticed that some of PipelineStageInfo objects are referencing resource bundle keys that are not exist in i18n file. For example keys for DomifyPipelineStage does not exist in current CVS version of i18n . Please commit these files before releasing 1.0 today! Bruce, don't forget to re-generate pipelinestage.xml and scanner.xml ;) Dejan |
|
From: <br...@mc...> - 2003-05-14 07:03:17
|
Buildfile: build.xml
declare:
depends:
[echo] Build order: core gui sql web soap scanner crypto babelfish conversion
build:
[echo] Building Babeldoc in: /home/bruce/work/cvs-babeldoc/babeldoc_v1
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/examples
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/readme
build:
[echo] Building core
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[javac] Compiling 148 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 26 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build/env
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_core.jar
[copy] Copying 80 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building core
build:
[echo] Building gui
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[javac] Compiling 3 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_gui.jar
build:
[echo] Building gui
build:
[echo] Building sql
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[javac] Compiling 21 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_sql.jar
[copy] Copying 7 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building sql
build:
[echo] Building web
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[javac] Compiling 5 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 23 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-console.war
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-httpfeed.war
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/bin
build:
[echo] Building web
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
build:
[echo] Building soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soapfeed.war
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building soap
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
build:
[echo] Building scanner
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[javac] Compiling 28 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[rmic] RMI Compiling 1 class to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-scanner.jar
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building scanner
build:
[echo] Building crypto
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_crypto.jar
build:
[echo] Building crypto
build:
[echo] Building babelfish
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[javac] Compiling 2 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_babelfish.jar
build:
[echo] Building babelfish
build:
[echo] Building conversion
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[javac] Compiling 14 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_conversion.jar
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building conversion
BUILD SUCCESSFUL
Total time: 35 seconds
|
|
From: Sherman W. <sw...@ga...> - 2003-05-14 01:30:40
|
I am working with Ken Geis on getting BabelDoc up and running in our
product.
As we are going through understanding BDoc, and seeing how we can use
it, I am stuck on something which seems like it should be a standard
thing to do.
We have XML documents running through the pipelines, and have a need to
include the results of a SQL query back into the XML itself. For
example, we have the name of an item:
<ITEM>
<NAME>An item name</NAME>
</ITEM>
We have a static data table that relates an item name to a code:
CODE table
ID | CODE | NAME |
1 | 25 | An item name |
We need to execute:
Select code from Code where name = $name
We need the result:
<ITEM>
<CODE>25</CODE>
<NAME>An item name</NAME>
</ITEM>
The xslt-velocity-sql example in BDoc 1.0 RC5 sort of looks like the way
to go, but:
- VariableProcessor.executeSqlSelect has been moved to
VelocitySqlContext and seems incomplete (initialize is not called
anywhere)
- I think I want to embed the SQL in the XSL, not in the
underlying document. The example has the SQL in the document.
I know about SqlEnrich, but I need the data in the document itself for
downstream processing, not in the BabelDoc attributes.
Does anyone in BabelDoc land have any advice?
Thanks!
Sherman Wood
GalenWorks LLC
415 516-4894
|
|
From: <ld...@ba...> - 2003-05-13 14:02:46
|
Bruce, my sourceforge logon name is ldong (from ld...@ba...). To: ek...@ba..., bab...@li... cc: ld...@ba... Subject: Re: [Babeldoc-devel] My project partner What is his sourceforge logon name? On Monday 12 May 2003 10:10 am, ek...@ba... wrote: > As you may have heard, my client will not be renewing my consulting > agreement and I will be leaving the project on May 23rd. Leong Dong > (pronounced Leon) has been on the project since its inception but has > allowed me to focus on the Babeldoc side of things while he has built all > the J2EE "wrappings" around Babeldoc. Leong will be taking over Babeldoc > shortly and I will start the "Knowledge Transfer" this week. He will > become the main Babeldoc contact for our project. > > Bruce, could you setup Leong as a developer with CVS access? I believe he > already has a SourceForge account and I know he gets the emails. > > All, please welcome Leong. Thanks. > > Erik > > ________________________________________________________________________ > The information in this e-mail, and any attachment therein, is confidential > and for use by the addressee only. If you are not the intended recipient, > please return the e-mail to the sender and delete it from your computer. > Although The Bank of New York attempts to sweep e-mail and attachments for > viruses, it does not guarantee that either are virus-free and accepts no > liability for any damage sustained as a result of viruses. ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: <br...@mc...> - 2003-05-13 07:03:45
|
Buildfile: build.xml
declare:
depends:
[echo] Build order: core gui sql web soap scanner crypto babelfish conversion
build:
[echo] Building Babeldoc in: /home/bruce/work/cvs-babeldoc/babeldoc_v1
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/examples
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/readme
build:
[echo] Building core
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[javac] Compiling 148 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 26 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build/env
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_core.jar
[copy] Copying 80 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building core
build:
[echo] Building gui
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[javac] Compiling 3 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_gui.jar
build:
[echo] Building gui
build:
[echo] Building sql
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[javac] Compiling 21 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_sql.jar
[copy] Copying 7 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building sql
build:
[echo] Building web
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[javac] Compiling 5 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 23 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-console.war
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-httpfeed.war
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/bin
build:
[echo] Building web
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
build:
[echo] Building soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soapfeed.war
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building soap
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
build:
[echo] Building scanner
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[javac] Compiling 28 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[rmic] RMI Compiling 1 class to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-scanner.jar
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building scanner
build:
[echo] Building crypto
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_crypto.jar
build:
[echo] Building crypto
build:
[echo] Building babelfish
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[javac] Compiling 2 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_babelfish.jar
build:
[echo] Building babelfish
build:
[echo] Building conversion
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[javac] Compiling 14 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_conversion.jar
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building conversion
BUILD SUCCESSFUL
Total time: 34 seconds
|
|
From: Bruce M. <br...@mc...> - 2003-05-13 01:13:14
|
What is his sourceforge logon name? On Monday 12 May 2003 10:10 am, ek...@ba... wrote: > As you may have heard, my client will not be renewing my consulting > agreement and I will be leaving the project on May 23rd. Leong Dong > (pronounced Leon) has been on the project since its inception but has > allowed me to focus on the Babeldoc side of things while he has built all > the J2EE "wrappings" around Babeldoc. Leong will be taking over Babeldoc > shortly and I will start the "Knowledge Transfer" this week. He will > become the main Babeldoc contact for our project. > > Bruce, could you setup Leong as a developer with CVS access? I believe he > already has a SourceForge account and I know he gets the emails. > > All, please welcome Leong. Thanks. > > Erik > > ________________________________________________________________________ > The information in this e-mail, and any attachment therein, is confidential > and for use by the addressee only. If you are not the intended recipient, > please return the e-mail to the sender and delete it from your computer. > Although The Bank of New York attempts to sweep e-mail and attachments for > viruses, it does not guarantee that either are virus-free and accepts no > liability for any damage sustained as a result of viruses. |
|
From: Dejan K. <dej...@ya...> - 2003-05-12 19:59:56
|
Hmm. I couldn't re-create this bug here at home. Altough I have installed babeldoc at two lines long folder structure... I must check tomorrow in office what was the problem. Maybe Windows XP does not have same limitations as Windows 2000?! Dejan --- ek...@ba... wrote: > << > There is a bug when starting babeldoc.bat on Win2k. > I got input line too > long error. > >> > > This is most likely a problem with any Windows > Platform. It happens to me > all the time using NT for starting Weblogic. The > problem is that the > combination of a huge string of JARs in a classpath > combined with all the > "-D" system variables exceeds Window's command > length. One approach that > worked for me (until Jython decided it didn't like > it) was to use > -Dbabeldoc.scandir=<JAR directory>. My other > solution (which Jython also > didn't like) was creating an EAR including all JARs > in it. My last > solution (which is embarrassing) is that I JARred up > all the Apache > Common's JARs into one big JAR ... I know ... not > elegant. > > ________________________________________________________________________ > The information in this e-mail, and any attachment > therein, is confidential and for use by the > addressee only. If you are not the intended > recipient, please return the e-mail to the sender > and delete it from your computer. Although The Bank > of New York attempts to sweep e-mail and attachments > for viruses, it does not guarantee that either are > virus-free and accepts no liability for any damage > sustained as a result of viruses. __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com |
|
From: <ek...@ba...> - 2003-05-12 16:03:29
|
<< There is a bug when starting babeldoc.bat on Win2k. I got input line too long error. >> This is most likely a problem with any Windows Platform. It happens to me all the time using NT for starting Weblogic. The problem is that the combination of a huge string of JARs in a classpath combined with all the "-D" system variables exceeds Window's command length. One approach that worked for me (until Jython decided it didn't like it) was to use -Dbabeldoc.scandir=<JAR directory>. My other solution (which Jython also didn't like) was creating an EAR including all JARs in it. My last solution (which is embarrassing) is that I JARred up all the Apache Common's JARs into one big JAR ... I know ... not elegant. ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: Dejan K. <dej...@nb...> - 2003-05-12 15:38:59
|
There is a bug when starting babeldoc.bat on Win2k. I got input line too long error. An user has reported this, too. We should fix this before 1.0 release Dejan |
|
From: <ek...@ba...> - 2003-05-12 14:11:07
|
As you may have heard, my client will not be renewing my consulting agreement and I will be leaving the project on May 23rd. Leong Dong (pronounced Leon) has been on the project since its inception but has allowed me to focus on the Babeldoc side of things while he has built all the J2EE "wrappings" around Babeldoc. Leong will be taking over Babeldoc shortly and I will start the "Knowledge Transfer" this week. He will become the main Babeldoc contact for our project. Bruce, could you setup Leong as a developer with CVS access? I believe he already has a SourceForge account and I know he gets the emails. All, please welcome Leong. Thanks. Erik ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: <br...@mc...> - 2003-05-12 07:00:49
|
Buildfile: build.xml
declare:
depends:
[echo] Build order: core gui sql web soap scanner crypto babelfish conversion
build:
[echo] Building Babeldoc in: /home/bruce/work/cvs-babeldoc/babeldoc_v1
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/examples
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/readme
build:
[echo] Building core
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[javac] Compiling 148 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 26 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build/env
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_core.jar
[copy] Copying 81 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building core
build:
[echo] Building gui
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[javac] Compiling 3 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_gui.jar
build:
[echo] Building gui
build:
[echo] Building sql
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[javac] Compiling 21 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_sql.jar
[copy] Copying 7 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building sql
build:
[echo] Building web
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[javac] Compiling 5 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 23 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-console.war
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-httpfeed.war
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/bin
build:
[echo] Building web
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
build:
[echo] Building soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soapfeed.war
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building soap
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
build:
[echo] Building scanner
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[javac] Compiling 28 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[rmic] RMI Compiling 1 class to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-scanner.jar
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building scanner
build:
[echo] Building crypto
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_crypto.jar
build:
[echo] Building crypto
build:
[echo] Building babelfish
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[javac] Compiling 2 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_babelfish.jar
build:
[echo] Building babelfish
build:
[echo] Building conversion
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[javac] Compiling 14 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_conversion.jar
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building conversion
BUILD SUCCESSFUL
Total time: 34 seconds
|
|
From: <br...@mc...> - 2003-05-11 07:00:52
|
Buildfile: build.xml
declare:
depends:
[echo] Build order: core gui sql web soap scanner crypto babelfish conversion
build:
[echo] Building Babeldoc in: /home/bruce/work/cvs-babeldoc/babeldoc_v1
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/examples
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/readme
build:
[echo] Building core
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[javac] Compiling 148 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 26 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build/env
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_core.jar
[copy] Copying 81 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building core
build:
[echo] Building gui
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[javac] Compiling 3 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_gui.jar
build:
[echo] Building gui
build:
[echo] Building sql
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[javac] Compiling 21 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_sql.jar
[copy] Copying 7 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building sql
build:
[echo] Building web
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[javac] Compiling 5 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 23 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-console.war
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-httpfeed.war
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/bin
build:
[echo] Building web
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
build:
[echo] Building soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soapfeed.war
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building soap
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
build:
[echo] Building scanner
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[javac] Compiling 28 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[rmic] RMI Compiling 1 class to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-scanner.jar
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building scanner
build:
[echo] Building crypto
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_crypto.jar
build:
[echo] Building crypto
build:
[echo] Building babelfish
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[javac] Compiling 2 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_babelfish.jar
build:
[echo] Building babelfish
build:
[echo] Building conversion
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[javac] Compiling 14 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_conversion.jar
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building conversion
BUILD SUCCESSFUL
Total time: 36 seconds
|
|
From: <br...@mc...> - 2003-05-10 07:00:48
|
Buildfile: build.xml
declare:
depends:
[echo] Build order: core gui sql web soap scanner crypto babelfish conversion
build:
[echo] Building Babeldoc in: /home/bruce/work/cvs-babeldoc/babeldoc_v1
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/examples
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/readme
build:
[echo] Building core
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[javac] Compiling 148 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 26 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build/env
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_core.jar
[copy] Copying 81 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building core
build:
[echo] Building gui
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[javac] Compiling 3 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/gui/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_gui.jar
build:
[echo] Building gui
build:
[echo] Building sql
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[javac] Compiling 21 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/sql/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_sql.jar
[copy] Copying 7 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building sql
build:
[echo] Building web
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[javac] Compiling 5 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 23 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/console/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-console.war
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/web/build/httpfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-httpfeed.war
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/bin
build:
[echo] Building web
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_web.jar
build:
[echo] Building soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed/WEB-INF
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soapfeed.war
[copy] Copying 5 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building soap
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soap.jar
build:
[echo] Building scanner
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[javac] Compiling 28 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[rmic] RMI Compiling 1 class to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/scanner/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc-scanner.jar
[copy] Copying 3 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building scanner
build:
[echo] Building crypto
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[javac] Compiling 4 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/crypto/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_crypto.jar
build:
[echo] Building crypto
build:
[echo] Building babelfish
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[javac] Compiling 2 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/babelfish/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_babelfish.jar
build:
[echo] Building babelfish
build:
[echo] Building conversion
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[javac] Compiling 14 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[copy] Copying 2 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/conversion/build
[jar] Building jar: /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_conversion.jar
[copy] Copying 11 files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
build:
[echo] Building conversion
BUILD SUCCESSFUL
Total time: 34 seconds
|
|
From: <ek...@ba...> - 2003-05-09 12:51:06
|
<< Talking about documentation, do you speak Serbian? ;-) >> Not yet ... I'll get on it right away ... sorry for my American ignorance (we're born with it here) ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: Dejan K. <dej...@nb...> - 2003-05-09 12:46:50
|
Right. No new functionalities. Dejan ----- Original Message ----- From: "Bruce McDonald" <br...@mc...> To: "Dejan Krsmanovic" <dej...@nb...>; <bab...@li...> Sent: Friday, May 09, 2003 2:44 PM Subject: Re: [Babeldoc-devel] Preparing 1.0 release > Ok, > > So the changes for 1.0 are all in? (This is not referring to bug fixes). > > regards, > Bruce. > > On Friday 09 May 2003 08:37 am, Dejan Krsmanovic wrote: > > No. They are still in experimental phase. I even havent tested it in my > > company. > > Dejan > > > > ----- Original Message ----- > > From: "Bruce McDonald" <br...@mc...> > > To: "Dejan Krsmanovic" <dej...@nb...>; > > <bab...@li...> > > Sent: Friday, May 09, 2003 2:33 PM > > Subject: Re: [Babeldoc-devel] Preparing 1.0 release > > > > > Dejan, > > > > > > Good point about cvs - The main branch (MAIN) is the current development > > > stream. So, if you checkin/out code, it will go to MAIN unless to attach > > > > to > > > > > the 1.0 branch. > > > > > > Here is a question? Your changes to scanner - do you want to get them in > > > > for > > > > > 1.0?? > > > > > > regards, > > > Bruce. > > > > > > On Friday 09 May 2003 03:01 am, Dejan Krsmanovic wrote: > > > > > On monday, I want to get in touch with the sourceforge folks to > > > > > > > > restructure > > > > > > > > > CVS. I thing that we should remove the old babeldoc module and > > > > > rename the babeldoc_v1 to babeldoc. We should also delete the other > > > > > crud > > > > thats > > > > > > > out there. We can then tag that release v1_0 and branch it right > > > > there. > > > > > > Agreed. No need for useless CVS modules... > > > > > > > > > Bug fixes and incremental fixes to this branch will go in this > > > > > branch. At > > > > > > > > the > > > > > > > > > same time I will get a v1_1 branch opened where we will start > > > > > development. The culmination of v1_1 development will be a 1.2 > > > > > release > > > > at > > > > > > > which point > > > > > > > > we > > > > > > > > > branch again. > > > > > > > > One tehnical question. If we have branch v1_0 for bug fixes and v1_1 > > > > for new development, what should go in HEAD branch? I think new > > > > development should go in HEAD branch (main branch) and after every > > > > major release we should create branch for bugfixes. For other releases > > > > we could just use tags (as we did by now). > > > > > > > > > Please comment - unless there is a major objection tomorrow, I will > > > > > be > > > > > > > > going > > > > > > > > > ahead as planned. > > > > > > > > > > Whats in my future for babeldoc: > > > > > > > > > > 0. Update outdated libraries > > > > > > > > > > 1. Commons/discovery > > > > > I have been tinkering with this library and have been able to get it > > > > > > > > working > > > > > > > > > to the point that I am very confident that this can replace the > > > > > module discovery code. I have tested this standalone and in tomcat. > > > > > > > > > > 2. Compiler > > > > > I have also been hacking with Javassist (this is an amazing library) > > > > and > > > > > > want > > > > > > > > > to make a compiler. This compiler will take a pipeline definition > > > > > and > > > > > > > > create > > > > > > > > > a class that will represent the computational steps for that pipeline > > > > but > > > > > > all > > > > > > > > > statically resolved (as far as possible). This will result in > > > > > performance benefits. > > > > > > > > > > 3. Gui > > > > > Start a gui framework that we can build and extend into a full blown > > > > > Application. > > > > > > > > > > Thoughts, Comments? > > > > > > > > I am doing some experiments with scanners and I believe it will be well > > > > tested for new release. The main idea right now in my head is to > > > > separate > > > > > > code for scanning messages and for processing. Baisicly, I am planning > > > > to > > > > > > use classic producer/consumer pattern, where scanners will just get new > > > > documents and queue them up. Processing of documents should be done in > > > > separate thread by getting documents from queue. Documents in queues > > > > should > > > > > > be serialized so in case of some accident they will be loaded > > > > application > > > > > > starts next time. I am still not sure if we should use JMS for queueing > > > > or > > > > > > write class for this stuff... Anyway, I am planning to use JMX for > > > > managment of all these components. > > > > > > > > I have already wrote some basic code for validation and setting > > > > configuration options for scanner workers. The code would simply go > > > > from option to option and check option value. The code should also try > > > > to set option values if getter and setter methods are avaliable. So if > > > > you have username option you could provide getUsername and setUsername > > > > methods so validatior could set username property. Now, this code could > > > > also be applied to pipeline stages. These are basic differences between > > > > scanner > > > > and > > > > > > pipelineStage configuration: > > > > - PipelineStage options are evaluated in runtime for each document. > > > > - PipelineStage options can have suboptions > > > > - PipelineStage use PipelineStageConfig and scanners use > > > > ScannerWorkerConfig classes. > > > > > > > > I guess both PipelineStageConfig ans ScannerConfig could be generalized > > > > in > > > > > > one class that later could be specialized if necessery. All other > > > > problems > > > > > > could be solved by this. > > > > > > > > Other features that I plan in the near future is some kind of > > > > ExcelReader > > > > > > pipeline stage that would create xml file from excel file using Jakarta > > > > POI, HttpScanner class and maybe some other features we would need... > > > > By the way, next week I am starting Babeldoc training for 4 employees > > > > in > > > > my > > > > > > company. I guess this will give me better picture how successfull > > > > ordinary > > > > > > users can use Babeldoc... > > > > > > > > Best regards, > > > > Dejan > > > > > > > > > regards, > > > > > Bruce. > > > > > > > > > > On Thursday 08 May 2003 05:41 am, Dejan Krsmanovic wrote: > > > > > > I agree. > > > > > > Dejan > > > > > > > > > > > > > By the way: I had a look at the jalopy plugin for ant (before I > > > > only > > > > > > had > > > > > > > > > > > used the one for eclipse). Do you (all of you) really want me to > > > > > > > > include > > > > > > > > > > > this in all build.xml files? I would put it in a separate task > > > > > > > > "format" > > > > > > > > > > > that should be called manually before committing to cvs. We would > > > > of > > > > > > > > > course have to apply it once to all files in the repository - not > > > > > > > > before > > > > > > > > > > > friday, I assume... :-) > > > > > > > > > > > > > > Regards, > > > > > > > Hans > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa > > > > Clara > > > > > > > > > The only event dedicated to issues related to Linux enterprise > > > > > > > > solutions > > > > > > > > > > > www.enterpriselinuxforum.com > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Babeldoc-devel mailing list > > > > > > > Bab...@li... > > > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > > > > > > > ------------------------------------------------------- > > > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa > > > > Clara > > > > > > > > The only event dedicated to issues related to Linux enterprise > > > > > > solutions www.enterpriselinuxforum.com > > > > > > > > > > > > _______________________________________________ > > > > > > Babeldoc-devel mailing list > > > > > > Bab...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > > > > > ------------------------------------------------------- > > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > > > The only event dedicated to issues related to Linux enterprise > > > > solutions > > > > > > > www.enterpriselinuxforum.com > > > > > > > > > > _______________________________________________ > > > > > Babeldoc-devel mailing list > > > > > Bab...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > > > ------------------------------------------------------- > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > > The only event dedicated to issues related to Linux enterprise > > > > solutions www.enterpriselinuxforum.com > > > > > > > > _______________________________________________ > > > > Babeldoc-devel mailing list > > > > Bab...@li... > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > ------------------------------------------------------- > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > The only event dedicated to issues related to Linux enterprise solutions > > > www.enterpriselinuxforum.com > > > > > > _______________________________________________ > > > Babeldoc-devel mailing list > > > Bab...@li... > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Dejan K. <dej...@nb...> - 2003-05-09 12:44:33
|
You are right about JMS. Talking about documentation, do you speak Serbian? ;-) I am planning to give them only offical Babeldoc documentation. I am also writing some materials for one conference here, but that will be in Serbian, too! Dejan ----- Original Message ----- From: ek...@ba... To: Dejan Krsmanovic Cc: Bruce McDonald ; bab...@li... Sent: Friday, May 09, 2003 2:31 PM Subject: Re: [Babeldoc-devel] Preparing 1.0 release << One tehnical question. If we have branch v1_0 for bug fixes and v1_1 for new development, what should go in HEAD branch? I think new development should go in HEAD branch (main branch) and after every major release we should create branch for bugfixes. For other releases we could just use tags (as we did by now). >> Agreed. << Documents in queues should be serialized so in case of some accident they will be loaded application starts next time. I am still not sure if we should use JMS for queueing or write class for this stuff. >> Remember that JMS pretty much mandates that Babeldoc be inside of a J2EE container in order to use scanners in your scenario ... I'm not sure that was the original intent of the project. << By the way, next week I am starting Babeldoc training for 4 employees in my company. >> You might want to share any documentation / handouts you provide for them with this group. ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: Bruce M. <br...@mc...> - 2003-05-09 12:44:08
|
Ok, So the changes for 1.0 are all in? (This is not referring to bug fixes). regards, Bruce. On Friday 09 May 2003 08:37 am, Dejan Krsmanovic wrote: > No. They are still in experimental phase. I even havent tested it in my > company. > Dejan > > ----- Original Message ----- > From: "Bruce McDonald" <br...@mc...> > To: "Dejan Krsmanovic" <dej...@nb...>; > <bab...@li...> > Sent: Friday, May 09, 2003 2:33 PM > Subject: Re: [Babeldoc-devel] Preparing 1.0 release > > > Dejan, > > > > Good point about cvs - The main branch (MAIN) is the current development > > stream. So, if you checkin/out code, it will go to MAIN unless to attach > > to > > > the 1.0 branch. > > > > Here is a question? Your changes to scanner - do you want to get them in > > for > > > 1.0?? > > > > regards, > > Bruce. > > > > On Friday 09 May 2003 03:01 am, Dejan Krsmanovic wrote: > > > > On monday, I want to get in touch with the sourceforge folks to > > > > > > restructure > > > > > > > CVS. I thing that we should remove the old babeldoc module and > > > > rename the babeldoc_v1 to babeldoc. We should also delete the other > > > > crud > > thats > > > > > out there. We can then tag that release v1_0 and branch it right > > there. > > > > Agreed. No need for useless CVS modules... > > > > > > > Bug fixes and incremental fixes to this branch will go in this > > > > branch. At > > > > > > the > > > > > > > same time I will get a v1_1 branch opened where we will start > > > > development. The culmination of v1_1 development will be a 1.2 > > > > release > > at > > > > > which point > > > > > > we > > > > > > > branch again. > > > > > > One tehnical question. If we have branch v1_0 for bug fixes and v1_1 > > > for new development, what should go in HEAD branch? I think new > > > development should go in HEAD branch (main branch) and after every > > > major release we should create branch for bugfixes. For other releases > > > we could just use tags (as we did by now). > > > > > > > Please comment - unless there is a major objection tomorrow, I will > > > > be > > > > > > going > > > > > > > ahead as planned. > > > > > > > > Whats in my future for babeldoc: > > > > > > > > 0. Update outdated libraries > > > > > > > > 1. Commons/discovery > > > > I have been tinkering with this library and have been able to get it > > > > > > working > > > > > > > to the point that I am very confident that this can replace the > > > > module discovery code. I have tested this standalone and in tomcat. > > > > > > > > 2. Compiler > > > > I have also been hacking with Javassist (this is an amazing library) > > and > > > > want > > > > > > > to make a compiler. This compiler will take a pipeline definition > > > > and > > > > > > create > > > > > > > a class that will represent the computational steps for that pipeline > > but > > > > all > > > > > > > statically resolved (as far as possible). This will result in > > > > performance benefits. > > > > > > > > 3. Gui > > > > Start a gui framework that we can build and extend into a full blown > > > > Application. > > > > > > > > Thoughts, Comments? > > > > > > I am doing some experiments with scanners and I believe it will be well > > > tested for new release. The main idea right now in my head is to > > separate > > > > code for scanning messages and for processing. Baisicly, I am planning > > to > > > > use classic producer/consumer pattern, where scanners will just get new > > > documents and queue them up. Processing of documents should be done in > > > separate thread by getting documents from queue. Documents in queues > > should > > > > be serialized so in case of some accident they will be loaded > > application > > > > starts next time. I am still not sure if we should use JMS for queueing > > or > > > > write class for this stuff... Anyway, I am planning to use JMX for > > > managment of all these components. > > > > > > I have already wrote some basic code for validation and setting > > > configuration options for scanner workers. The code would simply go > > > from option to option and check option value. The code should also try > > > to set option values if getter and setter methods are avaliable. So if > > > you have username option you could provide getUsername and setUsername > > > methods so validatior could set username property. Now, this code could > > > also be applied to pipeline stages. These are basic differences between > > > scanner > > and > > > > pipelineStage configuration: > > > - PipelineStage options are evaluated in runtime for each document. > > > - PipelineStage options can have suboptions > > > - PipelineStage use PipelineStageConfig and scanners use > > > ScannerWorkerConfig classes. > > > > > > I guess both PipelineStageConfig ans ScannerConfig could be generalized > > in > > > > one class that later could be specialized if necessery. All other > > problems > > > > could be solved by this. > > > > > > Other features that I plan in the near future is some kind of > > ExcelReader > > > > pipeline stage that would create xml file from excel file using Jakarta > > > POI, HttpScanner class and maybe some other features we would need... > > > By the way, next week I am starting Babeldoc training for 4 employees > > > in > > my > > > > company. I guess this will give me better picture how successfull > > ordinary > > > > users can use Babeldoc... > > > > > > Best regards, > > > Dejan > > > > > > > regards, > > > > Bruce. > > > > > > > > On Thursday 08 May 2003 05:41 am, Dejan Krsmanovic wrote: > > > > > I agree. > > > > > Dejan > > > > > > > > > > > By the way: I had a look at the jalopy plugin for ant (before I > > only > > > > had > > > > > > > > > used the one for eclipse). Do you (all of you) really want me to > > > > > > include > > > > > > > > > this in all build.xml files? I would put it in a separate task > > > > > > "format" > > > > > > > > > that should be called manually before committing to cvs. We would > > of > > > > > > > course have to apply it once to all files in the repository - not > > > > > > before > > > > > > > > > friday, I assume... :-) > > > > > > > > > > > > Regards, > > > > > > Hans > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa > > Clara > > > > > > > The only event dedicated to issues related to Linux enterprise > > > > > > solutions > > > > > > > > > www.enterpriselinuxforum.com > > > > > > > > > > > > _______________________________________________ > > > > > > Babeldoc-devel mailing list > > > > > > Bab...@li... > > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > > > > > ------------------------------------------------------- > > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa > > Clara > > > > > > The only event dedicated to issues related to Linux enterprise > > > > > solutions www.enterpriselinuxforum.com > > > > > > > > > > _______________________________________________ > > > > > Babeldoc-devel mailing list > > > > > Bab...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > > > ------------------------------------------------------- > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > > The only event dedicated to issues related to Linux enterprise > > solutions > > > > > www.enterpriselinuxforum.com > > > > > > > > _______________________________________________ > > > > Babeldoc-devel mailing list > > > > Bab...@li... > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > ------------------------------------------------------- > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > The only event dedicated to issues related to Linux enterprise > > > solutions www.enterpriselinuxforum.com > > > > > > _______________________________________________ > > > Babeldoc-devel mailing list > > > Bab...@li... > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Dejan K. <dej...@nb...> - 2003-05-09 12:38:01
|
No. They are still in experimental phase. I even havent tested it in my company. Dejan ----- Original Message ----- From: "Bruce McDonald" <br...@mc...> To: "Dejan Krsmanovic" <dej...@nb...>; <bab...@li...> Sent: Friday, May 09, 2003 2:33 PM Subject: Re: [Babeldoc-devel] Preparing 1.0 release > Dejan, > > Good point about cvs - The main branch (MAIN) is the current development > stream. So, if you checkin/out code, it will go to MAIN unless to attach to > the 1.0 branch. > > Here is a question? Your changes to scanner - do you want to get them in for > 1.0?? > > regards, > Bruce. > > On Friday 09 May 2003 03:01 am, Dejan Krsmanovic wrote: > > > On monday, I want to get in touch with the sourceforge folks to > > > > restructure > > > > > CVS. I thing that we should remove the old babeldoc module and rename > > > the babeldoc_v1 to babeldoc. We should also delete the other crud thats > > > out there. We can then tag that release v1_0 and branch it right there. > > > > Agreed. No need for useless CVS modules... > > > > > Bug fixes and incremental fixes to this branch will go in this branch. > > > At > > > > the > > > > > same time I will get a v1_1 branch opened where we will start > > > development. The culmination of v1_1 development will be a 1.2 release at > > > which point > > > > we > > > > > branch again. > > > > One tehnical question. If we have branch v1_0 for bug fixes and v1_1 for > > new development, what should go in HEAD branch? I think new development > > should go in HEAD branch (main branch) and after every major release we > > should create branch for bugfixes. For other releases we could just use > > tags (as we did by now). > > > > > Please comment - unless there is a major objection tomorrow, I will be > > > > going > > > > > ahead as planned. > > > > > > Whats in my future for babeldoc: > > > > > > 0. Update outdated libraries > > > > > > 1. Commons/discovery > > > I have been tinkering with this library and have been able to get it > > > > working > > > > > to the point that I am very confident that this can replace the module > > > discovery code. I have tested this standalone and in tomcat. > > > > > > 2. Compiler > > > I have also been hacking with Javassist (this is an amazing library) and > > > > want > > > > > to make a compiler. This compiler will take a pipeline definition and > > > > create > > > > > a class that will represent the computational steps for that pipeline but > > > > all > > > > > statically resolved (as far as possible). This will result in > > > performance benefits. > > > > > > 3. Gui > > > Start a gui framework that we can build and extend into a full blown > > > Application. > > > > > > Thoughts, Comments? > > > > I am doing some experiments with scanners and I believe it will be well > > tested for new release. The main idea right now in my head is to separate > > code for scanning messages and for processing. Baisicly, I am planning to > > use classic producer/consumer pattern, where scanners will just get new > > documents and queue them up. Processing of documents should be done in > > separate thread by getting documents from queue. Documents in queues should > > be serialized so in case of some accident they will be loaded application > > starts next time. I am still not sure if we should use JMS for queueing or > > write class for this stuff... Anyway, I am planning to use JMX for > > managment of all these components. > > > > I have already wrote some basic code for validation and setting > > configuration options for scanner workers. The code would simply go from > > option to option and check option value. The code should also try to set > > option values if getter and setter methods are avaliable. So if you have > > username option you could provide getUsername and setUsername methods so > > validatior could set username property. Now, this code could also be > > applied to pipeline stages. These are basic differences between scanner and > > pipelineStage configuration: > > - PipelineStage options are evaluated in runtime for each document. > > - PipelineStage options can have suboptions > > - PipelineStage use PipelineStageConfig and scanners use > > ScannerWorkerConfig classes. > > > > I guess both PipelineStageConfig ans ScannerConfig could be generalized in > > one class that later could be specialized if necessery. All other problems > > could be solved by this. > > > > Other features that I plan in the near future is some kind of ExcelReader > > pipeline stage that would create xml file from excel file using Jakarta > > POI, HttpScanner class and maybe some other features we would need... > > By the way, next week I am starting Babeldoc training for 4 employees in my > > company. I guess this will give me better picture how successfull ordinary > > users can use Babeldoc... > > > > Best regards, > > Dejan > > > > > regards, > > > Bruce. > > > > > > On Thursday 08 May 2003 05:41 am, Dejan Krsmanovic wrote: > > > > I agree. > > > > Dejan > > > > > > > > > By the way: I had a look at the jalopy plugin for ant (before I only > > > > had > > > > > > > used the one for eclipse). Do you (all of you) really want me to > > > > include > > > > > > > this in all build.xml files? I would put it in a separate task > > > > "format" > > > > > > > that should be called manually before committing to cvs. We would of > > > > > course have to apply it once to all files in the repository - not > > > > before > > > > > > > friday, I assume... :-) > > > > > > > > > > Regards, > > > > > Hans > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > > > The only event dedicated to issues related to Linux enterprise > > > > solutions > > > > > > > www.enterpriselinuxforum.com > > > > > > > > > > _______________________________________________ > > > > > Babeldoc-devel mailing list > > > > > Bab...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > > > ------------------------------------------------------- > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > > The only event dedicated to issues related to Linux enterprise > > > > solutions www.enterpriselinuxforum.com > > > > > > > > _______________________________________________ > > > > Babeldoc-devel mailing list > > > > Bab...@li... > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > ------------------------------------------------------- > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > The only event dedicated to issues related to Linux enterprise solutions > > > www.enterpriselinuxforum.com > > > > > > _______________________________________________ > > > Babeldoc-devel mailing list > > > Bab...@li... > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Dejan K. <dej...@nb...> - 2003-05-09 12:35:10
|
I have just commited Erik's code. I have tested it with my pipelines and only thing I mentioned was requirement that nextStage have to be set. So I have added one line with stage.nextStage=null where needed. I am not sure if documentation states this requirement Dejan ----- Original Message ----- From: ek...@ba... To: bab...@li... Cc: br...@mc... ; dej...@nb... ; ben...@ch... ; cbw...@ea... Sent: Friday, May 09, 2003 1:49 AM Subject: Re: [Babeldoc-devel] Heads Up Guys, As I informed earlier, I have made some "substantial" changes to a number of classes involved with pipeline processing to improve its ability to report errors/exception is pipeline processing. I'm a bit paranoid about "breaking the build" and have therefore "JARred" up the changes that I have made (I believe I have included them all) and attached them to this email, rather than putting them in CVS (which I abhor, but that is another subject). Can you please UnJar these files into your build directory, rebuild, and run with all the pipelines you currently have? I have done so and have actually identified errors in a few pipelines that I didn't even know I had. Please let me know your results tomorrow as it is my last official "programming day" for my project. Thanks. Erik To: ek...@ba..., bab...@li... cc: Subject: Re: [Babeldoc-devel] Heads Up Erik, All: Excellent work - this is kind of polish that is needed. In the light of this, I want to delay to next wednesday to release 1.0. This will give me some time to work on a news release. regards Bruce On Thursday 08 May 2003 02:27 pm, ek...@ba... wrote: > Just wanted to let you all know that Dejan and I brainstormed over the > last 2 days as to the best way to enhance the exception handling without > doing more work than is necessary in the system. I've been working today > on a few classes associated with Pipeline processing where I see the most > "bang for the buck" in making corrections ... progress is good ... I hope > to check in the results before end of day. > > However, I feel that we should all give this code a little workout before > we do an official announcement to make sure that our pipelines all act as > we expect them to. This might take a couple of days. > > Any feelings on this? > > Erik > > ________________________________________________________________________ > The information in this e-mail, and any attachment therein, is confidential > and for use by the addressee only. If you are not the intended recipient, > please return the e-mail to the sender and delete it from your computer. > Although The Bank of New York attempts to sweep e-mail and attachments for > viruses, it does not guarantee that either are virus-free and accepts no > liability for any damage sustained as a result of viruses. ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: Bruce M. <br...@mc...> - 2003-05-09 12:33:13
|
Dejan, Good point about cvs - The main branch (MAIN) is the current development stream. So, if you checkin/out code, it will go to MAIN unless to attach to the 1.0 branch. Here is a question? Your changes to scanner - do you want to get them in for 1.0?? regards, Bruce. On Friday 09 May 2003 03:01 am, Dejan Krsmanovic wrote: > > On monday, I want to get in touch with the sourceforge folks to > > restructure > > > CVS. I thing that we should remove the old babeldoc module and rename > > the babeldoc_v1 to babeldoc. We should also delete the other crud thats > > out there. We can then tag that release v1_0 and branch it right there. > > Agreed. No need for useless CVS modules... > > > Bug fixes and incremental fixes to this branch will go in this branch. > > At > > the > > > same time I will get a v1_1 branch opened where we will start > > development. The culmination of v1_1 development will be a 1.2 release at > > which point > > we > > > branch again. > > One tehnical question. If we have branch v1_0 for bug fixes and v1_1 for > new development, what should go in HEAD branch? I think new development > should go in HEAD branch (main branch) and after every major release we > should create branch for bugfixes. For other releases we could just use > tags (as we did by now). > > > Please comment - unless there is a major objection tomorrow, I will be > > going > > > ahead as planned. > > > > Whats in my future for babeldoc: > > > > 0. Update outdated libraries > > > > 1. Commons/discovery > > I have been tinkering with this library and have been able to get it > > working > > > to the point that I am very confident that this can replace the module > > discovery code. I have tested this standalone and in tomcat. > > > > 2. Compiler > > I have also been hacking with Javassist (this is an amazing library) and > > want > > > to make a compiler. This compiler will take a pipeline definition and > > create > > > a class that will represent the computational steps for that pipeline but > > all > > > statically resolved (as far as possible). This will result in > > performance benefits. > > > > 3. Gui > > Start a gui framework that we can build and extend into a full blown > > Application. > > > > Thoughts, Comments? > > I am doing some experiments with scanners and I believe it will be well > tested for new release. The main idea right now in my head is to separate > code for scanning messages and for processing. Baisicly, I am planning to > use classic producer/consumer pattern, where scanners will just get new > documents and queue them up. Processing of documents should be done in > separate thread by getting documents from queue. Documents in queues should > be serialized so in case of some accident they will be loaded application > starts next time. I am still not sure if we should use JMS for queueing or > write class for this stuff... Anyway, I am planning to use JMX for > managment of all these components. > > I have already wrote some basic code for validation and setting > configuration options for scanner workers. The code would simply go from > option to option and check option value. The code should also try to set > option values if getter and setter methods are avaliable. So if you have > username option you could provide getUsername and setUsername methods so > validatior could set username property. Now, this code could also be > applied to pipeline stages. These are basic differences between scanner and > pipelineStage configuration: > - PipelineStage options are evaluated in runtime for each document. > - PipelineStage options can have suboptions > - PipelineStage use PipelineStageConfig and scanners use > ScannerWorkerConfig classes. > > I guess both PipelineStageConfig ans ScannerConfig could be generalized in > one class that later could be specialized if necessery. All other problems > could be solved by this. > > Other features that I plan in the near future is some kind of ExcelReader > pipeline stage that would create xml file from excel file using Jakarta > POI, HttpScanner class and maybe some other features we would need... > By the way, next week I am starting Babeldoc training for 4 employees in my > company. I guess this will give me better picture how successfull ordinary > users can use Babeldoc... > > Best regards, > Dejan > > > regards, > > Bruce. > > > > On Thursday 08 May 2003 05:41 am, Dejan Krsmanovic wrote: > > > I agree. > > > Dejan > > > > > > > By the way: I had a look at the jalopy plugin for ant (before I only > > had > > > > > used the one for eclipse). Do you (all of you) really want me to > > include > > > > > this in all build.xml files? I would put it in a separate task > > "format" > > > > > that should be called manually before committing to cvs. We would of > > > > course have to apply it once to all files in the repository - not > > before > > > > > friday, I assume... :-) > > > > > > > > Regards, > > > > Hans > > > > > > > > > > > > > > > > ------------------------------------------------------- > > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > > The only event dedicated to issues related to Linux enterprise > > solutions > > > > > www.enterpriselinuxforum.com > > > > > > > > _______________________________________________ > > > > Babeldoc-devel mailing list > > > > Bab...@li... > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > > > ------------------------------------------------------- > > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > > The only event dedicated to issues related to Linux enterprise > > > solutions www.enterpriselinuxforum.com > > > > > > _______________________________________________ > > > Babeldoc-devel mailing list > > > Bab...@li... > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: <ek...@ba...> - 2003-05-09 12:31:24
|
<< One tehnical question. If we have branch v1_0 for bug fixes and v1_1 for new development, what should go in HEAD branch? I think new development should go in HEAD branch (main branch) and after every major release we should create branch for bugfixes. For other releases we could just use tags (as we did by now). >> Agreed. << Documents in queues should be serialized so in case of some accident they will be loaded application starts next time. I am still not sure if we should use JMS for queueing or write class for this stuff. >> Remember that JMS pretty much mandates that Babeldoc be inside of a J2EE container in order to use scanners in your scenario ... I'm not sure that was the original intent of the project. << By the way, next week I am starting Babeldoc training for 4 employees in my company. >> You might want to share any documentation / handouts you provide for them with this group. ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: Bruce M. <br...@mc...> - 2003-05-09 12:30:01
|
Dejan, Thank you - regards, Bruce. On Friday 09 May 2003 03:12 am, Dejan Krsmanovic wrote: > > I cannot do this tomorrow. I know time is short - who can help here? I > > have > > > a very limited connection from work. I also dont want to trigger > > anything from a security stand. What I am doing is looking at all the > > stuff that > > has > > > moved since babeldoc was in its rapid evolution. Still waiting for > > access > > to > > > the host. Man - I have read the documentation a number of times. > > I will do it.. > > > And I hear what you are saying about CVS. Its very dated. There is one > > feature of Eclipse that is fantastic. You can synchronize and then > > decide which files get updated, committed and merged. > > You can also use TortoiseCVS. Until I have installed it I have used WinCVS > and nothing was clear to me. TortoiseCVS is nice little program that > integrates into Windows Explorer. You just can click with right mouse > button and checkout CVS modules, make tags, branches etc.... > You can get it on http://sourceforge.net/projects/tortoisecvs > > Dejan > > > later, > > Bruce. > > > > On Thursday 08 May 2003 07:49 pm, ek...@ba... wrote: > > > Guys, > > > > > > As I informed earlier, I have made some "substantial" changes to a > > number > > > > of classes involved with pipeline processing to improve its ability to > > > report errors/exception is pipeline processing. I'm a bit paranoid > > about > > > > "breaking the build" and have therefore "JARred" up the changes that I > > > have made (I believe I have included them all) and attached them to > > > this email, rather than putting them in CVS (which I abhor, but that is > > another > > > > subject). > > > > > > Can you please UnJar these files into your build directory, rebuild, > > > and run with all the pipelines you currently have? I have done so and > > > have actually identified errors in a few pipelines that I didn't even > > > know I had. Please let me know your results tomorrow as it is my last > > > official "programming day" for my project. > > > > > > Thanks. > > > > > > > > > > > > Erik > > > > > > > > > > > > > > > > > > > > > > > > To: ek...@ba..., bab...@li... > > > cc: > > > Subject: Re: [Babeldoc-devel] Heads Up > > > > > > Erik, All: > > > > > > Excellent work - this is kind of polish that is needed. In the light > > > of this, > > > I want to delay to next wednesday to release 1.0. This will give me > > some > > > > time to work on a news release. > > > > > > regards > > > Bruce > > > > > > On Thursday 08 May 2003 02:27 pm, ek...@ba... wrote: > > > > Just wanted to let you all know that Dejan and I brainstormed over > > > > the last 2 days as to the best way to enhance the exception handling > > without > > > > > doing more work than is necessary in the system. I've been working > > > > > > today > > > > > > > on a few classes associated with Pipeline processing where I see the > > > > > > most > > > > > > > "bang for the buck" in making corrections ... progress is good ... I > > > > > > hope > > > > > > > to check in the results before end of day. > > > > > > > > However, I feel that we should all give this code a little workout > > > > > > before > > > > > > > we do an official announcement to make sure that our pipelines all > > > > act > > > > > > as > > > > > > > we expect them to. This might take a couple of days. > > > > > > > > Any feelings on this? > > > > > > > > Erik > > ________________________________________________________________________ > > > > > The information in this e-mail, and any attachment therein, is > > > > > > confidential > > > > > > > and for use by the addressee only. If you are not the intended > > > > > > recipient, > > > > > > > please return the e-mail to the sender and delete it from your > > computer. > > > > > Although The Bank of New York attempts to sweep e-mail and > > > > attachments > > > > > > for > > > > > > > viruses, it does not guarantee that either are virus-free and accepts > > no > > > > > liability for any damage sustained as a result of viruses. > > > > > > _______________________________________________________________________ > > >_ The information in this e-mail, and any attachment therein, is > > confidential > > > > and for use by the addressee only. If you are not the intended > > recipient, > > > > please return the e-mail to the sender and delete it from your > > > computer. Although The Bank of New York attempts to sweep e-mail and > > > attachments > > for > > > > viruses, it does not guarantee that either are virus-free and accepts > > > no liability for any damage sustained as a result of viruses. > > > > ------------------------------------------------------- > > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > > The only event dedicated to issues related to Linux enterprise solutions > > www.enterpriselinuxforum.com > > > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Dejan K. <dej...@nb...> - 2003-05-09 10:48:29
|
Erik, I cannot compile code you have sent me. These are problems: PipelineStage.getMyConfiguration() Earlier, this methods had throws clause and now it doesn't. compiler complains because PipelineException is not handled. The only method that throws exception here is from IPipelineStageResolver.getConfig(). I guess there is no need for throwing excepion here since its children cannot throw it. Is this correct? The next problem I noticed is in PipelineStageResolver.getnextPipelineStageName(). In interface this method does not declare throws clause but in implementation class it does. This caused several problems in other implementation classes. Looking in implementation I have noticed that you throw exception if nextStage is null, so I included throws clause in method. Can you confirm these are the changes you want? If yes, this could cause problems since nextStage CAN be null (not provided). This just mean that processing should stop in that stage. Dejan ----- Original Message ----- From: ek...@ba... To: bab...@li... Cc: br...@mc... ; dej...@nb... ; ben...@ch... ; cbw...@ea... Sent: Friday, May 09, 2003 1:49 AM Subject: Re: [Babeldoc-devel] Heads Up Guys, As I informed earlier, I have made some "substantial" changes to a number of classes involved with pipeline processing to improve its ability to report errors/exception is pipeline processing. I'm a bit paranoid about "breaking the build" and have therefore "JARred" up the changes that I have made (I believe I have included them all) and attached them to this email, rather than putting them in CVS (which I abhor, but that is another subject). Can you please UnJar these files into your build directory, rebuild, and run with all the pipelines you currently have? I have done so and have actually identified errors in a few pipelines that I didn't even know I had. Please let me know your results tomorrow as it is my last official "programming day" for my project. Thanks. Erik To: ek...@ba..., bab...@li... cc: Subject: Re: [Babeldoc-devel] Heads Up Erik, All: Excellent work - this is kind of polish that is needed. In the light of this, I want to delay to next wednesday to release 1.0. This will give me some time to work on a news release. regards Bruce On Thursday 08 May 2003 02:27 pm, ek...@ba... wrote: > Just wanted to let you all know that Dejan and I brainstormed over the > last 2 days as to the best way to enhance the exception handling without > doing more work than is necessary in the system. I've been working today > on a few classes associated with Pipeline processing where I see the most > "bang for the buck" in making corrections ... progress is good ... I hope > to check in the results before end of day. > > However, I feel that we should all give this code a little workout before > we do an official announcement to make sure that our pipelines all act as > we expect them to. This might take a couple of days. > > Any feelings on this? > > Erik > > ________________________________________________________________________ > The information in this e-mail, and any attachment therein, is confidential > and for use by the addressee only. If you are not the intended recipient, > please return the e-mail to the sender and delete it from your computer. > Although The Bank of New York attempts to sweep e-mail and attachments for > viruses, it does not guarantee that either are virus-free and accepts no > liability for any damage sustained as a result of viruses. ________________________________________________________________________ The information in this e-mail, and any attachment therein, is confidential and for use by the addressee only. If you are not the intended recipient, please return the e-mail to the sender and delete it from your computer. Although The Bank of New York attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. |
|
From: Dejan K. <dej...@nb...> - 2003-05-09 07:12:25
|
> I cannot do this tomorrow. I know time is short - who can help here? I have > a very limited connection from work. I also dont want to trigger anything > from a security stand. What I am doing is looking at all the stuff that has > moved since babeldoc was in its rapid evolution. Still waiting for access to > the host. Man - I have read the documentation a number of times. I will do it.. > > And I hear what you are saying about CVS. Its very dated. There is one > feature of Eclipse that is fantastic. You can synchronize and then decide > which files get updated, committed and merged. You can also use TortoiseCVS. Until I have installed it I have used WinCVS and nothing was clear to me. TortoiseCVS is nice little program that integrates into Windows Explorer. You just can click with right mouse button and checkout CVS modules, make tags, branches etc.... You can get it on http://sourceforge.net/projects/tortoisecvs Dejan > > later, > Bruce. > > > On Thursday 08 May 2003 07:49 pm, ek...@ba... wrote: > > Guys, > > > > As I informed earlier, I have made some "substantial" changes to a number > > of classes involved with pipeline processing to improve its ability to > > report errors/exception is pipeline processing. I'm a bit paranoid about > > "breaking the build" and have therefore "JARred" up the changes that I > > have made (I believe I have included them all) and attached them to this > > email, rather than putting them in CVS (which I abhor, but that is another > > subject). > > > > Can you please UnJar these files into your build directory, rebuild, and > > run with all the pipelines you currently have? I have done so and have > > actually identified errors in a few pipelines that I didn't even know I > > had. Please let me know your results tomorrow as it is my last official > > "programming day" for my project. > > > > Thanks. > > > > > > > > Erik > > > > > > > > > > > > > > > > To: ek...@ba..., bab...@li... > > cc: > > Subject: Re: [Babeldoc-devel] Heads Up > > > > Erik, All: > > > > Excellent work - this is kind of polish that is needed. In the light of > > this, > > I want to delay to next wednesday to release 1.0. This will give me some > > time to work on a news release. > > > > regards > > Bruce > > > > On Thursday 08 May 2003 02:27 pm, ek...@ba... wrote: > > > Just wanted to let you all know that Dejan and I brainstormed over the > > > last 2 days as to the best way to enhance the exception handling without > > > doing more work than is necessary in the system. I've been working > > > > today > > > > > on a few classes associated with Pipeline processing where I see the > > > > most > > > > > "bang for the buck" in making corrections ... progress is good ... I > > > > hope > > > > > to check in the results before end of day. > > > > > > However, I feel that we should all give this code a little workout > > > > before > > > > > we do an official announcement to make sure that our pipelines all act > > > > as > > > > > we expect them to. This might take a couple of days. > > > > > > Any feelings on this? > > > > > > Erik > > > > > > ________________________________________________________________________ > > > The information in this e-mail, and any attachment therein, is > > > > confidential > > > > > and for use by the addressee only. If you are not the intended > > > > recipient, > > > > > please return the e-mail to the sender and delete it from your computer. > > > Although The Bank of New York attempts to sweep e-mail and attachments > > > > for > > > > > viruses, it does not guarantee that either are virus-free and accepts no > > > liability for any damage sustained as a result of viruses. > > > > ________________________________________________________________________ > > The information in this e-mail, and any attachment therein, is confidential > > and for use by the addressee only. If you are not the intended recipient, > > please return the e-mail to the sender and delete it from your computer. > > Although The Bank of New York attempts to sweep e-mail and attachments for > > viruses, it does not guarantee that either are virus-free and accepts no > > liability for any damage sustained as a result of viruses. > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
2 messages has been excluded from this view by a project administrator.
