babeldoc-devel — Babeldoc developer list

Re: [Babeldoc-devel] Using Journal to monitor status...?

[David G. <dg...@co...>]

Ah!  That was the clue I needed.  I had tried several XML editors, and none 
would work with chapter 2.  By commenting out the lines beginning with an '&' 
as Dejan indicated, all the editors could work with it (note that I also took 
Bruce's suggestion of 'vi' in order to comment out the lines...).

FYI, I'm using XMLmind because it seems to be the closest to a true WYSIWYG 
editor.  I'll let you know if I change my mind later...


David

On Friday 15 August 2003 1:02 pm, Dejan Krsmanovic wrote:
> Try OpenOffice 1.1. It supports "simplified DocBook".
> However, I could use it with our documents except two
> chapters that conatins generated documentation. You
> should manualy remove &scanners or &stages from the
> file and then you can use OpenOffice. When you finish
> editig just return it back.
>
> Dejan
>
> --- David Glick <dg...@co...> wrote:
> > Thanks, Bruce.  Throwing an exception in a Script
> > stage gives me exactly what
> > I need.  FYI, it seems that the logic for
> > failOnError is exactly the opposite
> > as described in the Users Guide, in that my testing
> > seems to indicate that it
> > defaults to true unless explicitly set to false.
> >
> > Speaking of the Users Guide, I'm having an
> > interesting time finding something
> > that will allow me to edit the docbook file in a
> > WYSIWYG format.  Being new
> > to docbook, can I ask what you use (preferably Java
> > or Linux-based)?
> >
> >
> > Thanks again,
> >
> > David
> >
> > On Friday 15 August 2003 11:12 am, McDonald, Bruce
> >
> > wrote:
> > > All seems good - In in specialized processing like
> >
> > this - The Scripting
> >
> > > stage is your friend.
> > >
> > >
> > > See comments inline:
> > >
> > > 1. I understand that a stage that fails will force
> >
> > a FAIL status.  However,
> >
> > > what I'm trying to do is force a FAIL status when
> >
> > a stage completes
> >
> > > successfully, but the application detects an
> >
> > error.  For example, in my
> >
> > > case I post SOAP messages, and if the response is
> >
> > a SOAPFAULT, I want to
> >
> > > force an error into the journal and stop the
> >
> > pipeline processing.  My
> >
> > > question is: can I do this via a script stage (and
> >
> > if so, how), or must I
> >
> > > create a new stage type to support it?
> > >
> > >
> > > If you throw an exception from the pipelinestage -
> >
> > that stage will write a
> >
> > > failed to the journal.  You might need to expand
> >
> > the SoapWriter stage and
> >
> > > add a config option like 'failOnFault' (default
> >
> > false) to do this. <<<<
> >
> > > 2. I also understand about setting the 'tracked'
> >
> > attribute for the stages.
> >
> > > The question I have regards the use of the journal
> >
> > tool.  Using it to view
> >
> > > entries, is there any indication that a particular
> >
> > entry in the journal
> >
> > > contains a tracked document?  The reason is that,
> >
> > in the case of a failure,
> >
> > > I expect the operator to do the following:
> > >
> > > a. View the journal entries to determine which
> >
> > stage failed.
> >
> > > b. Correct the cause of the failure.
> > > c. Assuming the problem was not due to the
> >
> > document, replay the journal
> >
> > > from the stage that failed.  If the particular
> >
> > stage that failed is not
> >
> > > tracking the document, I assume he will need to
> >
> > find the closest previous
> >
> > > stage that has a document associated with it, and
> >
> > replay it from that
> >
> > > point.  If this is correct, he'll need some way to
> >
> > determine which stage to
> >
> > > use.  If this is not correct, how should I be
> >
> > using the replay
> >
> > > functionality?
> > >
> > >
> > > YOu might need to write a specialized journal view
> >
> > to do this.  I am not
> >
> > > sure if the default tools support this. <<<<
> > >
> > > Thanks again for your help,
> > >
> > > David
> > >
> > > On Friday 15 August 2003 12:05 am, Dejan
> >
> > Krsmanovic wrote:
> > > > Hi David,
> > > >
> > > > > Hello to the Great and Powerful List,
> > > > >
> > > > > I would like to use the journal to track all
> >
> > documents through the
> >
> > > > > system.
> > > >
> > > > In
> > > >
> > > > > order to do this, I'll need to do the
> >
> > following:
> > > > > 1. If I encounter an application error, I'd
> >
> > like to force a FAIL status
> >
> > > > into
> > > >
> > > > > the Journal, with an appropriate error
> >
> > message.  Is there a way to do
> >
> > > > this?
> > > >
> > > > All pipeline stages by default forces FAIL
> >
> > status in case of error. Also,
> >
> > > > processing
> > > > is stopped in case of error. This can be changed
> >
> > using errorStage and
> >
> > > > failOnError
> > > > config options. I think there is a section about
> >
> > this is User Guide.
> >
> > > > > 2. I'll be using pretty large documents for
> >
> > some of my operations, so I
> >
> > > > don't
> > > >
> > > > > want to track it in every stage; only those
> >
> > stages where it will be
> >
> > > > > transformed in some way.  Is there anyway to
> >
> > know from the journal
> >
> > > > > which stages track document?  This will
> >
> > simplify things once I turn
> >
> > > > > over
> > > >
> > > > monitoring
> > > >
> > > > > of the system to the client.
> > > >
> > > > By default documents are NOT tracked. If you
> >
> > want to track documents you
> >
> > > > should
> > > > use tracked config option which is false by
> >
> > default
> >
> > > > > 3. Also, is the document tracked on entry to
> >
> > the stage or on exit from
> >
> > > > > it?
> > > >
> > > > In
> > > >
> > > > > other words, is tracking saving the document
> >
> > before any transformation
> >
> > > > > is applied by the stage, or after it's
> >
> > transformed?
> >
> > > > Before.
> > > >
> > > > > 4. I would like to organize pipeline fragments
> >
> > to operate as
> >
> > > > > subroutines
> > > >
> > > > that
> > > >
> > > > > can be called by multiple stages, which I
> >
> > believe that I can now do
> >
> > > > > with
> > > >
> > > > the
> > > >
> > > > > updated CallStage functionality.  I would also
> >
> > like to place these
> >
> > > > fragments
> > > >
> > > > > in a separate file so that I can use them in
> >
> > multiple pipeline
> >
> > > > > configurations.  Can this be done?
> > > >
> > > > This should be possible now, right Bruce? Bruce
> >
> > and I have discussion
> >
> > > > about that few
> > > > months ago and I think he has implemented it. I
> >
> > havent used it so I am
> >
> > > > not sure if it is working.
> > > >
> > > >
> > > > Dejan
> > > >
> > > > > Thanks,
> > > > >
> > > > > David
> > > > >
> > > > > --
> > > > > David Glick
> > > > > Transmit Consulting, Inc
> > > > > 619-475-4052
> > > > > dg...@tr...
>
> === message truncated ===
>
>
> __________________________________
> 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

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

RE: [Babeldoc-devel] Using Journal to monitor status...?

[McDonald, B. <Bru...@ba...>]

Kidding :)

Check this out:
http://www.oxygenxml.com/  (non-free)
 
or this:
http://kxmleditor.sourceforge.net/ (free / kde)

regards,
Bruce.

-----Original Message-----
From: David Glick [mailto:dg...@co...]
Sent: Friday, August 15, 2003 3:55 PM
To: McDonald, Bruce; bab...@li...
Subject: Re: [Babeldoc-devel] Using Journal to monitor status...?


Well, I can certainly run vi on Linux...

On Friday 15 August 2003 12:42 pm, McDonald, Bruce wrote:
> vi :)
>
> -----Original Message-----
> From: David Glick [mailto:dg...@co...]
> Sent: Friday, August 15, 2003 3:36 PM
> To: McDonald, Bruce; bab...@li...
> Subject: Re: [Babeldoc-devel] Using Journal to monitor status...?
>
>
> Thanks, Bruce.  Throwing an exception in a Script stage gives me exactly
> what I need.  FYI, it seems that the logic for failOnError is exactly the
> opposite as described in the Users Guide, in that my testing seems to
> indicate that it defaults to true unless explicitly set to false.
>
> Speaking of the Users Guide, I'm having an interesting time finding
> something that will allow me to edit the docbook file in a WYSIWYG format. 
> Being new to docbook, can I ask what you use (preferably Java or
> Linux-based)?
>
>
> Thanks again,
>
> David
>
> On Friday 15 August 2003 11:12 am, McDonald, Bruce wrote:
> > All seems good - In in specialized processing like this - The Scripting
> > stage is your friend.
> >
> >
> > See comments inline:
> >
> > 1. I understand that a stage that fails will force a FAIL status. 
> > However, what I'm trying to do is force a FAIL status when a stage
> > completes successfully, but the application detects an error.  For
> > example, in my case I post SOAP messages, and if the response is a
> > SOAPFAULT, I want to force an error into the journal and stop the
> > pipeline processing.  My question is: can I do this via a script stage
> > (and if so, how), or must I create a new stage type to support it?
> >
> >
> > If you throw an exception from the pipelinestage - that stage will write
> > a failed to the journal.  You might need to expand the SoapWriter stage
> > and add a config option like 'failOnFault' (default false) to do this.
> > <<<<
> >
> >
> > 2. I also understand about setting the 'tracked' attribute for the
> > stages. The question I have regards the use of the journal tool.  Using
> > it to view entries, is there any indication that a particular entry in
> > the journal contains a tracked document?  The reason is that, in the case
> > of a failure, I expect the operator to do the following:
> >
> > a. View the journal entries to determine which stage failed.
> > b. Correct the cause of the failure.
> > c. Assuming the problem was not due to the document, replay the journal
> > from the stage that failed.  If the particular stage that failed is not
> > tracking the document, I assume he will need to find the closest previous
> > stage that has a document associated with it, and replay it from that
> > point.  If this is correct, he'll need some way to determine which stage
> > to use.  If this is not correct, how should I be using the replay
> > functionality?
> >
> >
> > YOu might need to write a specialized journal view to do this.  I am not
> > sure if the default tools support this. <<<<
> >
> > Thanks again for your help,
> >
> > David
> >
> > On Friday 15 August 2003 12:05 am, Dejan Krsmanovic wrote:
> > > Hi David,
> > >
> > > > Hello to the Great and Powerful List,
> > > >
> > > > I would like to use the journal to track all documents through the
> > > > system.
> > >
> > > In
> > >
> > > > order to do this, I'll need to do the following:
> > > >
> > > > 1. If I encounter an application error, I'd like to force a FAIL
> > > > status
> > >
> > > into
> > >
> > > > the Journal, with an appropriate error message.  Is there a way to do
> > >
> > > this?
> > >
> > > All pipeline stages by default forces FAIL status in case of error.
> > > Also, processing
> > > is stopped in case of error. This can be changed using errorStage and
> > > failOnError
> > > config options. I think there is a section about this is User Guide.
> > >
> > > > 2. I'll be using pretty large documents for some of my operations, so
> > > > I
> > >
> > > don't
> > >
> > > > want to track it in every stage; only those stages where it will be
> > > > transformed in some way.  Is there anyway to know from the journal
> > > > which stages track document?  This will simplify things once I turn
> > > > over
> > >
> > > monitoring
> > >
> > > > of the system to the client.
> > >
> > > By default documents are NOT tracked. If you want to track documents
> > > you should
> > > use tracked config option which is false by default
> > >
> > > > 3. Also, is the document tracked on entry to the stage or on exit
> > > > from it?
> > >
> > > In
> > >
> > > > other words, is tracking saving the document before any
> > > > transformation is applied by the stage, or after it's transformed?
> > >
> > > Before.
> > >
> > > > 4. I would like to organize pipeline fragments to operate as
> > > > subroutines
> > >
> > > that
> > >
> > > > can be called by multiple stages, which I believe that I can now do
> > > > with
> > >
> > > the
> > >
> > > > updated CallStage functionality.  I would also like to place these
> > >
> > > fragments
> > >
> > > > in a separate file so that I can use them in multiple pipeline
> > > > configurations.  Can this be done?
> > >
> > > This should be possible now, right Bruce? Bruce and I have discussion
> > > about that few
> > > months ago and I think he has implemented it. I havent used it so I am
> > > not sure if it is working.
> > >
> > >
> > > Dejan
> > >
> > > > 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_0
> > >1/ 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_0
> > >1/ 01 _______________________________________________
> > > Babeldoc-devel mailing list
> > > Bab...@li...
> > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

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

