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: Hans B. <ben...@ch...> - 2003-04-09 09:37:24
|
First of all thanks to you, Bruce and Dejan, for your confidence in me - I will try to not break the CVS repository completely ... ;-) I have not yet looked on the Axis API, but as you point out, as a follow-up to Apache SOAP, it should be possible to use it as well. I tend a little bit to use Sun's jaxm, because it is sort of a "more official" standard, but of course I will have a look on Axis as well. Anyway, perhaps it isn't even necesary to switch APIs at all, because it might be correct, what SOAP is doing here. The way it is used in the SoapWriter - via the Message class - implies a one-way communication that might as well happen via smtp, where the response (if any) would not be available at once. Still I would expect Exceptions in case of errors on the transport layer... But depending on your intentions it might be better to use the rpc-style mechanisms of soap, where an immediate response is expected. So I now have some questions about the original intentions for the whole SOAP module: Are the SoapWriter and the SoapFeeder meant to be interfaces to external applications that happen to speak SOAP? Or should they transport a pipeline from one sytem to another? (like this: SomeScanner----PipelineStage1----PipelineStage2-- --SoapWriter........sends.HTTP.request........SoapFeeder-- --PipelineStage3----SomeWriter ) In the latter case, I would expect that tickets would have to travel over the soap link (although I have to admit, that I have not yet completely understood the ticket mechanism). But as far as I can see, at the moment the SoapFeeder servlet produces an xml response containing tickets, that is not a SOAP response and SoapWriter does not look at the response at all. Shall I change this behaviour as well? Regards, Hans On Wed, 9 Apr 2003, Dejan Krsmanovic wrote: > This is desirable, but I don't think it is neceserry. They should work > correctly even if they use different libraries, right? However, I agree that > we should minimize usage of different APIs and libraries and if we have > enough time we should switch to one library. > I must admint I haven't worked a lot with SOAP and web services at all, but > what about Apache Axis project? Could it be used instead of SOAP since I > think they said Axis project it is Apache SOAP's follow-up? > > Dejan > |
|
From: Dejan K. <dej...@nb...> - 2003-04-09 07:35:30
|
This is desirable, but I don't think it is neceserry. They should work correctly even if they use different libraries, right? However, I agree that we should minimize usage of different APIs and libraries and if we have enough time we should switch to one library. I must admint I haven't worked a lot with SOAP and web services at all, but what about Apache Axis project? Could it be used instead of SOAP since I think they said Axis project it is Apache SOAP's follow-up? Dejan > > Done. Dejan is correct here - the soap module has not been extensively tested > but I certainly think that the feeder and the pipeline should use the same > library. > |
|
From: Dejan K. <dej...@nb...> - 2003-04-09 07:07:39
|
I think I have used functions but they were called from sql statements. I haven't tried to call them directly. However, I don't think it would be a problem to implement stored procedures... Dejan ----- Original Message ----- From: ek...@ba... To: dej...@nb... Sent: Tuesday, April 08, 2003 6:18 PM Subject: Stored Procedures Quick Question: Do you know if Stored Procedures can be called from within a SQLWriter or SQLEnrich PipelineStage? ________________________________________________________________________ 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-04-09 07:03:56
|
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 145 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 25 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 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 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 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 soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 3 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 4 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 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
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 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 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 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 SUCCESSFUL
Total time: 26 seconds
|
|
From: Dejan K. <dej...@ya...> - 2003-04-08 17:25:51
|
Currently I do some bugfixes in scanner module. If I have a time I will work on crypto module, too. These module was planned to be included in project that I have been worked on. We planned to enable encryption/decryption as well as signing/verifying of messages. Unfortunately, it is not likely that we will need them (my company) soon. So until we or somebody else would really need these stuff I guess there will be issues with this module. In the next months I will help some of my colegues to implement various projects built on Babeldoc so I will do necessery bugfixes and implement needed features. So, in the short tems I will do bugfixes in scanner module and maybe test, fix and document crypto module. I will do some refactorings in other modules (no bugfixes, no features - just improve code design). I can help in documentation stuff but keep in mind that English is not my natural language. In the long terms I plan to do reimplement scanner to use Timer and TimerTask classes. I am working on it right now but this is not for 1.0 release and it need to be tested. Also, I think we will need some gui tools that will make configuration stuff easer. If people in my company found this necessery, I will probably have more time to spend on it.. Best Regards, Dejan --- Bruce McDonald <br...@mc...> wrote: > Yes but bear in mind that until we get to 1.0 we > need to be sure to > concentrate on bug fixing as opposed adding big > chunks of code. To this end, > I will be more up front about my intentions to > release code. Well, here is > my call for release 1.0 > > 1. Documentation updates (ME + anyone willing to > help) > 2. Soap updates - Hans > 3. Some more work on the module system (caching) - > ME > > What else guys? > > Bruce. > > On Tuesday 08 April 2003 08:01 am, Dejan Krsmanovic > wrote: > > Since Babeldoc community grows I suggest to be > more carefull with releasing > > new versions. All developers should be informed > before new release should > > be made. If all developers agree that new release > could be made, then Bruce > > should release new version. If somebody has more > things to fix/implement > > then we should wait until he do what he want to > do. > > This way we can prevent releasing version with > bugs that was known in the > > release time and which could be fixed. > > > > Dejan > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of > bandwidth! > No other company gives more support or power for > your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com |
|
From: Bruce M. <br...@mc...> - 2003-04-08 14:47:09
|
Great - every little bit helps. On Tuesday 08 April 2003 10:40 am, ek...@ba... wrote: > I will need to deliver a "certain level" of documentation to my management > ... it is yet undefined ... but it is on my agenda. Timeframe is unknown > now (but most likely before mid-July) ... will *most likely* include > documentation describing: > > 1. How to configure the system (i.e. properties definitions and values) > 2. Some level of Class Diagrams and possibly even Sequence Diagrams. > > I'm happy to share what I build for my management. > > Erik > > > > Sent by: bab...@li... > To: "Dejan Krsmanovic" <dej...@nb...>, "Babeldoc Developers > List" <bab...@li...> > cc: > Subject: Re: [Babeldoc-devel] An idea to prevent buggy releases > > > Yes but bear in mind that until we get to 1.0 we need to be sure to > concentrate on bug fixing as opposed adding big chunks of code. To this > end, > I will be more up front about my intentions to release code. Well, here > is > my call for release 1.0 > > 1. Documentation updates (ME + anyone willing to help) > 2. Soap updates - Hans > 3. Some more work on the module system (caching) - ME > > What else guys? > > Bruce. > > On Tuesday 08 April 2003 08:01 am, Dejan Krsmanovic wrote: > > Since Babeldoc community grows I suggest to be more carefull with > > releasing > > > new versions. All developers should be informed before new release > > should > > > be made. If all developers agree that new release could be made, then > > Bruce > > > should release new version. If somebody has more things to > > fix/implement > > > then we should wait until he do what he want to do. > > This way we can prevent releasing version with bugs that was known in > > the > > > release time and which could be fixed. > > > > Dejan > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > > ________________________________________________________________________ > 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: <ek...@ba...> - 2003-04-08 14:40:34
|
I will need to deliver a "certain level" of documentation to my management ... it is yet undefined ... but it is on my agenda. Timeframe is unknown now (but most likely before mid-July) ... will *most likely* include documentation describing: 1. How to configure the system (i.e. properties definitions and values) 2. Some level of Class Diagrams and possibly even Sequence Diagrams. I'm happy to share what I build for my management. Erik Sent by: bab...@li... To: "Dejan Krsmanovic" <dej...@nb...>, "Babeldoc Developers List" <bab...@li...> cc: Subject: Re: [Babeldoc-devel] An idea to prevent buggy releases Yes but bear in mind that until we get to 1.0 we need to be sure to concentrate on bug fixing as opposed adding big chunks of code. To this end, I will be more up front about my intentions to release code. Well, here is my call for release 1.0 1. Documentation updates (ME + anyone willing to help) 2. Soap updates - Hans 3. Some more work on the module system (caching) - ME What else guys? Bruce. On Tuesday 08 April 2003 08:01 am, Dejan Krsmanovic wrote: > Since Babeldoc community grows I suggest to be more carefull with releasing > new versions. All developers should be informed before new release should > be made. If all developers agree that new release could be made, then Bruce > should release new version. If somebody has more things to fix/implement > then we should wait until he do what he want to do. > This way we can prevent releasing version with bugs that was known in the > release time and which could be fixed. > > Dejan ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel ________________________________________________________________________ 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-04-08 14:34:13
|
Yes but bear in mind that until we get to 1.0 we need to be sure to concentrate on bug fixing as opposed adding big chunks of code. To this end, I will be more up front about my intentions to release code. Well, here is my call for release 1.0 1. Documentation updates (ME + anyone willing to help) 2. Soap updates - Hans 3. Some more work on the module system (caching) - ME What else guys? Bruce. On Tuesday 08 April 2003 08:01 am, Dejan Krsmanovic wrote: > Since Babeldoc community grows I suggest to be more carefull with releasing > new versions. All developers should be informed before new release should > be made. If all developers agree that new release could be made, then Bruce > should release new version. If somebody has more things to fix/implement > then we should wait until he do what he want to do. > This way we can prevent releasing version with bugs that was known in the > release time and which could be fixed. > > Dejan |
|
From: Bruce M. <br...@mc...> - 2003-04-08 14:24:55
|
On Tuesday 08 April 2003 09:24 am, Dejan Krsmanovic wrote: > Hans, > My opinion is that you should make your changes. soap is module that will > be used by less users than core. Also, it has not been tested a lot anyway. > So if you think we could make these things work correcty my advice is "just > do it!". > Pipeline stage and saop feeder servlet are separate parts of application > and using of first does not imply using of others. I want to say that it is > not too important that they should use same libraries if it is hard to > change servlet. > > Dejan > > P.S. > Bruce, you should add Hans to developers list. He has already done few > bugfixes and I think he will be helpful in the future, too. (Am I right, > Hans?! ;-) ) Done. Dejan is correct here - the soap module has not been extensively tested but I certainly think that the feeder and the pipeline should use the same library. > > ----- Original Message ----- > From: "Hans Benedict" <ben...@ch...> > To: "Bruce McDonald" <br...@mc...> > Cc: <bab...@li...> > Sent: Tuesday, April 08, 2003 2:50 PM > Subject: Re: [Babeldoc-devel] SOAP: missing Exceptions > > > On Mon, 7 Apr 2003, Bruce McDonald wrote: > > > Unfortunately this pipelinestage has not recieved all the attention > > > that other stages have. I would welcome suggestions as to how to > > > address these kinds of issues. > > > > Bruce, > > > > I took some time reading the sources of Apache SOAP. The http status is > > read somewhere down in org.apache.soap.util.net.HTTPUtils and then > > ignored. So it is not accessible from the point where you call > > the send method of org.apache.soap.messaging.Message. And even the > > parsing of the (html) error message of the server does not lead to an > > SOAPException. > > > > The only way I see to fix this, is to use another SOAP API. My suggestion > > is to switch to Sun's JAXM/SAAJ API, which throws a SOAPException when > > encountering an 404 error. The rewrite of the SOAPWriterPipelineStage > > should not be to difficult, but I have not yet looked at the two other > > classes. Is any of the other modules using the SOAP API? > > > > Concerning real SOAP faults, it seems that the client, i.e. the > > pipelinestage, has to check the SOAP response for them, and then throw an > > Exception by itself. > > > > If you agree, I could do the rewrite as well as the additional fault > > handling. But probably you don't want to have too many changes before the > > 1.0 release... Maybe, we should only add the fault handling and keep the > > rewrite for later? > > > > Regards, > > Hans > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: ValueWeb: > > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > > No other company gives more support or power for your dedicated server > > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Bruce M. <br...@mc...> - 2003-04-08 14:17:48
|
Hans, This is a trick question. The first thing to do is to make you a developer. I am on this now. You will have to get your SSH public key uploaded to sourceforge. Now as to the question of changing the SOAP library - heres my thinking: (This email has been written in stages) This sounds good. Thanks for you efforts here. Please make the change but bear in mind that if you change the "SOAP library" from apache's to sun's then you will have to touch other code too. You will have to be sure that you can do it all before you start a wholesale rewrite. regards, Bruce. On Tuesday 08 April 2003 08:50 am, Hans Benedict wrote: > On Mon, 7 Apr 2003, Bruce McDonald wrote: > > Unfortunately this pipelinestage has not recieved all the attention that > > other stages have. I would welcome suggestions as to how to address > > these kinds of issues. > > Bruce, > > I took some time reading the sources of Apache SOAP. The http status is > read somewhere down in org.apache.soap.util.net.HTTPUtils and then > ignored. So it is not accessible from the point where you call > the send method of org.apache.soap.messaging.Message. And even the parsing > of the (html) error message of the server does not lead to an > SOAPException. > > The only way I see to fix this, is to use another SOAP API. My suggestion > is to switch to Sun's JAXM/SAAJ API, which throws a SOAPException when > encountering an 404 error. The rewrite of the SOAPWriterPipelineStage > should not be to difficult, but I have not yet looked at the two other > classes. Is any of the other modules using the SOAP API? > > Concerning real SOAP faults, it seems that the client, i.e. the > pipelinestage, has to check the SOAP response for them, and then throw an > Exception by itself. > > If you agree, I could do the rewrite as well as the additional fault > handling. But probably you don't want to have too many changes before the > 1.0 release... Maybe, we should only add the fault handling and keep the > rewrite for later? > > Regards, > Hans |
|
From: <ek...@ba...> - 2003-04-08 14:03:13
|
For what it's worth, Hans has hit on something that I was giving serious consideration to using (but had not yet tested) ... the SOAPWriter Pipeline Stage ... it's a pity that the Apache modules "eat" the exceptions ... I'm very interested to see a more "deliverable" version of this PipelineStage. Although my management won't yet to commit to using this, I feel it will play at least a minor role in my implementation. As many of you know, my management has handed me a very tight deadline to meet my deliverable within (one reason I'm using Babeldoc) ... if time permits and Hans is not able to complete the modifications alone, I may be able to assist in this effort. Thanks. Erik Sent by: bab...@li... To: "Babeldoc Developers List" <bab...@li...> cc: Subject: Re: [Babeldoc-devel] SOAP: missing Exceptions Hans, My opinion is that you should make your changes. soap is module that will be used by less users than core. Also, it has not been tested a lot anyway. So if you think we could make these things work correcty my advice is "just do it!". Pipeline stage and saop feeder servlet are separate parts of application and using of first does not imply using of others. I want to say that it is not too important that they should use same libraries if it is hard to change servlet. Dejan P.S. Bruce, you should add Hans to developers list. He has already done few bugfixes and I think he will be helpful in the future, too. (Am I right, Hans?! ;-) ) ----- Original Message ----- From: "Hans Benedict" <ben...@ch...> To: "Bruce McDonald" <br...@mc...> Cc: <bab...@li...> Sent: Tuesday, April 08, 2003 2:50 PM Subject: Re: [Babeldoc-devel] SOAP: missing Exceptions > On Mon, 7 Apr 2003, Bruce McDonald wrote: > > > Unfortunately this pipelinestage has not recieved all the attention that > > other stages have. I would welcome suggestions as to how to address > > these kinds of issues. > > Bruce, > > I took some time reading the sources of Apache SOAP. The http status is > read somewhere down in org.apache.soap.util.net.HTTPUtils and then > ignored. So it is not accessible from the point where you call > the send method of org.apache.soap.messaging.Message. And even the parsing > of the (html) error message of the server does not lead to an > SOAPException. > > The only way I see to fix this, is to use another SOAP API. My suggestion > is to switch to Sun's JAXM/SAAJ API, which throws a SOAPException when > encountering an 404 error. The rewrite of the SOAPWriterPipelineStage > should not be to difficult, but I have not yet looked at the two other > classes. Is any of the other modules using the SOAP API? > > Concerning real SOAP faults, it seems that the client, i.e. the > pipelinestage, has to check the SOAP response for them, and then throw an > Exception by itself. > > If you agree, I could do the rewrite as well as the additional fault > handling. But probably you don't want to have too many changes before the > 1.0 release... Maybe, we should only add the fault handling and keep the > rewrite for later? > > Regards, > Hans > > > > > > > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Babeldoc-devel mailing list Bab...@li... https://lists.sourceforge.net/lists/listinfo/babeldoc-devel ________________________________________________________________________ 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-04-08 13:27:45
|
Hans, My opinion is that you should make your changes. soap is module that will be used by less users than core. Also, it has not been tested a lot anyway. So if you think we could make these things work correcty my advice is "just do it!". Pipeline stage and saop feeder servlet are separate parts of application and using of first does not imply using of others. I want to say that it is not too important that they should use same libraries if it is hard to change servlet. Dejan P.S. Bruce, you should add Hans to developers list. He has already done few bugfixes and I think he will be helpful in the future, too. (Am I right, Hans?! ;-) ) ----- Original Message ----- From: "Hans Benedict" <ben...@ch...> To: "Bruce McDonald" <br...@mc...> Cc: <bab...@li...> Sent: Tuesday, April 08, 2003 2:50 PM Subject: Re: [Babeldoc-devel] SOAP: missing Exceptions > On Mon, 7 Apr 2003, Bruce McDonald wrote: > > > Unfortunately this pipelinestage has not recieved all the attention that > > other stages have. I would welcome suggestions as to how to address > > these kinds of issues. > > Bruce, > > I took some time reading the sources of Apache SOAP. The http status is > read somewhere down in org.apache.soap.util.net.HTTPUtils and then > ignored. So it is not accessible from the point where you call > the send method of org.apache.soap.messaging.Message. And even the parsing > of the (html) error message of the server does not lead to an > SOAPException. > > The only way I see to fix this, is to use another SOAP API. My suggestion > is to switch to Sun's JAXM/SAAJ API, which throws a SOAPException when > encountering an 404 error. The rewrite of the SOAPWriterPipelineStage > should not be to difficult, but I have not yet looked at the two other > classes. Is any of the other modules using the SOAP API? > > Concerning real SOAP faults, it seems that the client, i.e. the > pipelinestage, has to check the SOAP response for them, and then throw an > Exception by itself. > > If you agree, I could do the rewrite as well as the additional fault > handling. But probably you don't want to have too many changes before the > 1.0 release... Maybe, we should only add the fault handling and keep the > rewrite for later? > > Regards, > Hans > > > > > > > > > > > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Hans B. <ben...@ch...> - 2003-04-08 12:50:35
|
On Mon, 7 Apr 2003, Bruce McDonald wrote: > Unfortunately this pipelinestage has not recieved all the attention that > other stages have. I would welcome suggestions as to how to address > these kinds of issues. Bruce, I took some time reading the sources of Apache SOAP. The http status is read somewhere down in org.apache.soap.util.net.HTTPUtils and then ignored. So it is not accessible from the point where you call the send method of org.apache.soap.messaging.Message. And even the parsing of the (html) error message of the server does not lead to an SOAPException. The only way I see to fix this, is to use another SOAP API. My suggestion is to switch to Sun's JAXM/SAAJ API, which throws a SOAPException when encountering an 404 error. The rewrite of the SOAPWriterPipelineStage should not be to difficult, but I have not yet looked at the two other classes. Is any of the other modules using the SOAP API? Concerning real SOAP faults, it seems that the client, i.e. the pipelinestage, has to check the SOAP response for them, and then throw an Exception by itself. If you agree, I could do the rewrite as well as the additional fault handling. But probably you don't want to have too many changes before the 1.0 release... Maybe, we should only add the fault handling and keep the rewrite for later? Regards, Hans |
|
From: Dejan K. <dej...@nb...> - 2003-04-08 12:04:49
|
Since Babeldoc community grows I suggest to be more carefull with releasing new versions. All developers should be informed before new release should be made. If all developers agree that new release could be made, then Bruce should release new version. If somebody has more things to fix/implement then we should wait until he do what he want to do. This way we can prevent releasing version with bugs that was known in the release time and which could be fixed. Dejan |
|
From: <br...@mc...> - 2003-04-08 07:04:53
|
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 144 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 25 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 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 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 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 soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 3 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 4 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 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
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 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 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 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 SUCCESSFUL
Total time: 31 seconds
|
|
From: Bruce M. <br...@mc...> - 2003-04-07 16:27:53
|
Ok, so this is the build that will happen every night. I guess your responsibilities is to make sure that code you committed is not breaking the build. On Monday 07 April 2003 12:25 pm, bruce wrote: > 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 144 source files to > /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build [copy] Copying > 25 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 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 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 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-IN >F [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 soap > [mkdir] Created dir: > /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build [javac] > Compiling 3 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 4 files to > /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build/soapfeed/WEB-I >NF [jar] Building jar: > /home/bruce/work/cvs-babeldoc/babeldoc_v1/build/lib/babeldoc_soapfeed.war > [copy] Copying 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build > > 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 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 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 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 SUCCESSFUL > Total time: 27 seconds > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: <br...@mc...> - 2003-04-07 16:25:37
|
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 144 source files to /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/core/build
[copy] Copying 25 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 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 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 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 soap
[mkdir] Created dir: /home/bruce/work/cvs-babeldoc/babeldoc_v1/modules/soap/build
[javac] Compiling 3 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 4 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 1 file to /home/bruce/work/cvs-babeldoc/babeldoc_v1/build
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 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 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 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 SUCCESSFUL
Total time: 27 seconds
|
|
From: Bruce M. <br...@mc...> - 2003-04-07 15:50:49
|
Great - trust Oracle to be different! Make the case changes to DDL. On Monday 07 April 2003 11:49 am, ek...@ba... wrote: > it appears that the MySql implementation of the Babeldoc logic > seems to work for Sybase. Therefore, I have not yet created any > Sybase-specific classes ... rather, I am utilizing the MySql > implementation. One thing to note ... Sybase is a case-sensitive database > .... therefore, I had to make the Sybase table names all lower-case, as > virtually all of the SQL in the system specifies it in lower-case. Some > of the database ddl was in upper case. |
|
From: <ek...@ba...> - 2003-04-07 15:49:27
|
FYI ... it appears that the MySql implementation of the Babeldoc logic seems to work for Sybase. Therefore, I have not yet created any Sybase-specific classes ... rather, I am utilizing the MySql implementation. One thing to note ... Sybase is a case-sensitive database .... therefore, I had to make the Sybase table names all lower-case, as virtually all of the SQL in the system specifies it in lower-case. Some of the database ddl was in upper case. ________________________________________________________________________ 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-04-07 13:06:16
|
Hans, Unfortunately this pipelinestage has not recieved all the attention that other stages have. I would welcome suggestions as to how to address these kinds of issues. regards, Bruce. On Monday 07 April 2003 07:55 am, Hans Benedict wrote: > Hi, > > I have just started experimenting with the SoapWriterPipelineStage. > I wanted to find out, what happens to the Messages when something goes > wrong. > > To my surprise I found, that I do not get any Exceptions when there are > HTTP Errors like 404 (e.g. due to misspelled URL) or 500 (e.g. due to > calling the wrong SOAP function: > [from the SOAP response: ...] > <env:Fault><faultcode>env:Server</faultcode><faultstring>Internal Server > Error (unrecognized operation: nitf)</faultstring></env:Fault> > [...]). > > Is this the normal behaviour? > > Btw: I *do* get an Exception when the connection is completely refused: > Error: com.babeldoc.core.pipeline.PipelineException: Error sending soap > message: Error opening socket: java.net.ConnectException: Connection > refused > > So to me it looks like org.apache.soap.messaging.Message does not throw an > Exception where I am expecting it - am I missing something? > > Regards, > Hans > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of bandwidth! > No other company gives more support or power for your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel |
|
From: Hans B. <ben...@ch...> - 2003-04-07 11:55:21
|
Hi, I have just started experimenting with the SoapWriterPipelineStage. I wanted to find out, what happens to the Messages when something goes wrong. To my surprise I found, that I do not get any Exceptions when there are HTTP Errors like 404 (e.g. due to misspelled URL) or 500 (e.g. due to calling the wrong SOAP function: [from the SOAP response: ...] <env:Fault><faultcode>env:Server</faultcode><faultstring>Internal Server Error (unrecognized operation: nitf)</faultstring></env:Fault> [...]). Is this the normal behaviour? Btw: I *do* get an Exception when the connection is completely refused: Error: com.babeldoc.core.pipeline.PipelineException: Error sending soap message: Error opening socket: java.net.ConnectException: Connection refused So to me it looks like org.apache.soap.messaging.Message does not throw an Exception where I am expecting it - am I missing something? Regards, Hans |
|
From: Dejan K. <dej...@nb...> - 2003-04-07 06:37:57
|
I agree. Dejan > All, > > I have a proposal.... > > > My linux machine here at home does the following things every 3am: > > 1. updates its code from CVS > 2. cleans and builds the codebase > 3. generates the javadoc and the rest of the documentation. > > Heres my idea: > > I can email a copy of the build results (errors, etc) to the babeldoc-devel > list so that we can all be aware of build failures and fix the errors. > > Do you think that this is a good idea? > |
|
From: Bruce M. <br...@mc...> - 2003-04-07 05:24:11
|
All, I have a proposal.... My linux machine here at home does the following things every 3am: 1. updates its code from CVS 2. cleans and builds the codebase 3. generates the javadoc and the rest of the documentation. Heres my idea: I can email a copy of the build results (errors, etc) to the babeldoc-devel list so that we can all be aware of build failures and fix the errors. Do you think that this is a good idea? regards, Bruce. |
|
From: Dejan K. <dej...@ya...> - 2003-04-05 07:56:19
|
Currently commons-logging uses log4j as underlying implementation. But you can easily switch to another logging implementation without code changes. If you remove log4j from classpath then System.out will be used. If you use jdk1.4 and have no log4j.jar in classpath then JDK1.4 logging will be used. This is default behaviour but could be changed using commons-logging.properties file.... Dejan --- ek...@ba... wrote: > Does this mean that all of the "log4j.properties" > files and all the files > that contain "log4j" properties within them are no > longer being used? > > > > > Sent by: > bab...@li... > To: bab...@li... > cc: > Subject: Re: [Babeldoc-devel] Overview of > logging > > > I think we have removed all log4j dependences from > code. Also commons-logging is used only in > LogService > now. Since commons-logging is just a wrapper for > other > logging frameworks you can use log4j, logkit, jdk > 1.4 > logging or even some proprietery framework if you > write wrapper class for it. > It seems to me that using LogService is redundant > since it is just another wrapper but changing all > calls to use commons-logging would be very hard to > do > (I tried once to do this in scanners but recently I > have returned LogService calls). > By the way, I think log configuration should be in > lib > folder not in jar file as it is now. That way > changing > debug levels (from info to debug) would be much > easer. > > > Dejan > > --- ek...@ba... wrote: > > Can I get the 25 cent / highly abridged version of > > how we do logging? > > > > I've found a few different logging classes in the > > system (log4j, > > com.babeldoc.core.LogService, Commons Logging?) > ... > > we have a customized > > logging facility (shocking, right?) that I will > need > > to feed whenever we > > encounter errors as well as to record performance > > metrics, usage, etc ... > > standard Java API. Any suggestions? > > > __________________________________________________ > Do you Yahoo!? > Yahoo! Tax Center - File online, calculators, forms, > and more > http://tax.yahoo.com > > > ------------------------------------------------------- > This SF.net email is sponsored by: ValueWeb: > Dedicated Hosting for just $79/mo with 500 GB of > bandwidth! > No other company gives more support or power for > your dedicated server > http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com |
|
From: Bruce M. <br...@mc...> - 2003-04-05 05:25:56
|
On Friday 04 April 2003 05:11 pm, ek...@ba... wrote: > Is there any reason that the "log_datetime" field is implemented as a > numeric data type (rather than Date or DateTime) in the LOG table in the > database? Yeah - it makes it easier to write the number of milliseconds from the epoch as opposed to futzing with all the different levels of support in the various databases. |
2 messages has been excluded from this view by a project administrator.
