babeldoc-devel Mailing List for Babeldoc: Universal Document Processor (Page 91)

Brought to you by: dejank, santibegue, triphop, vharcq

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

Flat | Threaded

<< < 1 .. 89 90 91 92 93 .. 122 > >> (Page 91 of 122)

[Babeldoc-devel] babeldoc/modules/core/config/i18n messages.properties,1.14,1.15

From: <tr...@us...> - 2003-08-05 23:28:32

Update of /cvsroot/babeldoc/babeldoc/modules/core/config/i18n
In directory sc8-pr-cvs1:/tmp/cvs-serv21227/config/i18n

Modified Files:
	messages.properties 
Log Message:
Now able to add arbitraty numbers of parameters to the XSL transformer thereby making the whole thing more powerful (I hope)

Index: messages.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/config/i18n/messages.properties,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15
*** messages.properties	5 Aug 2003 23:13:43 -0000	1.14
--- messages.properties	5 Aug 2003 23:28:30 -0000	1.15
***************
*** 372,376 ****
  core.pipeline.stage.enrich.desc=Adds attributes to the document.  The value can be a velocity script.
  core.pipeline.stage.filewriter.desc=Writes the document to a disk file.  The contents are written as binary or text data depending on the binary flag on the document.
! core.stage.xslTransform.desc=Transform the document (has to be XML) using this XSL script.  The script can access all of the babeldoc internals.  See the examples.
  
  core.pipeline.stage.externalapplication.description=This pipeline stage allows for external applications to be run.  Optionally the pipeline document is piped to the application.
--- 372,380 ----
  core.pipeline.stage.enrich.desc=Adds attributes to the document.  The value can be a velocity script.
  core.pipeline.stage.filewriter.desc=Writes the document to a disk file.  The contents are written as binary or text data depending on the binary flag on the document.
! 
! core.pipeline.stage.xslTransform.desc=Transform the document (has to be XML) using this XSL script.  The script can access all of the babeldoc internals via a number of parameters.  The parameters (accessed through the xsl:param element) which are always placed in the transformer are:  pipelinestage and document.  Other parameters may be placed on the transformer using the param option.
! core.pipeline.stage.xslTransform.file=The filename or URL to the XSL transformation file.  If this is a file, then the XSL will be cached.  If the file is modified, then the XSL document will be reloaded.
! core.pipeline.stage.xslTransform.script=An inline XSL document that could be used instead of the file option above.  This will be cached.
! core.pipeline.stage.xslTransform.param=Complex configuration parameter (of form stage-name.param.param-name-n=param-value) of xsl:params that will be placed in the XSL transformer.  This can significantly aid transformation tasks.
  
  core.pipeline.stage.externalapplication.description=This pipeline stage allows for external applications to be run.  Optionally the pipeline document is piped to the application.

[Babeldoc-devel] babeldoc/modules/core/src/com/babeldoc/core/config/light LightConfigCommand.java,NONE,1.1 LightConfigService.java,1.11,1.12

From: <tr...@us...> - 2003-08-05 23:13:47

Update of /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/config/light
In directory sc8-pr-cvs1:/tmp/cvs-serv17599/src/com/babeldoc/core/config/light

Modified Files:
	LightConfigService.java 
Added Files:
	LightConfigCommand.java 
Log Message:
LightConfig configuration tracing tool.

--- NEW FILE: LightConfigCommand.java ---
package com.babeldoc.core.config.light;

import com.babeldoc.core.*;
import org.apache.commons.cli.Options;
import org.apache.commons.cli.OptionBuilder;
import org.apache.commons.cli.CommandLine;

import java.net.URL;
import java.io.IOException;
import java.util.Properties;

/**
 */
public class LightConfigCommand extends BabeldocCommand{
  public static final String SPACER = "  ";

  /**
   * process the class
   *
   * @param args DOCUMENT ME!
   */
  public LightConfigCommand(String[] args) {
    super("lightconfig", I18n.get("core.config.light.command.desc"), args);
  }


  /**
   * Execute the command
   *
   * @param commandLine The command line.
   */
  public void execute(CommandLine commandLine) {
    super.execute(commandLine);

    if(commandLine.hasOption('l')) {
      String trackKey = null;
      if(commandLine.hasOption('t')) {
        trackKey = commandLine.getOptionValue('t');
      }
      listConfigFiles(commandLine.getOptionValue('l'), trackKey);
    }
  }