RE: [Babeldoc-devel] Using Journal to monitor status...?

[McDonald, B. <Bru...@ba...>]

vi :)

-----Original Message-----
From: David Glick [mailto:dg...@co...]
Sent: Friday, August 15, 2003 3:36 PM
To: McDonald, Bruce; bab...@li...
Subject: Re: [Babeldoc-devel] Using Journal to monitor status...?


Thanks, Bruce.  Throwing an exception in a Script stage gives me exactly what 
I need.  FYI, it seems that the logic for failOnError is exactly the opposite 
as described in the Users Guide, in that my testing seems to indicate that it 
defaults to true unless explicitly set to false.

Speaking of the Users Guide, I'm having an interesting time finding something 
that will allow me to edit the docbook file in a WYSIWYG format.  Being new 
to docbook, can I ask what you use (preferably Java or Linux-based)?


Thanks again,

David

On Friday 15 August 2003 11:12 am, McDonald, Bruce wrote:
> All seems good - In in specialized processing like this - The Scripting
> stage is your friend.
>
>
> See comments inline:
>
> 1. I understand that a stage that fails will force a FAIL status.  However,
> what I'm trying to do is force a FAIL status when a stage completes
> successfully, but the application detects an error.  For example, in my
> case I post SOAP messages, and if the response is a SOAPFAULT, I want to
> force an error into the journal and stop the pipeline processing.  My
> question is: can I do this via a script stage (and if so, how), or must I
> create a new stage type to support it?
>
>
> If you throw an exception from the pipelinestage - that stage will write a
> failed to the journal.  You might need to expand the SoapWriter stage and
> add a config option like 'failOnFault' (default false) to do this. <<<<
>
>
> 2. I also understand about setting the 'tracked' attribute for the stages.
> The question I have regards the use of the journal tool.  Using it to view
> entries, is there any indication that a particular entry in the journal
> contains a tracked document?  The reason is that, in the case of a failure,
> I expect the operator to do the following:
>
> a. View the journal entries to determine which stage failed.
> b. Correct the cause of the failure.
> c. Assuming the problem was not due to the document, replay the journal
> from the stage that failed.  If the particular stage that failed is not
> tracking the document, I assume he will need to find the closest previous
> stage that has a document associated with it, and replay it from that
> point.  If this is correct, he'll need some way to determine which stage to
> use.  If this is not correct, how should I be using the replay
> functionality?
>
>
> YOu might need to write a specialized journal view to do this.  I am not
> sure if the default tools support this. <<<<
>
> Thanks again for your help,
>
> David
>
> On Friday 15 August 2003 12:05 am, Dejan Krsmanovic wrote:
> > Hi David,
> >
> > > Hello to the Great and Powerful List,
> > >
> > > I would like to use the journal to track all documents through the
> > > system.
> >
> > In
> >
> > > order to do this, I'll need to do the following:
> > >
> > > 1. If I encounter an application error, I'd like to force a FAIL status
> >
> > into
> >
> > > the Journal, with an appropriate error message.  Is there a way to do
> >
> > this?
> >
> > All pipeline stages by default forces FAIL status in case of error. Also,
> > processing
> > is stopped in case of error. This can be changed using errorStage and
> > failOnError
> > config options. I think there is a section about this is User Guide.
> >
> > > 2. I'll be using pretty large documents for some of my operations, so I
> >
> > don't
> >
> > > want to track it in every stage; only those stages where it will be
> > > transformed in some way.  Is there anyway to know from the journal
> > > which stages track document?  This will simplify things once I turn
> > > over
> >
> > monitoring
> >
> > > of the system to the client.
> >
> > By default documents are NOT tracked. If you want to track documents you
> > should
> > use tracked config option which is false by default
> >
> > > 3. Also, is the document tracked on entry to the stage or on exit from
> > > it?
> >
> > In
> >
> > > other words, is tracking saving the document before any transformation
> > > is applied by the stage, or after it's transformed?
> >
> > Before.
> >
> > > 4. I would like to organize pipeline fragments to operate as
> > > subroutines
> >
> > that
> >
> > > can be called by multiple stages, which I believe that I can now do
> > > with
> >
> > the
> >
> > > updated CallStage functionality.  I would also like to place these
> >
> > fragments
> >
> > > in a separate file so that I can use them in multiple pipeline
> > > configurations.  Can this be done?
> >
> > This should be possible now, right Bruce? Bruce and I have discussion
> > about that few
> > months ago and I think he has implemented it. I havent used it so I am
> > not sure if it is working.
> >
> >
> > Dejan
> >
> > > 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
> >
> > -------------------------------------------------------
> > 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

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

Re: [Babeldoc-devel] Using Journal to monitor status...?

[Dejan K. <dej...@ya...>]

Try OpenOffice 1.1. It supports "simplified DocBook".
However, I could use it with our documents except two
chapters that conatins generated documentation. You
should manualy remove &scanners or &stages from the
file and then you can use OpenOffice. When you finish
editig just return it back.

Dejan


--- David Glick <dg...@co...> wrote:
> Thanks, Bruce.  Throwing an exception in a Script
> stage gives me exactly what 
> I need.  FYI, it seems that the logic for
> failOnError is exactly the opposite 
> as described in the Users Guide, in that my testing
> seems to indicate that it 
> defaults to true unless explicitly set to false.
> 
> Speaking of the Users Guide, I'm having an
> interesting time finding something 
> that will allow me to edit the docbook file in a
> WYSIWYG format.  Being new 
> to docbook, can I ask what you use (preferably Java
> or Linux-based)?
> 
> 
> Thanks again,
> 
> David
> 
> On Friday 15 August 2003 11:12 am, McDonald, Bruce
> wrote:
> > All seems good - In in specialized processing like
> this - The Scripting
> > stage is your friend.
> >
> >
> > See comments inline:
> >
> > 1. I understand that a stage that fails will force
> a FAIL status.  However,
> > what I'm trying to do is force a FAIL status when
> a stage completes
> > successfully, but the application detects an
> error.  For example, in my
> > case I post SOAP messages, and if the response is
> a SOAPFAULT, I want to
> > force an error into the journal and stop the
> pipeline processing.  My
> > question is: can I do this via a script stage (and
> if so, how), or must I
> > create a new stage type to support it?
> >
> >
> > If you throw an exception from the pipelinestage -
> that stage will write a
> > failed to the journal.  You might need to expand
> the SoapWriter stage and
> > add a config option like 'failOnFault' (default
> false) to do this. <<<<
> >
> >
> > 2. I also understand about setting the 'tracked'
> attribute for the stages.
> > The question I have regards the use of the journal
> tool.  Using it to view
> > entries, is there any indication that a particular
> entry in the journal
> > contains a tracked document?  The reason is that,
> in the case of a failure,
> > I expect the operator to do the following:
> >
> > a. View the journal entries to determine which
> stage failed.
> > b. Correct the cause of the failure.
> > c. Assuming the problem was not due to the
> document, replay the journal
> > from the stage that failed.  If the particular
> stage that failed is not
> > tracking the document, I assume he will need to
> find the closest previous
> > stage that has a document associated with it, and
> replay it from that
> > point.  If this is correct, he'll need some way to
> determine which stage to
> > use.  If this is not correct, how should I be
> using the replay
> > functionality?
> >
> >
> > YOu might need to write a specialized journal view
> to do this.  I am not
> > sure if the default tools support this. <<<<
> >
> > Thanks again for your help,
> >
> > David
> >
> > On Friday 15 August 2003 12:05 am, Dejan
> Krsmanovic wrote:
> > > Hi David,
> > >
> > > > Hello to the Great and Powerful List,
> > > >
> > > > I would like to use the journal to track all
> documents through the
> > > > system.
> > >
> > > In
> > >
> > > > order to do this, I'll need to do the
> following:
> > > >
> > > > 1. If I encounter an application error, I'd
> like to force a FAIL status
> > >
> > > into
> > >
> > > > the Journal, with an appropriate error
> message.  Is there a way to do
> > >
> > > this?
> > >
> > > All pipeline stages by default forces FAIL
> status in case of error. Also,
> > > processing
> > > is stopped in case of error. This can be changed
> using errorStage and
> > > failOnError
> > > config options. I think there is a section about
> this is User Guide.
> > >
> > > > 2. I'll be using pretty large documents for
> some of my operations, so I
> > >
> > > don't
> > >
> > > > want to track it in every stage; only those
> stages where it will be
> > > > transformed in some way.  Is there anyway to
> know from the journal
> > > > which stages track document?  This will
> simplify things once I turn
> > > > over
> > >
> > > monitoring
> > >
> > > > of the system to the client.
> > >
> > > By default documents are NOT tracked. If you
> want to track documents you
> > > should
> > > use tracked config option which is false by
> default
> > >
> > > > 3. Also, is the document tracked on entry to
> the stage or on exit from
> > > > it?
> > >
> > > In
> > >
> > > > other words, is tracking saving the document
> before any transformation
> > > > is applied by the stage, or after it's
> transformed?
> > >
> > > Before.
> > >
> > > > 4. I would like to organize pipeline fragments
> to operate as
> > > > subroutines
> > >
> > > that
> > >
> > > > can be called by multiple stages, which I
> believe that I can now do
> > > > with
> > >
> > > the
> > >
> > > > updated CallStage functionality.  I would also
> like to place these
> > >
> > > fragments
> > >
> > > > in a separate file so that I can use them in
> multiple pipeline
> > > > configurations.  Can this be done?
> > >
> > > This should be possible now, right Bruce? Bruce
> and I have discussion
> > > about that few
> > > months ago and I think he has implemented it. I
> havent used it so I am
> > > not sure if it is working.
> > >
> > >
> > > Dejan
> > >
> > > > Thanks,
> > > >
> > > > David
> > > >
> > > > --
> > > > David Glick
> > > > Transmit Consulting, Inc
> > > > 619-475-4052
> > > > dg...@tr...
> > > >
> > > >
> > > >
> 
=== message truncated ===


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

Re: [Babeldoc-devel] Using Journal to monitor status...?

[David G. <dg...@co...>]

Well, I can certainly run vi on Linux...