  /**
   * list the configuration information.
   *
   * @param configName name of the configuration file to list
   * @param trackKey option key in the configuration file to track
   */
   public void listConfigFiles(String configName, String trackKey) {

 	// NOTE: copied from LightConfigService.mergePropertiesFileFromUserSearchPath
    configName = LightConfigService.getPropertyFileName(configName);
 	// get all the 'config.properties' files that are/will be loaded
     URL[] urls = ResourceLoader.getMatchingUrlsInSearchPath(configName, EnvironmentLoader.getSearchPaths());

 	  // display the name and contents of each config file
 	  System.out.println(I18n.get("core.config.light.command.list", configName));
     for (int i = urls.length - 1; i >= 0; --i) {
       URL url = urls[i];
       System.out.println(i+": " + url);

       if(trackKey!=null) {
         Properties properties = new Properties();
         try {
           properties.load(url.openStream());
         } catch (IOException e) {
           LogService.getInstance().logError(e);
         }
         if(properties.containsKey(trackKey)) {
           System.out.println(I18n.get("core.config.light.command.defined", trackKey,
               properties.getProperty(trackKey)));
         } else {
           System.out.println(I18n.get("core.config.light.command.notdefined", trackKey));
         }
       }
     }
   }


  /**
    * setup the options on the command line.
    *
    * @param options the options to access
    */
   public void setupCommandLine(Options options) {
     super.setupCommandLine(options);

     options.addOption(OptionBuilder.isRequired().hasArg()
                                    .withDescription(I18n.get("core.config.light.command.option.l"))
                                    .withLongOpt("list").create("l"));
    options.addOption(OptionBuilder.hasArg()
                                   .withDescription(I18n.get("core.config.light.command.option.t"))
                                   .withLongOpt("track").create("t"));
  }

  /**
   * Main entry point
   *
   * @param args the name of the stage and the name=value pairs
   */
  public static void main(String[] args) {
    new LightConfigCommand(args);
  }
}

Index: LightConfigService.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/config/light/LightConfigService.java,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** LightConfigService.java	8 Jul 2003 02:46:50 -0000	1.11
--- LightConfigService.java	5 Aug 2003 23:13:44 -0000	1.12
***************
*** 126,129 ****
--- 126,146 ----
     */
    public IConfig getConfig(String name) {
+     String newname = getPropertyFileName(name);
+ 
+ //    System.out.println("Loading: "+ name);
+     Properties properties = mergePropertiesFileFromUserSearchPath(newname,
+         new Properties());
+ 
+     return new LightConfig(name, properties);
+   }
+ 
+   /**
+    * Get the name of the property file (adds properties to end of
+    * the name if necessary)
+    *
+    * @param name configuration file name
+    * @return name + .properties if necessary
+    */
+   static String getPropertyFileName(String name) {
      String newname = name;
  
***************
*** 131,140 ****
        newname += DOT_PROPERTIES;
      }
! 
!     Properties properties = new Properties();
! //    loadFromModules(newname, properties);
!     mergePropertiesFileFromUserSearchPath(newname, properties);
! 
!     return new LightConfig(name, properties);
    }
  
--- 148,152 ----
        newname += DOT_PROPERTIES;
      }
!     return newname;
    }
  
***************
*** 240,244 ****
     * @param properties
     */
!   private void mergePropertiesFileFromUserSearchPath(String name,
      Properties properties) {
      URL[] urls = ResourceLoader.getMatchingUrlsInSearchPath(name,
--- 252,256 ----
     * @param properties
     */
!   Properties mergePropertiesFileFromUserSearchPath(String name,
      Properties properties) {
      URL[] urls = ResourceLoader.getMatchingUrlsInSearchPath(name,
***************
*** 248,252 ****
        URL url = urls[i];
  
- //      System.out.println("Search path: "+url);
        try {
          properties.load(url.openStream());
--- 260,263 ----
***************
*** 255,258 ****
--- 266,270 ----
        }
      }
+     return properties;
    }
  }

[Babeldoc-devel] babeldoc/modules/core/config/i18n messages.properties,1.13,1.14

From: <tr...@us...> - 2003-08-05 23:13:47

Update of /cvsroot/babeldoc/babeldoc/modules/core/config/i18n
In directory sc8-pr-cvs1:/tmp/cvs-serv17599/config/i18n

Modified Files:
	messages.properties 
Log Message:
LightConfig configuration tracing tool.

Index: messages.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/config/i18n/messages.properties,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -d -r1.13 -r1.14
*** messages.properties	27 Jun 2003 03:36:21 -0000	1.13
--- messages.properties	5 Aug 2003 23:13:43 -0000	1.14
***************
*** 388,390 ****
  core.module.command.option.create=Create the module cache (redundant)
  core.module.command.option.delete=Delete the module cache (redundant)
! core.module.command.list.output=Module: {0} is dependant on: {1}
\ No newline at end of file
--- 388,399 ----
  core.module.command.option.create=Create the module cache (redundant)
  core.module.command.option.delete=Delete the module cache (redundant)
! core.module.command.list.output=Module: {0} is dependant on: {1}
! 
! core.config.light.command.desc=Debug and track aspects of the light configuration
! core.config.light.command.list=Listing urls for the configuration: {0}
! core.config.light.command.defined=   {0}={1}
! core.config.light.command.notdefined=   {0} not (re)defined
! core.config.light.command.option.l=List all implementing configuration files for config
! core.config.light.command.option.t=Track a configuration value through all the configuration files
! 
!

[Babeldoc-devel] babeldoc/modules/core/config/service query.properties,1.9,1.10

From: <tr...@us...> - 2003-08-05 23:13:47

Update of /cvsroot/babeldoc/babeldoc/modules/core/config/service
In directory sc8-pr-cvs1:/tmp/cvs-serv17599/config/service

Modified Files:
	query.properties 
Log Message:
LightConfig configuration tracing tool.

Index: query.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/config/service/query.properties,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** query.properties	16 Jul 2003 22:45:26 -0000	1.9
--- query.properties	5 Aug 2003 23:13:44 -0000	1.10
***************
*** 19,23 ****
  PipelineStage.ZipArchiveWriter=com.babeldoc.core.pipeline.stage.ZipArchiveWriterPipelineStage
  PipelineStage.CallStage=com.babeldoc.core.pipeline.stage.CallStagePipelineStage
! PipelineStage.ExternalApplication=com.babeldoc.core.pipeline.stage.ExternalApplication
  
  Journal.simple=com.babeldoc.core.journal.simple.SimpleJournal
--- 19,23 ----
  PipelineStage.ZipArchiveWriter=com.babeldoc.core.pipeline.stage.ZipArchiveWriterPipelineStage
  PipelineStage.CallStage=com.babeldoc.core.pipeline.stage.CallStagePipelineStage
! PipelineStage.ExternalApplication=com.babeldoc.core.pipeline.stage.ExternalApplicationPipelineStage
  
  Journal.simple=com.babeldoc.core.journal.simple.SimpleJournal
***************
*** 32,35 ****
--- 32,36 ----
  Command.process=com.babeldoc.core.pipeline.command.PipelineFeeder
  Command.module=com.babeldoc.core.module.BabeldocModuleCommand
+ Command.lightconfig=com.babeldoc.core.config.light.LightConfigCommand
  
  UserResourceFactory.simple=com.babeldoc.core.user.simple.SimpleResourceFactory
***************
*** 38,44 ****
  Feeder.asynchronous=com.babeldoc.core.pipeline.feeder.AsynchronousFeeder
  
! 
! 
! PipelineStageProcessor.sync=com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor
  PipelineStageProcessor.async=com.babeldoc.core.pipeline.processor.AsyncPipelineStageProcessor
  PipelineStageProcessor.threadpool=com.babeldoc.core.pipeline.processor.ThreadPooledPipelineStageProcessor
--- 39,43 ----
  Feeder.asynchronous=com.babeldoc.core.pipeline.feeder.AsynchronousFeeder
  
! PipelineStageProcessor.sync=com.babeldoc.core.pipeline.processor.SyncPipelineStageProcessor
  PipelineStageProcessor.async=com.babeldoc.core.pipeline.processor.AsyncPipelineStageProcessor
  PipelineStageProcessor.threadpool=com.babeldoc.core.pipeline.processor.ThreadPooledPipelineStageProcessor

RE: [Babeldoc-devel] Config file dump committed; questions for completing

From: McDonald, B. <Bru...@ba...> - 2003-08-05 19:06:00

David,

You have to specify the -l switch.  If you do not, it complains and dies. 
Looking at your code, I see that it searches for the file:

URL[] urls = ResourceLoader.getMatchingUrlsInSearchPath("env/config.properties",
        EnvironmentLoader.getSearchPaths());

env/config.properties and nothing else.

Not sure how to search all configuration files.  It really would represent a lot of information.


Regards,
Bruce.

------
Moving strings into the resource bundle.

There are two kinds of string:  those with arguments and those without.  For this purpose lets look at the those with arguments:

System.out.println("Filename: "+fileName+" is broken beyond repair");

Now, lets say that we needed to represent this as a resource bundle string and that this existed in the conversion module.

Well, open the modules/conversion/config/i18n/messages.properties file

and add a property:

conversion.bad.broke=Filename: {0} is broken beyond repair

Then goto the code that does the println, and convert the literal string to:

System.out.println(I18n.get("conversion.bad.broke", filename));

And all is done.  Notice that the class I18n has the method get overloaded manytimes to cater to lots of additional arguments.  



-----Original Message-----
From: David Glick [mailto:dg...@co...]
Sent: Tuesday, August 05, 2003 2:01 PM
To: McDonald, Bruce; bab...@li...
Subject: Re: [Babeldoc-devel] Config file dump committed; questions for
completing


Okay, I understand how you're using it, and I think I can make it work for my 
scenario.  If the '-l' and '-t' switches aren't present, does it default to 
the original functionality, e..g list all config files and their contents?

Also, I had intended for the '-d' switch to be available for all modules to 
output appropriate debug information.  For example, a soap writer might dump 
the soap envelope and all the protocol packets.  This can also be 
accomplished, I suppose, by increasing (decreasing?  I always get confused 
which way it goes to show more info) the logging level; is there currently a 
way to set the log level on the command line?

Also, I still don't understand how to move hard-coded strings into the 
resource bundles...?


Thanks,

David




On Tuesday 05 August 2003 10:34 am, McDonald, Bruce wrote:
> David,
>
> Interesting - I did not think of that but still I think that it will
> probably be just as useful.  Here is a usage scenario:
>
> Lets say that the configuration 'pipeline/config' is somehow broken and we
> need to track the configuration key, documentation.type, the command:
>
> C:\work\vap_rpt>babeldoc lightconfig -l pipeline/config -t
> documentation.type Listing urls for the configuration:
> pipeline/config.properties
> 1:
> jar:file:/c:/download/babeldoc/build/lib/babeldoc_core.jar!/core/pipeline/c
>onfig.properties documentation.type = simple
> 0: file:/C:/work/vap_rpt/./pipeline/config.properties
>   documentation.type Not defined
>
>
>
> This tells me that the file pipeline/config.properties appears twice in the
> configuration and the configuration key, documentation.type is defined in
> the first configuration only and its value is simple.
>
> regards,
> Bruce.
>
> -----Original Message-----
> From: David Glick [mailto:dg...@co...]
> Sent: Tuesday, August 05, 2003 1:39 PM
> To: McDonald, Bruce; bab...@li...
> Subject: Re: [Babeldoc-devel] Config file dump committed; questions for
> completing
>
>
> Yeah, that's just what I had planned for rev 2... :-)
>
> I like your additional functionality, but I'm unclear as to what the
> advantage is of changing it from a command line switch into a separate
> command.  I had assumed that this would be most useful in conjunction with
> another command that was not operating the way you expected.  I therefore
> intended for this switch to be added to the original command line so that
> you could re-run it and determine if the problem was in the configuration,
> or elsewhere.  If it is now a separate command, how will be above scenario
> play out?
>
>
> David
>
> On Tuesday 05 August 2003 10:05 am, McDonald, Bruce wrote:
> > David,
> >
> > I am spending some time with this tool.
> >
> > Heres what I have done so far:
> >
> > 1.  Extracted the code into a new command:  lightconfig
> > 2.  Added another parameter (-t) which tracks a configuration value.  It
> > will indicate those files that override the configuration value.
> >
> > regards,
> > Bruce.
> >
> > -----Original Message-----
> > From: David Glick [mailto:dg...@co...]
> > Sent: Tuesday, August 05, 2003 11:15 AM
> > To: bab...@li...
> > Subject: [Babeldoc-devel] Config file dump committed; questions for
> > completing
> >
> >
> > Hi Bruce,
> >
> > I've committed my changes to dump the configuration files and contents.
> > Hopefully, the following questions will make sense:
> >
> > 1. In the setupCommandLine() method, I've hard-coded the description
> > string. I believe it should be changed into a reference key into the
> > resource bundles (as the other description strings are in the same
> > method), but I'm not sure if there is a formal way to do so.  How do I
> > assign the appropriate resource key?
> >
> > 2. I added a method printConfigInfo().  It also has a hard-coded string
> > that should be changed.  Same question as in #1 above.
> >
> > 3. Should the new '-d' option be added to the printUsage() method?  It
> > wasn't clear to me where it actually should be put.
> >
> >
> > Thanks,
> >
> > David

-- 
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...

Re: [Babeldoc-devel] Config file dump committed; questions for completing

From: David G. <dg...@co...> - 2003-08-05 18:08:48

Okay, I understand how you're using it, and I think I can make it work for my 
scenario.  If the '-l' and '-t' switches aren't present, does it default to 
the original functionality, e..g list all config files and their contents?

Also, I had intended for the '-d' switch to be available for all modules to 
output appropriate debug information.  For example, a soap writer might dump 
the soap envelope and all the protocol packets.  This can also be 
accomplished, I suppose, by increasing (decreasing?  I always get confused 
which way it goes to show more info) the logging level; is there currently a 
way to set the log level on the command line?

Also, I still don't understand how to move hard-coded strings into the 
resource bundles...?


Thanks,

David




On Tuesday 05 August 2003 10:34 am, McDonald, Bruce wrote:
> David,
>
> Interesting - I did not think of that but still I think that it will
> probably be just as useful.  Here is a usage scenario:
>
> Lets say that the configuration 'pipeline/config' is somehow broken and we
> need to track the configuration key, documentation.type, the command:
>
> C:\work\vap_rpt>babeldoc lightconfig -l pipeline/config -t
> documentation.type Listing urls for the configuration:
> pipeline/config.properties
> 1:
> jar:file:/c:/download/babeldoc/build/lib/babeldoc_core.jar!/core/pipeline/c
>onfig.properties documentation.type = simple
> 0: file:/C:/work/vap_rpt/./pipeline/config.properties
>   documentation.type Not defined
>
>
>
> This tells me that the file pipeline/config.properties appears twice in the
> configuration and the configuration key, documentation.type is defined in
> the first configuration only and its value is simple.
>
> regards,
> Bruce.
>
> -----Original Message-----
> From: David Glick [mailto:dg...@co...]
> Sent: Tuesday, August 05, 2003 1:39 PM
> To: McDonald, Bruce; bab...@li...
> Subject: Re: [Babeldoc-devel] Config file dump committed; questions for
> completing
>
>
> Yeah, that's just what I had planned for rev 2... :-)
>
> I like your additional functionality, but I'm unclear as to what the
> advantage is of changing it from a command line switch into a separate
> command.  I had assumed that this would be most useful in conjunction with
> another command that was not operating the way you expected.  I therefore
> intended for this switch to be added to the original command line so that
> you could re-run it and determine if the problem was in the configuration,
> or elsewhere.  If it is now a separate command, how will be above scenario
> play out?
>
>
> David
>
> On Tuesday 05 August 2003 10:05 am, McDonald, Bruce wrote:
> > David,
> >
> > I am spending some time with this tool.
> >
> > Heres what I have done so far:
> >
> > 1.  Extracted the code into a new command:  lightconfig
> > 2.  Added another parameter (-t) which tracks a configuration value.  It
> > will indicate those files that override the configuration value.
> >
> > regards,
> > Bruce.
> >
> > -----Original Message-----
> > From: David Glick [mailto:dg...@co...]
> > Sent: Tuesday, August 05, 2003 11:15 AM
> > To: bab...@li...
> > Subject: [Babeldoc-devel] Config file dump committed; questions for
> > completing
> >
> >
> > Hi Bruce,
> >
> > I've committed my changes to dump the configuration files and contents.
> > Hopefully, the following questions will make sense:
> >
> > 1. In the setupCommandLine() method, I've hard-coded the description
> > string. I believe it should be changed into a reference key into the
> > resource bundles (as the other description strings are in the same
> > method), but I'm not sure if there is a formal way to do so.  How do I
> > assign the appropriate resource key?
> >
> > 2. I added a method printConfigInfo().  It also has a hard-coded string
> > that should be changed.  Same question as in #1 above.
> >
> > 3. Should the new '-d' option be added to the printUsage() method?  It
> > wasn't clear to me where it actually should be put.
> >
> >
> > Thanks,
> >
> > David

-- 
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...

RE: [Babeldoc-devel] Config file dump committed; questions for completing

From: McDonald, B. <Bru...@ba...> - 2003-08-05 17:35:30

David,

Interesting - I did not think of that but still I think that it will probably be just as useful.  Here is a usage scenario:

Lets say that the configuration 'pipeline/config' is somehow broken and we need to track the configuration key, documentation.type, the command:

C:\work\vap_rpt>babeldoc lightconfig -l pipeline/config -t documentation.type
Listing urls for the configuration: pipeline/config.properties
1: jar:file:/c:/download/babeldoc/build/lib/babeldoc_core.jar!/core/pipeline/config.properties
  documentation.type = simple
0: file:/C:/work/vap_rpt/./pipeline/config.properties
  documentation.type Not defined

This tells me that the file pipeline/config.properties appears twice in the configuration and the configuration key, documentation.type is defined in the first configuration only and its value is simple.

regards,
Bruce.

-----Original Message-----
From: David Glick [mailto:dg...@co...]
Sent: Tuesday, August 05, 2003 1:39 PM
To: McDonald, Bruce; bab...@li...
Subject: Re: [Babeldoc-devel] Config file dump committed; questions for
completing

Yeah, that's just what I had planned for rev 2... :-)

I like your additional functionality, but I'm unclear as to what the advantage 
is of changing it from a command line switch into a separate command.  I had 
assumed that this would be most useful in conjunction with another command 
that was not operating the way you expected.  I therefore intended for this 
switch to be added to the original command line so that you could re-run it 
and determine if the problem was in the configuration, or elsewhere.  If it 
is now a separate command, how will be above scenario play out?

David

On Tuesday 05 August 2003 10:05 am, McDonald, Bruce wrote:
> David,
>
> I am spending some time with this tool.
>
> Heres what I have done so far:
>
> 1.  Extracted the code into a new command:  lightconfig
> 2.  Added another parameter (-t) which tracks a configuration value.  It
> will indicate those files that override the configuration value.
>
> regards,
> Bruce.
>
> -----Original Message-----
> From: David Glick [mailto:dg...@co...]
> Sent: Tuesday, August 05, 2003 11:15 AM
> To: bab...@li...
> Subject: [Babeldoc-devel] Config file dump committed; questions for
> completing
>
>
> Hi Bruce,
>
> I've committed my changes to dump the configuration files and contents.
> Hopefully, the following questions will make sense:
>
> 1. In the setupCommandLine() method, I've hard-coded the description
> string. I believe it should be changed into a reference key into the
> resource bundles (as the other description strings are in the same method),
> but I'm not sure if there is a formal way to do so.  How do I assign the
> appropriate resource key?
>
> 2. I added a method printConfigInfo().  It also has a hard-coded string
> that should be changed.  Same question as in #1 above.
>
> 3. Should the new '-d' option be added to the printUsage() method?  It
> wasn't clear to me where it actually should be put.
>
>
> Thanks,
>
> David

-- 
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...

Re: [Babeldoc-devel] Config file dump committed; questions for completing

From: David G. <dg...@co...> - 2003-08-05 17:28:05

Yeah, that's just what I had planned for rev 2... :-)

I like your additional functionality, but I'm unclear as to what the advantage 
is of changing it from a command line switch into a separate command.  I had 
assumed that this would be most useful in conjunction with another command 
that was not operating the way you expected.  I therefore intended for this 
switch to be added to the original command line so that you could re-run it 
and determine if the problem was in the configuration, or elsewhere.  If it 
is now a separate command, how will be above scenario play out?


David


On Tuesday 05 August 2003 10:05 am, McDonald, Bruce wrote:
> David,
>
> I am spending some time with this tool.
>
> Heres what I have done so far:
>
> 1.  Extracted the code into a new command:  lightconfig
> 2.  Added another parameter (-t) which tracks a configuration value.  It
> will indicate those files that override the configuration value.
>
> regards,
> Bruce.
>
> -----Original Message-----
> From: David Glick [mailto:dg...@co...]
> Sent: Tuesday, August 05, 2003 11:15 AM
> To: bab...@li...
> Subject: [Babeldoc-devel] Config file dump committed; questions for
> completing
>
>
> Hi Bruce,
>
> I've committed my changes to dump the configuration files and contents.
> Hopefully, the following questions will make sense:
>
> 1. In the setupCommandLine() method, I've hard-coded the description
> string. I believe it should be changed into a reference key into the
> resource bundles (as the other description strings are in the same method),
> but I'm not sure if there is a formal way to do so.  How do I assign the
> appropriate resource key?
>
> 2. I added a method printConfigInfo().  It also has a hard-coded string
> that should be changed.  Same question as in #1 above.
>
> 3. Should the new '-d' option be added to the printUsage() method?  It
> wasn't clear to me where it actually should be put.
>
>
> Thanks,
>
> David

-- 
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...

RE: [Babeldoc-devel] Config file dump committed; questions for completing

From: McDonald, B. <Bru...@ba...> - 2003-08-05 17:06:38

David,

I am spending some time with this tool.

Heres what I have done so far:

1.  Extracted the code into a new command:  lightconfig
2.  Added another parameter (-t) which tracks a configuration value.  It will indicate those files that override the configuration value.

regards,
Bruce.

-----Original Message-----
From: David Glick [mailto:dg...@co...]
Sent: Tuesday, August 05, 2003 11:15 AM
To: bab...@li...
Subject: [Babeldoc-devel] Config file dump committed; questions for
completing


Hi Bruce,

I've committed my changes to dump the configuration files and contents.  
Hopefully, the following questions will make sense:

1. In the setupCommandLine() method, I've hard-coded the description string.  
I believe it should be changed into a reference key into the resource bundles 
(as the other description strings are in the same method), but I'm not sure 
if there is a formal way to do so.  How do I assign the appropriate resource 
key?

2. I added a method printConfigInfo().  It also has a hard-coded string that 
should be changed.  Same question as in #1 above.

3. Should the new '-d' option be added to the printUsage() method?  It wasn't 
clear to me where it actually should be put.


Thanks,

David

-- 
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Babeldoc-devel mailing list
Bab...@li...
https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

AW: [Babeldoc-devel] SqlWriter stage

From: Stefan K. <ste...@co...> - 2003-08-05 16:28:33

Well, transaction control in the stage is only useful in unmanaged
environments.
I would like to have this feature configurable. This would allow the use of
this stage in J2EE environments with container managed transactions. At the
moment this is not possible.

Regards,
Stefan

-----Ursprüngliche Nachricht-----
Von: bab...@li...
[mailto:bab...@li...]Im Auftrag von Leech,
Jonathan
Gesendet: Montag, 4. August 2003 16:31
An: 'Dejan Krsmanovic'; bab...@li...
Betreff: RE: [Babeldoc-devel] SqlWriter stage

I didn't notice that you can control transaction rollback - that's a great
feature to have.  I'll also take a look at the batch capability.  I'll let
you know if I have any ideas.

-Jonathan

-----Original Message-----
From: Dejan Krsmanovic [mailto:dej...@ya...]
Sent: Sunday, August 03, 2003 11:03 AM
To: bab...@li...
Subject: [Babeldoc-devel] SqlWriter stage

--- "Leech, Jonathan" <jl...@vi...> wrote:
> Incidentally, I modified my pipeline configuration
> from this:
> XPathSplitter->XPathExtractor->SqlWriter
> to this:
> XslTransform->SqlWriter
> and it really flies.  So I used to split up the XML,
> extract values from it,
> then write each row to the database.  Now I just
> transform the XML into a
> bunch of SQL statements and run them.  Its much
> faster and it might be a
> good pattern in general.
>
> -Jonathan

I did the same thing in pipeline configuration for one
of projects I have been working on. In fact I wrote
SqlWriter stage for that purpose. Since I had to
manage few other problems I have introduced few
properties that might be confusing at first. For
example, you can define messages that should be
returned in case of error instead of returning
database error message. I guess you have noticed that
you can control wether transaciton should be rolled
back on first error or after all statements are
executed. This was important for my project. You can
also use batch statements altough I haven't noticed
some improvements in my project when using batch
statements with different batch sizes (I am using
Oracle database).

If you have some other ideas how to improve or
simplify this class I would be glad to hear.

Dejan

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Babeldoc-devel mailing list
Bab...@li...
https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Babeldoc-devel mailing list
Bab...@li...
https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

[Babeldoc-devel] Config file dump committed; questions for completing

From: David G. <dg...@co...> - 2003-08-05 15:03:54

Hi Bruce,

I've committed my changes to dump the configuration files and contents.  
Hopefully, the following questions will make sense:

1. In the setupCommandLine() method, I've hard-coded the description string.  
I believe it should be changed into a reference key into the resource bundles 
(as the other description strings are in the same method), but I'm not sure 
if there is a formal way to do so.  How do I assign the appropriate resource 
key?

2. I added a method printConfigInfo().  It also has a hard-coded string that 
should be changed.  Same question as in #1 above.

3. Should the new '-d' option be added to the printUsage() method?  It wasn't 
clear to me where it actually should be put.


Thanks,

David

-- 
David Glick
Transmit Consulting, Inc
619-475-4052
dg...@tr...

[Babeldoc-devel] babeldoc/modules/core/src/com/babeldoc/core BabeldocCommand.java,1.12,1.13

From: <dgl...@us...> - 2003-08-05 14:55:46

Update of /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core
In directory sc8-pr-cvs1:/tmp/cvs-serv25987/modules/core/src/com/babeldoc/core

Modified Files:
	BabeldocCommand.java 
Log Message:
Added '-d' switch for dumping configuration files and contents

Index: BabeldocCommand.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/BabeldocCommand.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** BabeldocCommand.java	27 Jun 2003 02:19:57 -0000	1.12
--- BabeldocCommand.java	5 Aug 2003 14:55:41 -0000	1.13
***************
*** 66,69 ****
--- 66,74 ----
  package com.babeldoc.core;
  
+ import java.io.BufferedReader;
+ import java.io.IOException;
+ import java.io.InputStreamReader;
+ import java.net.URL;
+ 
  import com.babeldoc.core.config.ConfigService;
  
***************
*** 164,167 ****
--- 169,175 ----
        setVerbose(true);
      }