On Friday 15 August 2003 12:42 pm, McDonald, Bruce wrote:
> vi :)
>
> -----Original Message-----
> From: David Glick [mailto:dg...@co...]
> Sent: Friday, August 15, 2003 3:36 PM
> To: McDonald, Bruce; bab...@li...
> Subject: Re: [Babeldoc-devel] Using Journal to monitor status...?
>
>
> Thanks, Bruce.  Throwing an exception in a Script stage gives me exactly
> what I need.  FYI, it seems that the logic for failOnError is exactly the
> opposite as described in the Users Guide, in that my testing seems to
> indicate that it defaults to true unless explicitly set to false.
>
> Speaking of the Users Guide, I'm having an interesting time finding
> something that will allow me to edit the docbook file in a WYSIWYG format. 
> Being new to docbook, can I ask what you use (preferably Java or
> Linux-based)?
>
>
> Thanks again,
>
> David
>
> On Friday 15 August 2003 11:12 am, McDonald, Bruce wrote:
> > All seems good - In in specialized processing like this - The Scripting
> > stage is your friend.
> >
> >
> > See comments inline:
> >
> > 1. I understand that a stage that fails will force a FAIL status. 
> > However, what I'm trying to do is force a FAIL status when a stage
> > completes successfully, but the application detects an error.  For
> > example, in my case I post SOAP messages, and if the response is a
> > SOAPFAULT, I want to force an error into the journal and stop the
> > pipeline processing.  My question is: can I do this via a script stage
> > (and if so, how), or must I create a new stage type to support it?
> >
> >
> > If you throw an exception from the pipelinestage - that stage will write
> > a failed to the journal.  You might need to expand the SoapWriter stage
> > and add a config option like 'failOnFault' (default false) to do this.
> > <<<<
> >
> >
> > 2. I also understand about setting the 'tracked' attribute for the
> > stages. The question I have regards the use of the journal tool.  Using
> > it to view entries, is there any indication that a particular entry in
> > the journal contains a tracked document?  The reason is that, in the case
> > of a failure, I expect the operator to do the following:
> >
> > a. View the journal entries to determine which stage failed.
> > b. Correct the cause of the failure.
> > c. Assuming the problem was not due to the document, replay the journal
> > from the stage that failed.  If the particular stage that failed is not
> > tracking the document, I assume he will need to find the closest previous
> > stage that has a document associated with it, and replay it from that
> > point.  If this is correct, he'll need some way to determine which stage
> > to use.  If this is not correct, how should I be using the replay
> > functionality?
> >
> >
> > YOu might need to write a specialized journal view to do this.  I am not
> > sure if the default tools support this. <<<<
> >
> > Thanks again for your help,
> >
> > David
> >
> > On Friday 15 August 2003 12:05 am, Dejan Krsmanovic wrote:
> > > Hi David,
> > >
> > > > Hello to the Great and Powerful List,
> > > >
> > > > I would like to use the journal to track all documents through the
> > > > system.
> > >
> > > In
> > >
> > > > order to do this, I'll need to do the following:
> > > >
> > > > 1. If I encounter an application error, I'd like to force a FAIL
> > > > status
> > >
> > > into
> > >
> > > > the Journal, with an appropriate error message.  Is there a way to do
> > >
> > > this?
> > >
> > > All pipeline stages by default forces FAIL status in case of error.
> > > Also, processing
> > > is stopped in case of error. This can be changed using errorStage and
> > > failOnError
> > > config options. I think there is a section about this is User Guide.
> > >
> > > > 2. I'll be using pretty large documents for some of my operations, so
> > > > I
> > >
> > > don't
> > >
> > > > want to track it in every stage; only those stages where it will be
> > > > transformed in some way.  Is there anyway to know from the journal
> > > > which stages track document?  This will simplify things once I turn
> > > > over
> > >
> > > monitoring
> > >
> > > > of the system to the client.
> > >
> > > By default documents are NOT tracked. If you want to track documents
> > > you should
> > > use tracked config option which is false by default
> > >
> > > > 3. Also, is the document tracked on entry to the stage or on exit
> > > > from it?
> > >
> > > In
> > >
> > > > other words, is tracking saving the document before any
> > > > transformation is applied by the stage, or after it's transformed?
> > >
> > > Before.
> > >
> > > > 4. I would like to organize pipeline fragments to operate as
> > > > subroutines
> > >
> > > that
> > >
> > > > can be called by multiple stages, which I believe that I can now do
> > > > with
> > >
> > > the
> > >
> > > > updated CallStage functionality.  I would also like to place these
> > >
> > > fragments
> > >
> > > > in a separate file so that I can use them in multiple pipeline
> > > > configurations.  Can this be done?
> > >
> > > This should be possible now, right Bruce? Bruce and I have discussion
> > > about that few
> > > months ago and I think he has implemented it. I havent used it so I am
> > > not sure if it is working.
> > >
> > >
> > > Dejan
> > >
> > > > 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_0
> > >1/ 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_0
> > >1/ 01 _______________________________________________
> > > Babeldoc-devel mailing list
> > > Bab...@li...
> > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

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

Re: [Babeldoc-devel] Using Journal to monitor status...?

[David G. <dg...@co...>]

Thanks, Bruce.  Throwing an exception in a Script stage gives me exactly what 
I need.  FYI, it seems that the logic for failOnError is exactly the opposite 
as described in the Users Guide, in that my testing seems to indicate that it 
defaults to true unless explicitly set to false.

Speaking of the Users Guide, I'm having an interesting time finding something 
that will allow me to edit the docbook file in a WYSIWYG format.  Being new 
to docbook, can I ask what you use (preferably Java or Linux-based)?


Thanks again,

David

On Friday 15 August 2003 11:12 am, McDonald, Bruce wrote:
> All seems good - In in specialized processing like this - The Scripting
> stage is your friend.
>
>
> See comments inline:
>
> 1. I understand that a stage that fails will force a FAIL status.  However,
> what I'm trying to do is force a FAIL status when a stage completes
> successfully, but the application detects an error.  For example, in my
> case I post SOAP messages, and if the response is a SOAPFAULT, I want to
> force an error into the journal and stop the pipeline processing.  My
> question is: can I do this via a script stage (and if so, how), or must I
> create a new stage type to support it?
>
>
> If you throw an exception from the pipelinestage - that stage will write a
> failed to the journal.  You might need to expand the SoapWriter stage and
> add a config option like 'failOnFault' (default false) to do this. <<<<
>
>
> 2. I also understand about setting the 'tracked' attribute for the stages.
> The question I have regards the use of the journal tool.  Using it to view
> entries, is there any indication that a particular entry in the journal
> contains a tracked document?  The reason is that, in the case of a failure,
> I expect the operator to do the following:
>
> a. View the journal entries to determine which stage failed.
> b. Correct the cause of the failure.
> c. Assuming the problem was not due to the document, replay the journal
> from the stage that failed.  If the particular stage that failed is not
> tracking the document, I assume he will need to find the closest previous
> stage that has a document associated with it, and replay it from that
> point.  If this is correct, he'll need some way to determine which stage to
> use.  If this is not correct, how should I be using the replay
> functionality?
>
>
> YOu might need to write a specialized journal view to do this.  I am not
> sure if the default tools support this. <<<<
>
> Thanks again for your help,
>
> David
>
> On Friday 15 August 2003 12:05 am, Dejan Krsmanovic wrote:
> > Hi David,
> >
> > > Hello to the Great and Powerful List,
> > >
> > > I would like to use the journal to track all documents through the
> > > system.
> >
> > In
> >
> > > order to do this, I'll need to do the following:
> > >
> > > 1. If I encounter an application error, I'd like to force a FAIL status
> >
> > into
> >
> > > the Journal, with an appropriate error message.  Is there a way to do
> >
> > this?
> >
> > All pipeline stages by default forces FAIL status in case of error. Also,
> > processing
> > is stopped in case of error. This can be changed using errorStage and
> > failOnError
> > config options. I think there is a section about this is User Guide.
> >
> > > 2. I'll be using pretty large documents for some of my operations, so I
> >
> > don't
> >
> > > want to track it in every stage; only those stages where it will be
> > > transformed in some way.  Is there anyway to know from the journal
> > > which stages track document?  This will simplify things once I turn
> > > over
> >
> > monitoring
> >
> > > of the system to the client.
> >
> > By default documents are NOT tracked. If you want to track documents you
> > should
> > use tracked config option which is false by default
> >
> > > 3. Also, is the document tracked on entry to the stage or on exit from
> > > it?
> >
> > In
> >
> > > other words, is tracking saving the document before any transformation
> > > is applied by the stage, or after it's transformed?
> >
> > Before.
> >
> > > 4. I would like to organize pipeline fragments to operate as
> > > subroutines
> >
> > that
> >
> > > can be called by multiple stages, which I believe that I can now do
> > > with
> >
> > the
> >
> > > updated CallStage functionality.  I would also like to place these
> >
> > fragments
> >
> > > in a separate file so that I can use them in multiple pipeline
> > > configurations.  Can this be done?
> >
> > This should be possible now, right Bruce? Bruce and I have discussion
> > about that few
> > months ago and I think he has implemented it. I havent used it so I am
> > not sure if it is working.
> >
> >
> > Dejan
> >
> > > 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
> >
> > -------------------------------------------------------
> > 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

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

RE: [Babeldoc-devel] Using Journal to monitor status...?

[McDonald, B. <Bru...@ba...>]

All seems good - In in specialized processing like this - The Scripting stage is your friend.


See comments inline:

1. I understand that a stage that fails will force a FAIL status.  However, 
what I'm trying to do is force a FAIL status when a stage completes 
successfully, but the application detects an error.  For example, in my case 
I post SOAP messages, and if the response is a SOAPFAULT, I want to force an 
error into the journal and stop the pipeline processing.  My question is: can 
I do this via a script stage (and if so, how), or must I create a new stage 
type to support it?

>>>>
If you throw an exception from the pipelinestage - that stage will write a failed to the journal.  You might need to expand the SoapWriter stage and add a config option like 'failOnFault' (default false) to do this.
<<<<


2. I also understand about setting the 'tracked' attribute for the stages.  
The question I have regards the use of the journal tool.  Using it to view 
entries, is there any indication that a particular entry in the journal 
contains a tracked document?  The reason is that, in the case of a failure, I expect the operator to do the following:

a. View the journal entries to determine which stage failed.
b. Correct the cause of the failure.
c. Assuming the problem was not due to the document, replay the journal from the stage that failed.  If the particular stage that failed is not tracking the document, I assume he will need to find the closest previous stage that has a document associated with it, and replay it from that point.  If this is correct, he'll need some way to determine which stage to use.  If this is not correct, how should I be using the replay functionality?

>>>>
YOu might need to write a specialized journal view to do this.  I am not sure if the default tools support this.
<<<<

Thanks again for your help,

David


On Friday 15 August 2003 12:05 am, Dejan Krsmanovic wrote:
> Hi David,
>
> > Hello to the Great and Powerful List,
> >
> > I would like to use the journal to track all documents through the
> > system.
>
> In
>
> > order to do this, I'll need to do the following:
> >
> > 1. If I encounter an application error, I'd like to force a FAIL status
>
> into
>
> > the Journal, with an appropriate error message.  Is there a way to do
>
> this?
>
> All pipeline stages by default forces FAIL status in case of error. Also,
> processing
> is stopped in case of error. This can be changed using errorStage and
> failOnError
> config options. I think there is a section about this is User Guide.
>
> > 2. I'll be using pretty large documents for some of my operations, so I
>
> don't
>
> > want to track it in every stage; only those stages where it will be
> > transformed in some way.  Is there anyway to know from the journal which
> > stages track document?  This will simplify things once I turn over
>
> monitoring
>
> > of the system to the client.
>
> By default documents are NOT tracked. If you want to track documents you
> should
> use tracked config option which is false by default
>
> > 3. Also, is the document tracked on entry to the stage or on exit from
> > it?
>
> In
>
> > other words, is tracking saving the document before any transformation is
> > applied by the stage, or after it's transformed?
>
> Before.
>
> > 4. I would like to organize pipeline fragments to operate as subroutines
>
> that
>
> > can be called by multiple stages, which I believe that I can now do with
>
> the
>
> > updated CallStage functionality.  I would also like to place these
>
> fragments
>
> > in a separate file so that I can use them in multiple pipeline
> > configurations.  Can this be done?
>
> This should be possible now, right Bruce? Bruce and I have discussion about
> that few
> months ago and I think he has implemented it. I havent used it so I am not
> sure if it is working.
>
>
> Dejan
>
> > 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
>
> -------------------------------------------------------
> 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