+     else if (commandLine.hasOption('d')) {
+     	printConfigInfo();
+     }
    }
  
***************
*** 189,192 ****
--- 197,233 ----
  
    /**
+    * print configuration info
+    */
+   public void printConfigInfo() {
+ 
+ 	// NOTE: copied from LightConfigService.mergePropertiesFileFromUserSearchPath
+ 
+ 	// get all the 'config.properties' files that are/will be loaded
+     URL[] urls = ResourceLoader.getMatchingUrlsInSearchPath("env/config.properties",
+         EnvironmentLoader.getSearchPaths());
+ 
+ 	// display the name and contents of each config file
+ 	System.out.println("Showing configuration files and contents:");
+     for (int i = urls.length - 1; i >= 0; --i) {
+       URL url = urls[i];
+       System.out.println(" === " + url + " ===");
+ 
+       try {
+       	BufferedReader reader = new BufferedReader(new InputStreamReader(url.openStream()));
+       	String line;
+       	do {
+       		line = reader.readLine();
+       		if (line != null) {
+       			System.out.println(line);
+       		}
+       	}
+       	while (line != null);
+       } catch (IOException e) {
+         LogService.getInstance().logError(e);
+       }
+     }
+   }
+ 
+   /**
     * setup the options on the command line.
     *
***************
*** 194,200 ****
     */
    public void setupCommandLine(Options options) {
!     options.addOption("v", "verbose", false,
!       com.babeldoc.core.I18n.get("001002"));
!     options.addOption("h", "help", false, com.babeldoc.core.I18n.get("001003"));
    }
  
--- 235,241 ----
     */
    public void setupCommandLine(Options options) {
!     options.addOption("v", "verbose", false, com.babeldoc.core.I18n.get("001002"));
!     options.addOption("h", "help"   , false, com.babeldoc.core.I18n.get("001003"));
!     options.addOption("d", "debug"  , false, "Write config info to stdout");
    }