-- 
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

Re: [Babeldoc-devel] Using Journal to monitor status...?

[David G. <dg...@co...>]

Hi Dejan,

Thanks for your reply; you've answered several of my questions, but I think I 
did not explain myself well enough on a couple of items:

1. I understand that a stage that fails will force a FAIL status.  However, 
what I'm trying to do is force a FAIL status when a stage completes 
successfully, but the application detects an error.  For example, in my case 
I post SOAP messages, and if the response is a SOAPFAULT, I want to force an 
error into the journal and stop the pipeline processing.  My question is: can 
I do this via a script stage (and if so, how), or must I create a new stage 
type to support it?

2. I also understand about setting the 'tracked' attribute for the stages.  
The question I have regards the use of the journal tool.  Using it to view 
entries, is there any indication that a particular entry in the journal 
contains a tracked document?  The reason is that, in the case of a failure, I 
expect the operator to do the following:

a. View the journal entries to determine which stage failed.
b. Correct the cause of the failure.
c. Assuming the problem was not due to the document, replay the journal from 
the stage that failed.  If the particular stage that failed is not tracking 
the document, I assume he will need to find the closest previous stage that 
has a document associated with it, and replay it from that point.  If this is 
correct, he'll need some way to determine which stage to use.  If this is not 
correct, how should I be using the replay functionality?


Thanks again for your help,

David


On Friday 15 August 2003 12:05 am, Dejan Krsmanovic wrote:
> Hi David,
>
> > Hello to the Great and Powerful List,
> >
> > I would like to use the journal to track all documents through the
> > system.
>
> In
>
> > order to do this, I'll need to do the following:
> >
> > 1. If I encounter an application error, I'd like to force a FAIL status
>
> into
>
> > the Journal, with an appropriate error message.  Is there a way to do
>
> this?
>
> All pipeline stages by default forces FAIL status in case of error. Also,
> processing
> is stopped in case of error. This can be changed using errorStage and
> failOnError
> config options. I think there is a section about this is User Guide.
>
> > 2. I'll be using pretty large documents for some of my operations, so I
>
> don't
>
> > want to track it in every stage; only those stages where it will be
> > transformed in some way.  Is there anyway to know from the journal which
> > stages track document?  This will simplify things once I turn over
>
> monitoring
>
> > of the system to the client.
>
> By default documents are NOT tracked. If you want to track documents you
> should
> use tracked config option which is false by default
>
> > 3. Also, is the document tracked on entry to the stage or on exit from
> > it?
>
> In
>
> > other words, is tracking saving the document before any transformation is
> > applied by the stage, or after it's transformed?
>
> Before.
>
> > 4. I would like to organize pipeline fragments to operate as subroutines
>
> that
>
> > can be called by multiple stages, which I believe that I can now do with
>
> the
>
> > updated CallStage functionality.  I would also like to place these
>
> fragments
>
> > in a separate file so that I can use them in multiple pipeline
> > configurations.  Can this be done?
>
> This should be possible now, right Bruce? Bruce and I have discussion about
> that few
> months ago and I think he has implemented it. I havent used it so I am not
> sure if it is working.
>
>
> Dejan
>
> > 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
>
> -------------------------------------------------------
> 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

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

Re: [Babeldoc-devel] Using Journal to monitor status...?

[Dejan K. <dej...@nb...>]

Hi David,

> Hello to the Great and Powerful List,
>
> I would like to use the journal to track all documents through the system.
In
> order to do this, I'll need to do the following:
>
> 1. If I encounter an application error, I'd like to force a FAIL status
into
> the Journal, with an appropriate error message.  Is there a way to do
this?

All pipeline stages by default forces FAIL status in case of error. Also,
processing
is stopped in case of error. This can be changed using errorStage and
failOnError
config options. I think there is a section about this is User Guide.

> 2. I'll be using pretty large documents for some of my operations, so I
don't
> want to track it in every stage; only those stages where it will be
> transformed in some way.  Is there anyway to know from the journal which
> stages track document?  This will simplify things once I turn over
monitoring
> of the system to the client.

By default documents are NOT tracked. If you want to track documents you
should
use tracked config option which is false by default

> 3. Also, is the document tracked on entry to the stage or on exit from it?
In
> other words, is tracking saving the document before any transformation is
> applied by the stage, or after it's transformed?

Before.

> 4. I would like to organize pipeline fragments to operate as subroutines
that
> can be called by multiple stages, which I believe that I can now do with
the
> updated CallStage functionality.  I would also like to place these
fragments
> in a separate file so that I can use them in multiple pipeline
> configurations.  Can this be done?
>

This should be possible now, right Bruce? Bruce and I have discussion about
that few
months ago and I think he has implemented it. I havent used it so I am not
sure if it is working.


Dejan
>
>
> 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

Re: [Babeldoc-devel] Adding examples to User Guide?

[Dejan K. <dej...@nb...>]

Hi David,
Currently is pretty dificult to do such thing since documentation is
autogenerated. Maybe you can add examples to description section? If you
want to do that,  you can edit source code or even better message resources.
All pipeline stages has getInfo() method which returns IConfigInfo object
with meta information about that stage. Scanner worker and pipeline stage
documentation is generated using this metainformation. In current
implementation every pipeline stage in its constructor calls super
constructor with IConfigInfo parameter. One of methods of object that is
sent to super constructor is getDescription() method which returns String
with stage description.

Anyway, most of examples in current distribution are in examples folder. So
maybe you would like to put them there....

Dejan

----- Original Message -----
From: "David Glick" <dg...@co...>
To: <bab...@li...>
Sent: Friday, August 15, 2003 2:09 AM
Subject: [Babeldoc-devel] Adding examples to User Guide?


> Hi Bruce,
>
> I'd like to add examples to the Users Guide to cover at the least the
issues
> that I faced coming up to speed with some of these stages. I'd like to add
> the examples in the Pipeline stage types section to keep them with the
stage
> they illustrate.  However, it looks like this section is auto-generated
from
> the source.  How would you recommend I proceed?
>
>
> 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

[Babeldoc-devel] babeldoc/modules/sql/src/com/babeldoc/sql/util SqlQueryManager.java,1.6,1.7 TableKeyHelper.java,1.5,1.6 VelocitySqlContext.java,1.4,1.5

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/util
In directory sc8-pr-cvs1:/tmp/cvs-serv6089/sql/src/com/babeldoc/sql/util

Modified Files:
	SqlQueryManager.java TableKeyHelper.java 
	VelocitySqlContext.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: SqlQueryManager.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/util/SqlQueryManager.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** SqlQueryManager.java	27 Jun 2003 02:05:59 -0000	1.6
--- SqlQueryManager.java	15 Aug 2003 00:25:30 -0000	1.7
***************
*** 77,82 ****
  /**
   * Description: Provides a very simple interface to the conifguration manager
!  * stuff for get sql query strings.  This is a useful abstraction so that the
!  * queries can get changes on the fly, etc.
   *
   * @author bmcdonald
--- 77,82 ----
  /**
   * Description: Provides a very simple interface to the conifguration manager
!  * stuff for getChild sql query strings.  This is a useful abstraction so that the
!  * queries can getChild changes on the fly, etc.
   *
   * @author bmcdonald

Index: TableKeyHelper.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/util/TableKeyHelper.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** TableKeyHelper.java	27 Jun 2003 02:05:59 -0000	1.5
--- TableKeyHelper.java	15 Aug 2003 00:25:30 -0000	1.6
***************
*** 76,80 ****
  /**
   * Simple class to create new ids using a db table to keep track of the max id
!  * for that table.  Useful to get unique keys in a db independent way.
   *
   * @author Bmcdonald
--- 76,80 ----
  /**
   * Simple class to create new ids using a db table to keep track of the max id
!  * for that table.  Useful to getChild unique getChildrenNameSet in a db independent way.
   *
   * @author Bmcdonald

Index: VelocitySqlContext.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/util/VelocitySqlContext.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** VelocitySqlContext.java	27 Jun 2003 02:05:59 -0000	1.4
--- VelocitySqlContext.java	15 Aug 2003 00:25:30 -0000	1.5
***************
*** 90,94 ****
     *
     * @param resourceName the name of the resource
!    * @param table the sql table name to get the next id for
     *
     * @return DOCUMENT ME!
--- 90,94 ----
     *
     * @param resourceName the name of the resource
!    * @param table the sql table name to getChild the next id for
     *
     * @return DOCUMENT ME!

[Babeldoc-devel] Using Journal to monitor status...?

[David G. <dg...@co...>]

Hello to the Great and Powerful List,

I would like to use the journal to track all documents through the system.  In 
order to do this, I'll need to do the following:

1. If I encounter an application error, I'd like to force a FAIL status into 
the Journal, with an appropriate error message.  Is there a way to do this?

2. I'll be using pretty large documents for some of my operations, so I don't 
want to track it in every stage; only those stages where it will be 
transformed in some way.  Is there anyway to know from the journal which 
stages track document?  This will simplify things once I turn over monitoring 
of the system to the client.

3. Also, is the document tracked on entry to the stage or on exit from it?  In 
other words, is tracking saving the document before any transformation is 
applied by the stage, or after it's transformed?

4. I would like to organize pipeline fragments to operate as subroutines that 
can be called by multiple stages, which I believe that I can now do with the 
updated CallStage functionality.  I would also like to place these fragments 
in a separate file so that I can use them in multiple pipeline 
configurations.  Can this be done?



Thanks,

David

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

[Babeldoc-devel] babeldoc/modules/scanner/config/i18n messages.properties,1.12,1.13

[<tr...@us...>]

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

Modified Files:
	messages.properties 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: messages.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/config/i18n/messages.properties,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** messages.properties	14 Aug 2003 23:57:19 -0000	1.12
--- messages.properties	15 Aug 2003 00:25:29 -0000	1.13
***************
*** 96,99 ****
--- 96,100 ----
  scanner.nullScanner.desc=Null Scanner feeds null documents everytime the scanner runs.  This is useful for scheduling.
  
+ 
  scanner.001=Started
  scanner.002=Stopped
***************
*** 168,175 ****
  scanner.074=ScannerThread did not start
  #scanner.075=ScannerThread waking up
- 
- 
- 
- 
  
  
--- 169,172 ----

[Babeldoc-devel] babeldoc/modules/sql/config/i18n messages.properties,1.7,1.8

[<tr...@us...>]

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

Modified Files:
	messages.properties 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: messages.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/config/i18n/messages.properties,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** messages.properties	13 Aug 2003 22:44:30 -0000	1.7
--- messages.properties	15 Aug 2003 00:25:30 -0000	1.8
***************
*** 35,40 ****
  sql.201=Option resourceName is not optional!
  sql.202=Either sqlScript or attributeSql must be defined!
- 
- sql.pipeline.stage.query.desc=Pipeline stage that runs a number of SQL queries and creates a pipeline document consisting of the results as an xml document
- sql.pipeline.stage.query.option.resource=Resource name that defines the SQL connection
- sql.pipeline.stage.query.option.sql=The set of SQL Query strings that will be executed to generate the results for the pipeline document
--- 35,36 ----

[Babeldoc-devel] babeldoc/modules/sql/src/com/babeldoc/sql/config SqlConfigService.java,1.6,1.7

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/config
In directory sc8-pr-cvs1:/tmp/cvs-serv6089/sql/src/com/babeldoc/sql/config

Modified Files:
	SqlConfigService.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: SqlConfigService.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/config/SqlConfigService.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** SqlConfigService.java	27 Jun 2003 02:05:58 -0000	1.6
--- SqlConfigService.java	15 Aug 2003 00:25:30 -0000	1.7
***************
*** 101,105 ****
    public static final String DB_DRIVER = "dbDriver";
  
!   /** constant:  the select query to get the configuration data */
    public static final String CONFIG_SELECT = "SELECT cfg_name, cfg_value FROM config WHERE cfg_name LIKE ";
  
--- 101,105 ----
    public static final String DB_DRIVER = "dbDriver";
  
!   /** constant:  the select query to getChild the configuration data */
    public static final String CONFIG_SELECT = "SELECT cfg_name, cfg_value FROM config WHERE cfg_name LIKE ";
  
***************
*** 139,143 ****
  
    /**
!    * get a config bundle for the name and given locale.  This extracts the
     * country and language strings from the locale object and calls the
     * getConfig method
--- 139,143 ----
  
    /**
!    * getChild a config bundle for the name and given locale.  This extracts the
     * country and language strings from the locale object and calls the
     * getConfig method
***************
*** 164,168 ****
  
    /**
!    * get a config bundle for the name and default locale.  This is were the the
     * database is actually opened and data is selected. <strong>TODO:  Use a
     * connection pool</strong>
--- 164,168 ----
  
    /**
!    * getChild a config bundle for the name and default locale.  This is were the the
     * database is actually opened and data is selected. <strong>TODO:  Use a
     * connection pool</strong>
***************
*** 251,255 ****
      ResultSet results = null;
  
!     // Build the string name/key - remember names + keys get
      // stored in the same table.
      name += ("." + key);
--- 251,255 ----
      ResultSet results = null;
  
!     // Build the string name/key - remember names + getChildrenNameSet getChild
      // stored in the same table.
      name += ("." + key);

[Babeldoc-devel] babeldoc/modules/sql/src/com/babeldoc/sql/journal GenericSqlJournal.java,1.9,1.10

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/journal
In directory sc8-pr-cvs1:/tmp/cvs-serv6089/sql/src/com/babeldoc/sql/journal

Modified Files:
	GenericSqlJournal.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: GenericSqlJournal.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/journal/GenericSqlJournal.java,v
retrieving revision 1.9
retrieving revision 1.10
diff -C2 -d -r1.9 -r1.10
*** GenericSqlJournal.java	28 Jul 2003 21:34:28 -0000	1.9
--- GenericSqlJournal.java	15 Aug 2003 00:25:30 -0000	1.10
***************
*** 300,304 ****
  
    /**
!    * get tickets between the specified dates.  Return up to the maxreturned
     * number of results.
     *
--- 300,304 ----
  
    /**
!    * getChild tickets between the specified dates.  Return up to the maxreturned
     * number of results.
     *
***************
*** 677,681 ****
          pstmt.setString(7, additional);
  
!         // without synchronized it is likely to get the same value
          // from getNextStep several times in multiple threads
          long step ;
--- 677,681 ----
          pstmt.setString(7, additional);
  
!         // without synchronized it is likely to getChild the same value
          // from getNextStep several times in multiple threads
          long step ;

[Babeldoc-devel] babeldoc/modules/sql/config/resource babel-config.properties,1.1.1.1,1.2 babel-journal.properties,1.1.1.1,1.2 babel-user.properties,1.1.1.1,1.2

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/sql/config/resource
In directory sc8-pr-cvs1:/tmp/cvs-serv6089/sql/config/resource

Modified Files:
	babel-config.properties babel-journal.properties 
	babel-user.properties 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: babel-config.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/config/resource/babel-config.properties,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** babel-config.properties	24 Feb 2003 22:47:21 -0000	1.1.1.1
--- babel-config.properties	15 Aug 2003 00:25:30 -0000	1.2
***************
*** 5,6 ****
--- 5,7 ----
  dbPassword=babel
  dbUrl=jdbc:mysql://localhost/babel_config
+ dbDriver=org.gjt.mm.mysql.Driver

Index: babel-journal.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/config/resource/babel-journal.properties,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** babel-journal.properties	24 Feb 2003 22:47:21 -0000	1.1.1.1
--- babel-journal.properties	15 Aug 2003 00:25:30 -0000	1.2
***************
*** 5,6 ****
--- 5,7 ----
  dbPassword=babel
  dbUrl=jdbc:mysql://localhost/babel_journal
+ dbDriver=org.gjt.mm.mysql.Driver

Index: babel-user.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/config/resource/babel-user.properties,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -C2 -d -r1.1.1.1 -r1.2
*** babel-user.properties	24 Feb 2003 22:47:21 -0000	1.1.1.1
--- babel-user.properties	15 Aug 2003 00:25:30 -0000	1.2
***************
*** 1,6 ****
  # Type is required.
! type=simple
  
  dbUser=babel
  dbPassword=babel
  dbUrl=jdbc:mysql://localhost/babel_user
--- 1,7 ----
  # Type is required.
! type=jdbc
  
  dbUser=babel
  dbPassword=babel
  dbUrl=jdbc:mysql://localhost/babel_user
+ dbDriver=org.gjt.mm.mysql.Driver

[Babeldoc-devel] babeldoc/modules/core/src/com/babeldoc/core/resource ResourceConfigInfo.java,NONE,1.1 IResource.java,1.3,1.4 Resource.java,1.5,1.6 ResourceFactory.java,1.5,1.6

[<tr...@us...>]

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

Modified Files:
	IResource.java Resource.java ResourceFactory.java 
Added Files:
	ResourceConfigInfo.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

--- NEW FILE: ResourceConfigInfo.java ---
/* ====================================================================
 * The Apache Software License, Version 1.1
 *
 * Copyright (c) 2000 The Apache Software Foundation.  All rights
 * reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in
 *    the documentation and/or other materials provided with the
 *    distribution.
 *
 * 3. The end-user documentation included with the redistribution,
 *    if any, must include the following acknowledgment:
 *       "This product includes software developed by the
 *        Apache Software Foundation (http://www.apache.org/)."
 *    Alternately, this acknowledgment may appear in the software itself,
 *    if and wherever such third-party acknowledgments normally appear.
 *
 * 4. The names "Apache" and "Apache Software Foundation" must
 *    not be used to endorse or promote products derived from this
 *    software without prior written permission. For written
 *    permission, please contact ap...@ap....
 *
 * 5. Products derived from this software may not be called "Apache",
 *    nor may "Apache" appear in their name, without prior written
 *    permission of the Apache Software Foundation.
 *
 * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
 * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 * OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
 * DISCLAIMED.  IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR
 * ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
 * USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
 * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
 * OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
 * OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.
 * ====================================================================
 *
 * This software consists of voluntary contributions made by many
 * individuals on behalf of the Apache Software Foundation.  For more
 * information on the Apache Software Foundation, please see
 * <http://www.apache.org/>.
 *
 * Portions of this software are based upon public domain software
 * originally written at the National Center for Supercomputing Applications,
 * University of Illinois, Urbana-Champaign.
 * ====================================================================
 *
 * Babeldoc:  The Universal Document Processor
 *
 * $Header: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/resource/ResourceConfigInfo.java,v 1.1 2003/08/15 00:25:29 triphop Exp $
 * $DateTime$
 * $Author: triphop $
 *
 */
package com.babeldoc.core.resource;

import com.babeldoc.core.option.ConfigInfo;

import java.util.Collection;

/**
 * Configuration information object for resources.  This will allow objects
 * to describe those configuration options that are required and optional.
 *
 * @author bmcdonald
 * @version 1.1
 */
public abstract class ResourceConfigInfo
    extends ConfigInfo {
  /**
   * Return an xmlized version of the of the config info
   *
   * @return String of configuration information.
   */
  public String toXml() {
    return null;
  }

  /**
   * This method returns options that are general to all components
   *
   * @return comments
   */
  public Collection getGeneralOptions() {
    return null;
  }
}

Index: IResource.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/resource/IResource.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** IResource.java	27 Jun 2003 02:19:59 -0000	1.3
--- IResource.java	15 Aug 2003 00:25:29 -0000	1.4
***************
*** 66,69 ****
--- 66,72 ----
  package com.babeldoc.core.resource;
  
+ import com.babeldoc.core.INamed;
+ import com.babeldoc.core.option.IConfigurable;
+ 
  /**
   * Interface for connection managers.  Primarily to be used by connection pools
***************
*** 75,79 ****
   * @version 1.0
   */
! public interface IResource extends com.babeldoc.core.INamed {
    /**
     * Check back in a checked out connection
--- 78,83 ----
   * @version 1.0
   */
! public interface IResource
!     extends INamed, IConfigurable {
    /**
     * Check back in a checked out connection

Index: Resource.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/resource/Resource.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** Resource.java	27 Jun 2003 02:19:59 -0000	1.5
--- Resource.java	15 Aug 2003 00:25:29 -0000	1.6
***************
*** 66,71 ****
  package com.babeldoc.core.resource;
  
! import com.babeldoc.core.config.ConfigService;
! import com.babeldoc.core.config.IConfig;
  
  
--- 66,70 ----
  package com.babeldoc.core.resource;
  
! import com.babeldoc.core.Named;
  
  
***************
*** 77,100 ****
   * @version 1.0
   */
! public abstract class Resource extends com.babeldoc.core.Named
      implements IResource {
-   /** Constants - will move to confserver when needs to be done. */
-   public static String CONFIG_FILENAME = "resource/";
  
!   /** Configuration stuff */
!   private IConfig config;
  
    /**
!    * Get the config object
     *
!    * @return DOCUMENT ME!
     */
!   protected IConfig getConfig() {
!     if (config == null) {
!       config = ConfigService.getInstance().getConfig(CONFIG_FILENAME +
!           getName());
      }
  
!     return config;
    }
  }
--- 76,126 ----
   * @version 1.0
   */
! abstract public class Resource
!     extends Named
      implements IResource {
  
!   /** State variables */
!   private boolean initialized = false;
  
    /**
!    * Setup the resource - this MUST be overridden by child resources
     *
!    * @throws ResourceException
     */
!   abstract protected void setup() throws ResourceException;
! 
!   /**
!    * Get a new connection.
!    *
!    * @return NOTHING - the extending class needs to do the actual work
!    *
!    * @throws ResourceException
!    */
!   synchronized public Object checkOut() throws ResourceException {
!     // If not initialized, setup now
!     if (!isInitialized()) {
!       setup();
!       setInitialized(true);
      }
  
!     return null;
!   }
! 
!   /**
!    * Has this resource been initialized
!    *
!    * @return
!    */
!   protected boolean isInitialized() {
!     return initialized;
!   }
! 
!   /**
!    * Set this resouces initialized state
!    *
!    * @param initialized
!    */
!   protected void setInitialized(boolean initialized) {
!     this.initialized = initialized;
    }
  }

Index: ResourceFactory.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/resource/ResourceFactory.java,v
retrieving revision 1.5
retrieving revision 1.6
diff -C2 -d -r1.5 -r1.6
*** ResourceFactory.java	27 Jun 2003 02:19:59 -0000	1.5
--- ResourceFactory.java	15 Aug 2003 00:25:29 -0000	1.6
***************
*** 68,71 ****
--- 68,73 ----
  import com.babeldoc.core.I18n;
  import com.babeldoc.core.LogService;
+ import com.babeldoc.core.option.IConfigData;
+ import com.babeldoc.core.option.ConfigData;
  import com.babeldoc.core.config.ConfigService;
  
***************
*** 133,137 ****
  //      LogService.getInstance().logDebug("[ResourceFactory.getResource] resource not cached, creating");
        try {
!         String typeName = ConfigService.getString(RESOURCE + "/" + name, TYPE);
  
  //        LogService.getInstance().logDebug("[ResourceFactory.getResource]: Type: \""+typeName+"\"");
--- 135,140 ----
  //      LogService.getInstance().logDebug("[ResourceFactory.getResource] resource not cached, creating");
        try {
!         String resourceConfigName = RESOURCE + "/" + name;
!         String typeName = ConfigService.getString(resourceConfigName, TYPE);
  
  //        LogService.getInstance().logDebug("[ResourceFactory.getResource]: Type: \""+typeName+"\"");
***************
*** 142,145 ****
--- 145,150 ----
              resource = (Resource) classObj.newInstance();
              resource.setName(name);
+             IConfigData configData = ConfigData.getConfigData("root", resourceConfigName);
+             resource.getInfo().applyConfigData(configData);
              getInstance().resources.put(name, resource);
            } else {

[Babeldoc-devel] babeldoc/modules/sql/src/com/babeldoc/sql/pipeline/stage SqlEnrichPipelineStage.java,1.14,1.15 SqlQueryPipelineStage.java,1.4,1.5 SqlWriterPipelineStage.java,1.14,1.15

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/pipeline/stage
In directory sc8-pr-cvs1:/tmp/cvs-serv6089/sql/src/com/babeldoc/sql/pipeline/stage

Modified Files:
	SqlEnrichPipelineStage.java SqlQueryPipelineStage.java 
	SqlWriterPipelineStage.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: SqlEnrichPipelineStage.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/pipeline/stage/SqlEnrichPipelineStage.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15

Index: SqlQueryPipelineStage.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/pipeline/stage/SqlQueryPipelineStage.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** SqlQueryPipelineStage.java	13 Aug 2003 22:44:30 -0000	1.4
--- SqlQueryPipelineStage.java	15 Aug 2003 00:25:30 -0000	1.5
***************
*** 126,130 ****
  
        public String getDescription() {
!         return I18n.get("sql.pipeline.stage.query.desc");
        }
  
--- 126,130 ----
  
        public String getDescription() {
!         return I18n.get("sql.900");
        }
  
***************
*** 132,144 ****
          ArrayList options = new ArrayList();
          options.add(new ConfigOption(RESOURCE_NAME, IConfigOptionType.STRING,
!             null, true, I18n.get("sql.pipeline.stage.query.option.resource")));
  
          IConfigOptionType queries = new ComplexConfigOptionType(new ConfigOption[]{
!           new ConfigOption(SQL, IConfigOptionType.MULTI, null, false,
!               I18n.get("sql.pipeline.stage.query.option.sql"))
          });
  
          options.add(new ConfigOption(SQL, queries,
!             null, false, I18n.get("sql.pipeline.stage.query.option.sql")));
  
          return options;
--- 132,143 ----
          ArrayList options = new ArrayList();
          options.add(new ConfigOption(RESOURCE_NAME, IConfigOptionType.STRING,
!             null, true, I18n.get("sql.901")));
  
          IConfigOptionType queries = new ComplexConfigOptionType(new ConfigOption[]{
!           new ConfigOption(SQL, IConfigOptionType.MULTI, null, false, I18n.get("sql.902"))
          });
  
          options.add(new ConfigOption(SQL, queries,
!             null, false, I18n.get("sql.106")));
  
          return options;
***************
*** 186,191 ****
        // Iterate through sqls
        if ((queries != null) && (queries.length > 0)) {
-         Element queryElement = root.addElement(QUERY);
          for (int i = 0; i < queries.length; ++i) {
            String queryName = queries[i].getName();
            queryElement.addAttribute(QUERY_NAME, queryName);
--- 185,190 ----
        // Iterate through sqls
        if ((queries != null) && (queries.length > 0)) {
          for (int i = 0; i < queries.length; ++i) {
+           Element queryElement = root.addElement(QUERY);
            String queryName = queries[i].getName();
            queryElement.addAttribute(QUERY_NAME, queryName);

Index: SqlWriterPipelineStage.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/pipeline/stage/SqlWriterPipelineStage.java,v
retrieving revision 1.14
retrieving revision 1.15
diff -C2 -d -r1.14 -r1.15

[Babeldoc-devel] babeldoc/modules/sql/src/com/babeldoc/sql/resource PooledJdbc.java,1.4,1.5 SimpleJdbc.java,1.3,1.4

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/resource
In directory sc8-pr-cvs1:/tmp/cvs-serv6089/sql/src/com/babeldoc/sql/resource

Modified Files:
	PooledJdbc.java SimpleJdbc.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: PooledJdbc.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/resource/PooledJdbc.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** PooledJdbc.java	14 Jul 2003 17:02:36 -0000	1.4
--- PooledJdbc.java	15 Aug 2003 00:25:30 -0000	1.5
***************
*** 66,71 ****
  package com.babeldoc.sql.resource;
  
- import com.babeldoc.core.resource.Resource;
  import com.babeldoc.core.resource.ResourceException;
  
  import org.apache.commons.dbcp.ConnectionFactory;
--- 66,71 ----
  package com.babeldoc.sql.resource;
  
  import com.babeldoc.core.resource.ResourceException;
+ import com.babeldoc.core.option.IConfigInfo;
  
  import org.apache.commons.dbcp.ConnectionFactory;
***************
*** 76,82 ****
  import org.apache.commons.pool.impl.GenericObjectPool;
  
- import java.sql.Connection;
- import java.sql.DriverManager;
- 
  
  /**
--- 76,79 ----
***************
*** 88,174 ****
   * @version 1.0
   */
! public class PooledJdbc extends Resource {
    /** the connection pool stuff. */
    private static PoolingDriver driver = new PoolingDriver();
  
-   /** the user and database url stuff. */
-   private static String DB_USER = "dbUser";
-   private static String DB_PASSWD = "dbPassword";
-   private static String DB_URL = "dbUrl";
- 
-   /** Jdbc variables */
-   private String dbName;
-   private String dbPasswd;
-   private String dbUrl;
- 
    /**
!    * Checkin this connection
     *
!    * @param connection
     *
!    * @throws ResourceException
     */
!   public void checkIn(Object connection) throws ResourceException {
!     try {
!       ((Connection) connection).close();
!     } catch (Exception e) {
!       throw new ResourceException("[ResourceException.checkIn]", e);
!     }
    }
  
    /**
!    * Get a new connection.
!    *
!    * @return the connection
     *
!    * @throws ResourceException
     */
!   public Object checkOut() throws ResourceException {
      try {
!       synchronized(this) {
!         // if we have no dbUrl, setup jdbc NOW
!         if (dbUrl == null) {
!           setupJdbc();
!         }
!       }
! 
!       return DriverManager.getConnection(dbUrl, dbName, dbPasswd);
      } catch (Exception e) {
!       throw new ResourceException("[ResourceException.checkOut]", e);
      }
    }
  
    /**
!    * TODO: DOCUMENT ME!
!    *
!    * @param connectURI DOCUMENT ME!
     *
!    * @throws Exception DOCUMENT ME!
     */
!   public void setupDriver(String connectURI) throws Exception {
!     ObjectPool connectionPool = new GenericObjectPool(null);
!     ConnectionFactory connectionFactory = new DriverManagerConnectionFactory(connectURI,
!         dbName, dbPasswd);
!     PoolableConnectionFactory poolableConnectionFactory = new PoolableConnectionFactory(connectionFactory,
!         connectionPool, null, null, false, true);
!     driver.registerPool(getName(), connectionPool);
! 
!     // convert to the url that talks to the connection pool
!     dbUrl = "jdbc:apache:commons:dbcp:" + getName();
!   }
  
!   /**
!    * Setup the jdbc stuff
!    *
!    * @throws Exception DOCUMENT ME!
!    */
!   private void setupJdbc() throws Exception {
!     try {
!       dbName = getConfig().getString(DB_USER);
!       dbPasswd = getConfig().getString(DB_PASSWD);
!       setupDriver(getConfig().getString(DB_URL));
!     } catch (Exception x) {
!       com.babeldoc.core.LogService.getInstance().logError(x);
      }
    }
  }
--- 85,154 ----
   * @version 1.0
   */
! public class PooledJdbc extends SimpleJdbc {
    /** the connection pool stuff. */
    private static PoolingDriver driver = new PoolingDriver();
  
    /**
!    * Now setup the connection pool - this means rewriting the URL to point instead
!    * to the apache connection pool
     *
!    * @param connectURI the connection uri to the underlying Jdbc driver
     *
!    * @throws Exception Oh, anything really!!!
     */
!   protected void setupConnectionPool(String connectURI) throws Exception {
!     ObjectPool connectionPool = new GenericObjectPool(null);
!     ConnectionFactory connectionFactory = new DriverManagerConnectionFactory(connectURI,
!         getDbName(), getDbPasswd());
!     PoolableConnectionFactory poolableConnectionFactory = new PoolableConnectionFactory(connectionFactory,
!         connectionPool, null, null, false, true);
!     driver.registerPool(getName(), connectionPool);
! 
!     // toXml to the url that talks to the connection pool
!     setDbUrl("jdbc:apache:commons:dbcp:" + getName());
    }
  
    /**
!    * Setup the jdbc stuff
     *
!    * @throws ResourceException DOCUMENT ME!
     */
!   protected void setup() throws ResourceException {
!     super.setup();
      try {
!       setupConnectionPool(getDbUrl());
      } catch (Exception e) {
!       throw new ResourceException("", e);
      }
    }
  
    /**
!    * Get the configuration iformation for this class
     *
!    * @return IConfigInfo object
     */
!   public IConfigInfo getInfo() {
!     if(info==null) {
!       info = new SimpleJdbcConfigInfo() {
!         /**
!          * Return description of this worker
!          *
!          * @return description
!          */
!         public String getDescription() {
!           return "Pooled jdbc connection resource.  CheckIn and Checkouts operate on a pool of connections.";
!         }
  
!         /**
!          * return the name
!          *
!          * @return
!          */
!         public String getName() {
!           return "pooled";
!         }
!       };
      }
+     return info;
    }
  }

Index: SimpleJdbc.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/resource/SimpleJdbc.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** SimpleJdbc.java	27 Jun 2003 02:05:59 -0000	1.3
--- SimpleJdbc.java	15 Aug 2003 00:25:30 -0000	1.4
***************
*** 68,78 ****
  import com.babeldoc.core.resource.Resource;
  import com.babeldoc.core.resource.ResourceException;
  
  import java.sql.Connection;
  import java.sql.DriverManager;
  
  
  /**
!  * How to get connections using the simplest jdbc code, etc.  This merely
   * creates new connections every time the resource is checked out.  Not too
   * good especially for drives / databases that have a limited number of
--- 68,84 ----
  import com.babeldoc.core.resource.Resource;
  import com.babeldoc.core.resource.ResourceException;
+ import com.babeldoc.core.resource.ResourceConfigInfo;
+ import com.babeldoc.core.option.IConfigInfo;
+ import com.babeldoc.core.option.ConfigOption;
+ import com.babeldoc.core.option.IConfigOptionType;
  
  import java.sql.Connection;
  import java.sql.DriverManager;
+ import java.util.Collection;
+ import java.util.ArrayList;
  
  
  /**
!  * How to getChild connections using the simplest jdbc code, etc.  This merely
   * creates new connections every time the resource is checked out.  Not too
   * good especially for drives / databases that have a limited number of
***************
*** 82,96 ****
   * @version 1.0
   */
! public class SimpleJdbc extends Resource {
    public static final String DB_USER = "dbUser";
    public static final String DB_PASSWD = "dbPassword";
    public static final String DB_DRIVER = "dbDriver";
    public static final String DB_URL = "dbUrl";
-   private String dbDriver;
  
    /** Jdbc variables */
!   private String dbName;
!   private String dbPasswd;
!   private String dbUrl;
  
    /**
--- 88,105 ----
   * @version 1.0
   */
! public class SimpleJdbc
!     extends Resource {
    public static final String DB_USER = "dbUser";
    public static final String DB_PASSWD = "dbPassword";
    public static final String DB_DRIVER = "dbDriver";
    public static final String DB_URL = "dbUrl";
  
    /** Jdbc variables */
!   private String dbName = null;
!   private String dbPasswd = null;
!   private String dbUrl = null;
!   private String dbDriver = null;
! 
!   protected IConfigInfo info = null;
  
    /**
***************
*** 110,114 ****
  
    /**
!    * Get a new connection.
     *
     * @return the connection
--- 119,124 ----
  
    /**
!    * Get a new connection.  This method calls the super checkOut which
!    * does resouce initialization checking.
     *
     * @return the connection
***************
*** 117,127 ****
     */
    public synchronized Object checkOut() throws ResourceException {
!     try {
!       // if we have no dbUrl, setup jdbc NOW
!       if (dbUrl == null) {
!         setupJdbc();
!       }
  
!       return DriverManager.getConnection(dbUrl, dbName, dbPasswd);
      } catch (Exception e) {
        throw new ResourceException("[ResourceException.checkOut]", e);
--- 127,134 ----
     */
    public synchronized Object checkOut() throws ResourceException {
!     super.checkOut();
  
!     try {
!       return DriverManager.getConnection(getDbUrl(), getDbName(), getDbPasswd());
      } catch (Exception e) {
        throw new ResourceException("[ResourceException.checkOut]", e);
***************
*** 130,150 ****
  
    /**
!    * Setup the jdbc stuff
     */
!   private void setupJdbc() {
!     try {
!       dbName = getConfig().getString(DB_USER);
!       dbPasswd = getConfig().getString(DB_PASSWD);
!       dbDriver = getConfig().getString(DB_DRIVER);
!       dbUrl = getConfig().getString(DB_URL);
! 
!       if ((dbName != null) && (dbPasswd != null) && (dbDriver != null) &&
!             (dbUrl != null)) {
!         Class.forName(dbDriver).newInstance();
        }
!     } catch (Exception x) {
!       com.babeldoc.core.LogService.getInstance().logError(x);
!       dbUrl = null;
      }
    }
  }
--- 137,298 ----
  
    /**
!    * Setup the jdbc stuff.  This largely ensures that all the four components of the
!    * sql resource are provided and that the driver class
!    *
!    * @throws ResourceException
     */
!   protected void setup() throws ResourceException {
!     if ((getDbName() != null) &&
!         (getDbPasswd() != null) &&
!         (getDbDriver() != null) &&
!         (getDbUrl() != null)) {
!       try {
!           Class.forName(getDbDriver()).newInstance();
!       } catch (Exception x) {
!         setDbUrl(null);
!         throw new ResourceException("Jdbc driver exception: ", x);
        }
!     } else {
!       throw new ResourceException("The resource is not COMPLETELY specified");
!     }
!   }
! 
!   /**
!    * Get the db user name - get from the config if not provided
!    *
!    * @return
!    */
!   protected String getDbName() {
!     if(dbName==null) {
!       dbName = getInfo().getStrValue(DB_USER);
!     }
!     return dbName;
!   }
! 
!   /**
!    * Set the db username
!    *
!    * @param dbName
!    */
!   protected void setDbName(String dbName) {
!     this.dbName = dbName;
!   }
! 
!   /**
!    * get the db password
!    *
!    * @return
!    */
!   protected String getDbPasswd() {
!     if(dbPasswd==null) {
!       dbPasswd = getInfo().getStrValue(DB_PASSWD);
!     }
!     return dbPasswd;
!   }
! 
!   /**
!    * Set the db password
!    *
!    * @param dbPasswd
!    */
!   protected void setDbPasswd(String dbPasswd) {
!     this.dbPasswd = dbPasswd;
!   }
! 
!   /**
!    * get the db url
!    *
!    * @return
!    */
!   protected String getDbUrl() {
!     if(dbUrl==null) {
!       dbUrl=getInfo().getStrValue(DB_URL);
      }
+     return dbUrl;
+   }
+ 
+   /**
+    * Set the db url
+    *
+    * @param dbUrl
+    */
+   protected void setDbUrl(String dbUrl) {
+     this.dbUrl = dbUrl;
+   }
+ 
+   /**
+    * Get the db driver
+    *
+    * @return
+    */
+   protected String getDbDriver() {
+     if(dbDriver==null) {
+       dbDriver=getInfo().getStrValue(DB_DRIVER);
+     }
+     return dbDriver;
+   }
+ 
+   /**
+    * set the db driver
+    *
+    * @param dbDriver
+    */
+   protected void setDbDriver(String dbDriver) {
+     this.dbDriver = dbDriver;
+   }
+ 
+   /**
+    * Get the configuration iformation for this class
+    *
+    * @return IConfigInfo object
+    */
+   public IConfigInfo getInfo() {
+     if(info==null) {
+       info = new SimpleJdbcConfigInfo();
+     }
+     return info;
+   }
+ }
+ 
+ 
+ /**
+  * Manage the configuration options for resources.
+  */
+ class SimpleJdbcConfigInfo
+     extends ResourceConfigInfo{
+   /**
+    * This method returns type specific options
+    *
+    * @return comments
+    */
+   public Collection getTypeSpecificOptions() {
+     Collection options = new ArrayList();
+     options.add(new ConfigOption(SimpleJdbc.DB_USER, IConfigOptionType.STRING,
+           null, true, "Database user to logon with"));
+     options.add(new ConfigOption(SimpleJdbc.DB_PASSWD, IConfigOptionType.STRING,
+           null, true, "Database user password to logon with"));
+     options.add(new ConfigOption(SimpleJdbc.DB_DRIVER, IConfigOptionType.STRING,
+           null, true, "JDBC Driver class to manage the connection to your database.  See your vendors documentation.  This has to be in the classpath"));
+     options.add(new ConfigOption(SimpleJdbc.DB_URL, IConfigOptionType.STRING,
+           null, true, "The JDBC connection string.  This generally contains the database name, etc.  See your vendors documentation."));
+     return options;
+   }
+ 
+   /**
+    * Return description of this worker
+    *
+    * @return description
+    */
+   public String getDescription() {
+     return "Simple, non-pooled jdbc connection resource.  CheckIn and Checkouts create and destroy connections";
+   }
+ 
+   /**
+    * return the name
+    *
+    * @return
+    */
+   public String getName() {
+     return "jdbc";
    }
  }

[Babeldoc-devel] babeldoc/modules/sql/src/com/babeldoc/sql/user SqlOrganization.java,1.4,1.5 SqlUserFactory.java,1.4,1.5 SqlUserResourceFactory.java,1.3,1.4

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/user
In directory sc8-pr-cvs1:/tmp/cvs-serv6089/sql/src/com/babeldoc/sql/user

Modified Files:
	SqlOrganization.java SqlUserFactory.java 
	SqlUserResourceFactory.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: SqlOrganization.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/user/SqlOrganization.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** SqlOrganization.java	27 Jun 2003 02:05:59 -0000	1.4
--- SqlOrganization.java	15 Aug 2003 00:25:30 -0000	1.5
***************
*** 118,122 ****
  
    /**
!    * get the parent organization object -
     *
     * @return
--- 118,122 ----
  
    /**
!    * getChild the parent organization object -
     *
     * @return

Index: SqlUserFactory.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/user/SqlUserFactory.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -C2 -d -r1.4 -r1.5
*** SqlUserFactory.java	19 Jul 2003 15:32:28 -0000	1.4
--- SqlUserFactory.java	15 Aug 2003 00:25:30 -0000	1.5
***************
*** 100,116 ****
    public static final String RESOURCE_NAME = "resourceName";
  
!   /** constant: the name of the table when getting new keys */
    public static final String TABLE_ORG = "organization";
  
!   /** constant: the name of the table when getting new keys */
    public static final String TABLE_USER = "user";
  
!   /** constant:  the query to get the user by name */
    public static final String USER_GET_BY_NAME = "userGetByName";
  
!   /** constant:  the query to get the user by id */
    public static final String USER_GET_BY_ID = "userGetById";
  
!   /** constant:  the query to get the user by organization id */
    public static final String USER_GET_BY_ORG_ID = "userGetByOrgId";
  
--- 100,116 ----
    public static final String RESOURCE_NAME = "resourceName";
  
!   /** constant: the name of the table when getting new getChildrenNameSet */
    public static final String TABLE_ORG = "organization";
  
!   /** constant: the name of the table when getting new getChildrenNameSet */
    public static final String TABLE_USER = "user";
  
!   /** constant:  the query to getChild the user by name */
    public static final String USER_GET_BY_NAME = "userGetByName";
  
!   /** constant:  the query to getChild the user by id */
    public static final String USER_GET_BY_ID = "userGetById";
  
!   /** constant:  the query to getChild the user by organization id */
    public static final String USER_GET_BY_ORG_ID = "userGetByOrgId";
  
***************
*** 121,128 ****
    public static final String USER_DELETE = "userDelete";
  
!   /** constant:  get a named organization */
    public static final String ORG_GET_BY_NAME = "orgGetByName";
  
!   /** constant:  get an organization */
    public static final String ORG_GET_BY_ID = "orgGetById";
  
--- 121,128 ----
    public static final String USER_DELETE = "userDelete";
  
!   /** constant:  getChild a named organization */
    public static final String ORG_GET_BY_NAME = "orgGetByName";
  
!   /** constant:  getChild an organization */
    public static final String ORG_GET_BY_ID = "orgGetById";
  
***************
*** 165,169 ****
    /**
     * construct a sql user factory connect to the configuration service and then
!    * get the resource.
     */
    public SqlUserFactory() {
--- 165,169 ----
    /**
     * construct a sql user factory connect to the configuration service and then
!    * getChild the resource.
     */
    public SqlUserFactory() {
***************
*** 225,229 ****
  
    /**
!    * Get organization object. get a user context object for the named user.
     * This object is by default unauthenticated.  If the user is not found, the
     * context object is null.
--- 225,229 ----
  
    /**
!    * Get organization object. getChild a user context object for the named user.
     * This object is by default unauthenticated.  If the user is not found, the
     * context object is null.
***************
*** 278,282 ****
     * for the resource in a certain order.
     *
!    * @param org the org to get preference
     * @param key
     *
--- 278,282 ----
     * for the resource in a certain order.
     *
!    * @param org the org to getChild preference
     * @param key
     *
***************
*** 325,329 ****
  
    /**
!    * Get user context object. get a user context object for the named user.
     * This object is by default unauthenticated.  If the user is not found, the
     * context object is null.
--- 325,329 ----
  
    /**
!    * Get user context object. getChild a user context object for the named user.
     * This object is by default unauthenticated.  If the user is not found, the
     * context object is null.
***************
*** 383,387 ****
  
    /**
!    * Get user context object. get a user context object for the named user.
     * This opject is by default unauthenticated.
     *
--- 383,387 ----
  
    /**
!    * Get user context object. getChild a user context object for the named user.
     * This opject is by default unauthenticated.
     *
***************
*** 410,414 ****
     * resource in a certain order.  Returns null if no preference is found.
     *
!    * @param user the user to get preference
     * @param key the reference to the preference
     *
--- 410,414 ----
     * resource in a certain order.  Returns null if no preference is found.
     *
!    * @param user the user to getChild preference
     * @param key the reference to the preference
     *
***************
*** 794,798 ****
     * Dlete the preference string for the organization.
     *
!    * @param org the org to get preference
     * @param key the preference name
     *
--- 794,798 ----
     * Dlete the preference string for the organization.
     *
!    * @param org the org to getChild preference
     * @param key the preference name
     *
***************
*** 910,914 ****
  
    /**
!    * using md5, get a hash for the string.
     *
     * @param string
--- 910,914 ----
  
    /**
!    * using md5, getChild a hash for the string.
     *
     * @param string
***************
*** 939,943 ****
  
    /**
!    * Get organization object. get a user context object for the named user.
     * This object is by default unauthenticated.  If the user is not found, the
     * context object is null.
--- 939,943 ----
  
    /**
!    * Get organization object. getChild a user context object for the named user.
     * This object is by default unauthenticated.  If the user is not found, the
     * context object is null.

Index: SqlUserResourceFactory.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/sql/src/com/babeldoc/sql/user/SqlUserResourceFactory.java,v
retrieving revision 1.3
retrieving revision 1.4
diff -C2 -d -r1.3 -r1.4
*** SqlUserResourceFactory.java	27 Jun 2003 02:05:59 -0000	1.3
--- SqlUserResourceFactory.java	15 Aug 2003 00:25:30 -0000	1.4
***************
*** 108,115 ****
    public static final String RES_GET_BY_ID = "resGetById";
  
!   /** constant: get user id for resource */
    public static final String RES_GET_USER_FOR_RES = "resGetUserForRes";
  
!   /** constant: get org id for resource */
    public static final String RES_GET_ORG_FOR_RES = "resGetOrgForRes";
  
--- 108,115 ----
    public static final String RES_GET_BY_ID = "resGetById";
  
!   /** constant: getChild user id for resource */
    public static final String RES_GET_USER_FOR_RES = "resGetUserForRes";
  
!   /** constant: getChild org id for resource */
    public static final String RES_GET_ORG_FOR_RES = "resGetOrgForRes";
  
***************
*** 430,434 ****
    /**
     * Get a an array of resources id corresponding to the parts of the resource
!    * tree. This is a very useful feature that will get used subsequently
     *
     * @param connection the connection
--- 430,434 ----
    /**
     * Get a an array of resources id corresponding to the parts of the resource
!    * tree. This is a very useful feature that will getChild used subsequently
     *
     * @param connection the connection
***************
*** 487,491 ****
    /**
     * Get a an array of resources id corresponding to the parts of the resource
!    * tree. This is a very useful feature that will get used subsequently
     *
     * @param userResource the resource
--- 487,491 ----
    /**
     * Get a an array of resources id corresponding to the parts of the resource
!    * tree. This is a very useful feature that will getChild used subsequently
     *
     * @param userResource the resource

[Babeldoc-devel] babeldoc/modules/core/src/com/babeldoc/core/option ConfigData.java,1.2,1.3 ConfigInfo.java,1.8,1.9 ConfigOption.java,1.12,1.13 IConfigInfo.java,1.6,1.7

[<tr...@us...>]

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

Modified Files:
	ConfigData.java ConfigInfo.java ConfigOption.java 
	IConfigInfo.java 
Log Message:
Resources now are Configurable.  Added dbDriver configuration option to sql resources.  Lots of work on the resources - made things more logical from a SW POV.  Added Null scanner.

Index: ConfigData.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/option/ConfigData.java,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -d -r1.2 -r1.3

Index: ConfigInfo.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/option/ConfigInfo.java,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** ConfigInfo.java	13 Aug 2003 22:53:26 -0000	1.8
--- ConfigInfo.java	15 Aug 2003 00:25:29 -0000	1.9
***************
*** 72,75 ****
--- 72,77 ----
  import java.util.*;
  
+ import org.apache.commons.lang.NumberUtils;
+ 
  
  /**
***************
*** 85,92 ****
--- 87,100 ----
    /** Those options which are required */
    protected Collection mandatory = null;
+ 
    /** The complete set of options */
    protected Map options = null;
+ 
+   /** The configuration data */
+   private IConfigData configData;
+ 
    /** The descript of dynamic option */
    public static final String DYNAMIC_OPTION_DESC = "dynamically created config option";
+ 
    /** The description of the dynamic complex option */
    public static final String DYNAMIC_COMPLEX_OPTION_DESC = "dynamically created complex config option";
***************
*** 195,198 ****
--- 203,246 ----
  
    /**
+    * Get the option value in the path of options.  The path is
+    * specificed like a file path:  /option/suboption/etc
+    *
+    * @param path
+    * @return value
+    */
+   public Object getValue(String path) {
+     ConfigOption option = getOptionInPath(path);
+     if(option!=null) {
+       return option.getValue();
+     } else {
+       return null;
+     }
+   }
+ 
+   /**
+    * Get the option value in the path of options.  The path is
+    * specificed like a file path:  /option/suboption/etc
+    *
+    * @param path
+    * @return value
+    */
+   public String getStrValue(String path) {
+     return (String)getValue(path);
+   }
+ 
+   /**
+    * Get the option value in the path of options.  The path is
+    * specificed like a file path:  /option/suboption/etc.  Values
+    * not found, nulls, etc are returned as 0.
+    *
+    * @param path
+    * @return value
+    */
+   public int getIntValue(String path) {
+     return NumberUtils.stringToInt((String)getValue(path), 0);
+   }
+ 
+ 
+   /**
     * Get all the options.
     *
***************
*** 277,280 ****
--- 325,329 ----
     */
    public void applyConfigData(IConfigData data) {
+     this.setConfigData(data);
      for (Iterator iterator = data.getChildrenNameSet().iterator(); iterator.hasNext();) {
        String key = (String) iterator.next();
***************
*** 351,354 ****
--- 400,421 ----
  
      return dynamic;
+   }
+ 
+   /**
+    * Get the configuration data that has been set on this object
+    *
+    * @return
+    */
+   protected IConfigData getConfigData() {
+     return configData;
+   }
+ 
+   /**
+    * Set the configuration data on this object
+    *
+    * @param configData
+    */
+   protected void setConfigData(IConfigData configData) {
+     this.configData = configData;
    }
  }

Index: ConfigOption.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/option/ConfigOption.java,v
retrieving revision 1.12
retrieving revision 1.13
diff -C2 -d -r1.12 -r1.13
*** ConfigOption.java	13 Aug 2003 22:53:26 -0000	1.12
--- ConfigOption.java	15 Aug 2003 00:25:29 -0000	1.13
***************
*** 443,447 ****
      return "Option='" + name + "' type='" + type + "' Description='" +
      description + "' Default value='" + defaultValue + "' Allowed Values=" +
!     allowed;
    }
  }
--- 443,447 ----
      return "Option='" + name + "' type='" + type + "' Description='" +
      description + "' Default value='" + defaultValue + "' Allowed Values=" +
!     allowed+" value='"+value+"'";
    }
  }

Index: IConfigInfo.java
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/core/src/com/babeldoc/core/option/IConfigInfo.java,v
retrieving revision 1.6
retrieving revision 1.7
diff -C2 -d -r1.6 -r1.7
*** IConfigInfo.java	13 Aug 2003 22:53:26 -0000	1.6
--- IConfigInfo.java	15 Aug 2003 00:25:29 -0000	1.7
***************
*** 142,144 ****
--- 142,173 ----
     */
    boolean isValid();
+ 
+ 
+   /**
+    * Get the option value in the path of options.  The path is
+    * specificed like a file path:  /option/suboption/etc
+    *
+    * @param path
+    * @return value
+    */
+   public Object getValue(String path);
+ 
+     /**
+    * Get the option value in the path of options.  The path is
+    * specificed like a file path:  /option/suboption/etc
+    *
+    * @param path
+    * @return value
+    */
+   public String getStrValue(String path);
+ 
+   /**
+    * Get the option value in the path of options.  The path is
+    * specificed like a file path:  /option/suboption/etc.  Values
+    * not found, nulls, etc are returned as 0.
+    *
+    * @param path
+    * @return value
+    */
+   public int getIntValue(String path);
  }

[Babeldoc-devel] Adding examples to User Guide?

[David G. <dg...@co...>]

Hi Bruce,

I'd like to add examples to the Users Guide to cover at the least the issues 
that I faced coming up to speed with some of these stages. I'd like to add 
the examples in the Pipeline stage types section to keep them with the stage 
they illustrate.  However, it looks like this section is auto-generated from 
the source.  How would you recommend I proceed?


Thanks,

David

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

[Babeldoc-devel] babeldoc/modules/scanner/config/i18n messages.properties,1.11,1.12

[<tr...@us...>]

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

Modified Files:
	messages.properties 
Log Message:
Added null scanner - does nothing - submits an empty document to the pipeline when the thread runs.

Index: messages.properties
===================================================================
RCS file: /cvsroot/babeldoc/babeldoc/modules/scanner/config/i18n/messages.properties,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -d -r1.11 -r1.12
*** messages.properties	31 May 2003 01:46:01 -0000	1.11
--- messages.properties	14 Aug 2003 23:57:19 -0000	1.12
***************
*** 94,97 ****
--- 94,99 ----
  scanner.HttpScanner.error.failed=Failed to download from: {0}
  
+ scanner.nullScanner.desc=Null Scanner feeds null documents everytime the scanner runs.  This is useful for scheduling.
+ 
  scanner.001=Started
  scanner.002=Stopped

[Babeldoc-devel] babeldoc/modules/scanner/src/com/babeldoc/scanner/worker NullScanner.java,NONE,1.1

[<tr...@us...>]

Update of /cvsroot/babeldoc/babeldoc/modules/scanner/src/com/babeldoc/scanner/worker
In directory sc8-pr-cvs1:/tmp/cvs-serv1614/src/com/babeldoc/scanner/worker

Added Files:
	NullScanner.java 
Log Message:
Added null scanner - does nothing - submits an empty document to the pipeline when the thread runs.

--- NEW FILE: NullScanner.java ---
package com.babeldoc.scanner.worker;

import com.babeldoc.scanner.ScannerWorker;
import com.babeldoc.scanner.ScannerException;
import com.babeldoc.scanner.ScannerConfigurationException;
import com.babeldoc.scanner.ScannerWorkerInfo;
import com.babeldoc.core.option.IConfigInfo;
import com.babeldoc.core.I18n;

import java.util.Collection;

/**
 * A do-nothing scanner - this just runs regularly and feeds a document which contains
 * a null body.  It is assumed that the pipeline will actually do the work of getting
 * data into the pipeline.
 *
 * @author bmcdonald
 * @version 1.1
 */
public class NullScanner
    extends ScannerWorker{
  /**
   * Get the information object
   *
   * @return information object
   */
  public IConfigInfo getInfo() {
    return new ScannerWorkerInfo() {
      /**
       * This method returns type specific options
       *
       * @return comments
       */
      public Collection getTypeSpecificOptions() {
        return null;
      }

      /**
       * Return description of this worker
       *
       * @return description
       */
      public String getDescription() {
        return I18n.get("scanner.nullScanner.desc");
      }

      /**
       * return the name
       *
       * @return
       */
      public String getName() {
        return null;
      }
    };
  }

  /**
   * Do the scan - this does not actually do anything - it just fires up the pipeline processing.
   *
   * @throws ScannerException if anything goes wrong
   */
  public void doScan()
      throws ScannerException {
    enqueue(null, "");
  }

  /**
   * release the held resource.
   */
  public void relinquishResources() {
  }

  /**
   * This method is called when worker is being initialized. It should be  do
   * all needed initalization stuff.
   */
  protected void initialize()
      throws ScannerConfigurationException {
  }
}