babeldoc-devel — Babeldoc developer list

[Babeldoc-devel] Re: More JDK 1.3.1 incompatibilities

[bruce <br...@mc...>]

Yes, delete the modules - for now...

On Monday 31 March 2003 02:28 pm, ek...@ba... wrote:
> java.net.URLEncoder and java.net.URLDecoder have a 2-arg constructor in
> JDK 1.4 as well as a 1-arg constructor (which is now deprecated).  The
> 2nd argument is a String that represents the character encoding (such as
> UTF-8).  JDK 1.3.1 only has the 1-arg constructor.  I have not
> identified a way to set the encoding outside of the constructor.
>
> This situation is causing a compiler error in the following classes:
>
> com.babeldoc.web.context.JournalListingContext -- Line184
> com.babeldoc.babelfish.BabelfishTranslator -- Lines 102, 103, 230
>
> Any thoughts?
>
> Erik

[Babeldoc-devel] Re: More JDK 1.3.1 incompatibilities

[bruce <br...@mc...>]

On Monday 31 March 2003 02:28 pm, ek...@ba... wrote:
> java.net.URLEncoder and java.net.URLDecoder have a 2-arg constructor in
> JDK 1.4 as well as a 1-arg constructor (which is now deprecated).  The
> 2nd argument is a String that represents the character encoding (such as
> UTF-8).  JDK 1.3.1 only has the 1-arg constructor.  I have not
> identified a way to set the encoding outside of the constructor.
>
> This situation is causing a compiler error in the following classes:
>
> com.babeldoc.web.context.JournalListingContext -- Line184
> com.babeldoc.babelfish.BabelfishTranslator -- Lines 102, 103, 230
>
> Any thoughts?
>
> Erik

[Babeldoc-devel] More JDK 1.3.1 incompatibilities

[<ek...@ba...>]

java.net.URLEncoder and java.net.URLDecoder have a 2-arg constructor in
JDK 1.4 as well as a 1-arg constructor (which is now deprecated).  The
2nd argument is a String that represents the character encoding (such as
UTF-8).  JDK 1.3.1 only has the 1-arg constructor.  I have not
identified a way to set the encoding outside of the constructor.

This situation is causing a compiler error in the following classes:

com.babeldoc.web.context.JournalListingContext -- Line184
com.babeldoc.babelfish.BabelfishTranslator -- Lines 102, 103, 230

Any thoughts?

Erik

Re: [Babeldoc-devel] Modifications for PipelineCommand and PipelineDocument

[bruce <br...@mc...>]

Done

On Monday 31 March 2003 01:30 pm, ek...@ba... wrote:
> (See attached file: PipelineCommand.java)  See line 126
> (See attached file: PipelineDocument.java)    See line 299
>
> Please checkin to CVS (until I'm able to).
> The information in this e-mail, and any attachment therein, is
> confidential and for use by the addressee only. If you are not the
> intended recipient, please return the e-mail to the sender and delete it
> from your computer. Although The Bank of New York attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that either
> are virus-free and accepts no liability for any damage sustained as a
> result of viruses.

[Babeldoc-devel] Modifications for PipelineCommand and PipelineDocument

[<ek...@ba...>]

(See attached file: PipelineCommand.java)  See line 126
(See attached file: PipelineDocument.java)    See line 299

Please checkin to CVS (until I'm able to).
The information in this e-mail, and any attachment therein, is
confidential and for use by the addressee only. If you are not the
intended recipient, please return the e-mail to the sender and delete it
from your computer. Although The Bank of New York attempts to sweep
e-mail and attachments for viruses, it does not guarantee that either
are virus-free and accepts no liability for any damage sustained as a
result of viruses.

Re: [Babeldoc-devel] Re: JDK 1.3.x Compatibility

[bruce <br...@mc...>]

Erik,

That is entirely likely.  This is going to be tricky

you can download from www.babeldoc.com

Go to the browse section - and go from there.  This gets rebuild every evening 
at 3am...

regards,
Bruce.

On Monday 31 March 2003 12:03 pm, ek...@ba... wrote:
> <<
> Here is the command string that works for me:
>
> /usr/bin/cvs -z3
> -d:pserver:ano...@cv...:/cvsroot/babeldoc co
> babeldoc_v1
>
> (all on one line)
>
> You need to login first...
>
> cvs -d:pserver:ano...@cv...:/cvsroot/babeldoc login
>
>
> I think I'm screwed here ... there's a VERY strong likelihood that my
> company's firewall is blocking my attempt to exit the private network
> and enter the internet on the default port (which I think is 2401).  I
> have NO WAY around this, except by going port 80.

Re: [Babeldoc-devel] Re: JDK 1.3.x Compatibility

[bruce <br...@mc...>]

Erik,

Here is the command string that works for me:

/usr/bin/cvs -z3    
-d:pserver:ano...@cv...:/cvsroot/babeldoc co 
babeldoc_v1

(all on one line)

You need to login first...

cvs -d:pserver:ano...@cv...:/cvsroot/babeldoc login 

regards,
Bruce.

On Monday 31 March 2003 11:44 am, ek...@ba... wrote:
> Thanks so much!!  I am attempting to connect to our CVS ... this is the
> connect string I am trying to use
>
> :pserver:ano...@cv...:cvsroot/babeldoc
>
> Not working.  Should I be using "ek...@ba..." rather than
> "anonymous"?  Is there a port number I should specify?  Should I be
> using SSH?
>
> Erik
>
>
>
>
>
> bruce <br...@mc...>@lists.sourceforge.net on 03/31/2003
> 11:24:35 AM
>
> Sent by:    bab...@li...
>
>
> To:    "Babeldoc Developers List" <bab...@li...>
> cc:
> Subject:    [Babeldoc-devel] Re: JDK 1.3.x Compatibility
>
>
> All done - the only thing is that JavaXmlDecoder.  Just delete that
> class -
> there is no way to make that work under 1.3 since it explicitly needs
> 1.4
> support.
>
> regards,
> Bruce.
>
> On Monday 31 March 2003 11:01 am, ek...@ba... wrote:
> > ---------------------- Forwarded by Erik Klein/NY/DOMESTIC/BNY on
> > 03/31/2003 11:01 AM ---------------------------
> >
> >
> > Erik Klein
> > 03/31/2003 10:42 AM
> >
> > To:    "Babeldoc Developers List"
>
> <bab...@li...>
>
> > cc:
> > Subject:    JDK 1.3.x Compatibility  (Document link: Erik Klein)
> >
> >
> > Bruce,
> >
> > I have downloaded the three programs you have modified since I have
> > shown interest in Babeldoc (LogService.java, ConfigService.java, and
> > XslTransformPipelineStage.java).  This morning I attempted to do an
>
> ant
>
> > build using my JDK 1.3.1 compiler (and the programs listed above) and
> > received the following compiler errors:
> >
> >
> > D:\Program Files\babeldoc\src>build
> > Buildfile: build.xml
> >
> > declare:
> >
> > depends:
> >      [echo] Build order: core babelfish conversion crypto sql scanner
> > gui web soap
> >
> > build:
> >      [echo] Building Babeldoc in: D:\Program Files\babeldoc\src
> >
> > build:
> >      [echo] Building core
> >     [javac] Compiling 144 source files to D:\Program
> > Files\babeldoc\src\modules\core\build
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\LogService.java:28:
> > cannot resolve symbol
> >     [javac] symbol  : class StackTraceElement
> >     [javac] location: package lang
> >     [javac] import java.lang.StackTraceElement;
> >     [javac]                  ^
> >
> >
> > This is simple ... we just need to comment out the "import" statement
>
> in
>
> > LogService.java
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>
> >lDecoderPipelineStage.java:28:
> >
> > cannot resolve symbol
> >     [javac] symbol  : class XMLDecoder
> >     [javac] location: package beans
> >     [javac] import java.beans.XMLDecoder;
> >     [javac]                   ^
> >
> >
> > I'm not sure how to handle this ... this class does not exist in the
> > java.beans package in JDK 1.3.1.  Do you know if this came from a
> > "previously optional" Jar, such as JAXP that I could put in the
> > classpath?  I looked through the JAXP and JAXB Jars (the best I could
> > find) and did not see this class in either one.  Any ideas?
> >
> >
> >     [javac] D:\Program
> > Files\babeldoc\src\modules\core\src\com\babeldoc\core\I18n.java:133:
> > MessageFormat(java.lang.String,java.util.Locale) has private acces
> > s in java.text.MessageFormat
> >     [javac]     format = new MessageFormat(escape(formatString),
> > locale);
> >     [javac]              ^
> >
> >
> > This constructor does not exist in the JDK 1.3.1.  Rather, I believe
> > this can be implemented as:
> > format = new MessageFormat(escape(formatString));
> > format.setLocale(locale);
> >
> > Any objection?
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\PipelineDocu
>
> >ment.java:296:
> >
> > cannot resolve symbol
> >     [javac] symbol  : method toString  (boolean)
> >     [javac] location: class java.lang.Boolean
> >     [javac]     String bool = Boolean.toString(binary);
> >     [javac]                          ^
> >
> >
> > This static method does not exist in JDK 1.3.1.  My workaround for it
> > is:
> > (Boolean.valueOf(binary)).toString();
> >
> > Any objection?
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\command\Pipe
>
> >lineCommand.java:126:
> >
> > cannot resolve symbol
> >     [javac] symbol  : method toString  (boolean)
> >     [javac] location: class java.lang.Boolean
> >     [javac]           System.out.print(I18n.get("008004",
> > Boolean.toString(tracked)));
> >     [javac]                                                      ^
> >
> >
> > See above
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>
> >lDecoderPipelineStage.java:74:
> >
> > cannot resolve symbol
> >     [javac] symbol  : class XMLDecoder
> >     [javac] location: class
> > com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
> >     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
> >     [javac]     ^
> >
> >
> > See above
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>
> >lDecoderPipelineStage.java:74:
> >
> > cannot resolve symbol
> >     [javac] symbol  : class XMLDecoder
> >     [javac] location: class
> > com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
> >     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
> >     [javac]                        ^
> >
> >
> > See above
> >
> >
> >     [javac] 7 errors
> >
> > BUILD FAILED
> > file:D:/Program Files/babeldoc/src/./modules/core/build.xml:23:
>
> Compile
>
> > failed; see the compiler error output for details.
> >
> > Total time: 14 seconds
> >
> >
> > The information in this e-mail, and any attachment therein, is
> > confidential and for use by the addressee only. If you are not the
> > intended recipient, please return the e-mail to the sender and delete
>
> it
>
> > from your computer. Although The Bank of New York attempts to sweep
> > e-mail and attachments for viruses, it does not guarantee that either
> > are virus-free and accepts no liability for any damage sustained as a
> > result of viruses.
>
> -------------------------------------------------------
> This SF.net email is sponsored by: ValueWeb:
> Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
> No other company gives more support or power for your dedicated server
> http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Re: JDK 1.3.x Compatibility

[<ek...@ba...>]

Thanks so much!!  I am attempting to connect to our CVS ... this is the
connect string I am trying to use

:pserver:ano...@cv...:cvsroot/babeldoc

Not working.  Should I be using "ek...@ba..." rather than
"anonymous"?  Is there a port number I should specify?  Should I be
using SSH?

Erik





bruce <br...@mc...>@lists.sourceforge.net on 03/31/2003
11:24:35 AM

Sent by:    bab...@li...


To:    "Babeldoc Developers List" <bab...@li...>
cc:
Subject:    [Babeldoc-devel] Re: JDK 1.3.x Compatibility


All done - the only thing is that JavaXmlDecoder.  Just delete that
class -
there is no way to make that work under 1.3 since it explicitly needs
1.4
support.

regards,
Bruce.


On Monday 31 March 2003 11:01 am, ek...@ba... wrote:
> ---------------------- Forwarded by Erik Klein/NY/DOMESTIC/BNY on
> 03/31/2003 11:01 AM ---------------------------
>
>
> Erik Klein
> 03/31/2003 10:42 AM
>
> To:    "Babeldoc Developers List"
<bab...@li...>
> cc:
> Subject:    JDK 1.3.x Compatibility  (Document link: Erik Klein)
>
>
> Bruce,
>
> I have downloaded the three programs you have modified since I have
> shown interest in Babeldoc (LogService.java, ConfigService.java, and
> XslTransformPipelineStage.java).  This morning I attempted to do an
ant
> build using my JDK 1.3.1 compiler (and the programs listed above) and
> received the following compiler errors:
>
>
> D:\Program Files\babeldoc\src>build
> Buildfile: build.xml
>
> declare:
>
> depends:
>      [echo] Build order: core babelfish conversion crypto sql scanner
> gui web soap
>
> build:
>      [echo] Building Babeldoc in: D:\Program Files\babeldoc\src
>
> build:
>      [echo] Building core
>     [javac] Compiling 144 source files to D:\Program
> Files\babeldoc\src\modules\core\build
>     [javac] D:\Program
>
Files\babeldoc\src\modules\core\src\com\babeldoc\core\LogService.java:28:

>
> cannot resolve symbol
>     [javac] symbol  : class StackTraceElement
>     [javac] location: package lang
>     [javac] import java.lang.StackTraceElement;
>     [javac]                  ^
>
>
> This is simple ... we just need to comment out the "import" statement
in
> LogService.java
>
>
>     [javac] D:\Program
>
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm

>lDecoderPipelineStage.java:28:
>
> cannot resolve symbol
>     [javac] symbol  : class XMLDecoder
>     [javac] location: package beans
>     [javac] import java.beans.XMLDecoder;
>     [javac]                   ^
>
>
> I'm not sure how to handle this ... this class does not exist in the
> java.beans package in JDK 1.3.1.  Do you know if this came from a
> "previously optional" Jar, such as JAXP that I could put in the
> classpath?  I looked through the JAXP and JAXB Jars (the best I could
> find) and did not see this class in either one.  Any ideas?
>
>
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\I18n.java:133:
> MessageFormat(java.lang.String,java.util.Locale) has private acces
> s in java.text.MessageFormat
>     [javac]     format = new MessageFormat(escape(formatString),
> locale);
>     [javac]              ^
>
>
> This constructor does not exist in the JDK 1.3.1.  Rather, I believe
> this can be implemented as:
> format = new MessageFormat(escape(formatString));
> format.setLocale(locale);
>
> Any objection?
>
>
>     [javac] D:\Program
>
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\PipelineDocu

>ment.java:296:
>
> cannot resolve symbol
>     [javac] symbol  : method toString  (boolean)
>     [javac] location: class java.lang.Boolean
>     [javac]     String bool = Boolean.toString(binary);
>     [javac]                          ^
>
>
> This static method does not exist in JDK 1.3.1.  My workaround for it
> is:
> (Boolean.valueOf(binary)).toString();
>
> Any objection?
>
>
>     [javac] D:\Program
>
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\command\Pipe

>lineCommand.java:126:
>
> cannot resolve symbol
>     [javac] symbol  : method toString  (boolean)
>     [javac] location: class java.lang.Boolean
>     [javac]           System.out.print(I18n.get("008004",
> Boolean.toString(tracked)));
>     [javac]                                                      ^
>
>
> See above
>
>
>     [javac] D:\Program
>
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm

>lDecoderPipelineStage.java:74:
>
> cannot resolve symbol
>     [javac] symbol  : class XMLDecoder
>     [javac] location: class
> com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
>     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
>     [javac]     ^
>
>
> See above
>
>
>     [javac] D:\Program
>
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm

>lDecoderPipelineStage.java:74:
>
> cannot resolve symbol
>     [javac] symbol  : class XMLDecoder
>     [javac] location: class
> com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
>     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
>     [javac]                        ^
>
>
> See above
>
>
>     [javac] 7 errors
>
> BUILD FAILED
> file:D:/Program Files/babeldoc/src/./modules/core/build.xml:23:
Compile
> failed; see the compiler error output for details.
>
> Total time: 14 seconds
>
>
> The information in this e-mail, and any attachment therein, is
> confidential and for use by the addressee only. If you are not the
> intended recipient, please return the e-mail to the sender and delete
it
> from your computer. Although The Bank of New York attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that either
> are virus-free and accepts no liability for any damage sustained as a
> result of viruses.


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
_______________________________________________
Babeldoc-devel mailing list
Bab...@li...
https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

[Babeldoc-devel] Re: JDK 1.3.x Compatibility

[bruce <br...@mc...>]

All done - the only thing is that JavaXmlDecoder.  Just delete that class - 
there is no way to make that work under 1.3 since it explicitly needs 1.4 
support.

regards,
Bruce.


On Monday 31 March 2003 11:01 am, ek...@ba... wrote:
> ---------------------- Forwarded by Erik Klein/NY/DOMESTIC/BNY on
> 03/31/2003 11:01 AM ---------------------------
>
>
> Erik Klein
> 03/31/2003 10:42 AM
>
> To:    "Babeldoc Developers List" <bab...@li...>
> cc:
> Subject:    JDK 1.3.x Compatibility  (Document link: Erik Klein)
>
>
> Bruce,
>
> I have downloaded the three programs you have modified since I have
> shown interest in Babeldoc (LogService.java, ConfigService.java, and
> XslTransformPipelineStage.java).  This morning I attempted to do an ant
> build using my JDK 1.3.1 compiler (and the programs listed above) and
> received the following compiler errors:
>
>
> D:\Program Files\babeldoc\src>build
> Buildfile: build.xml
>
> declare:
>
> depends:
>      [echo] Build order: core babelfish conversion crypto sql scanner
> gui web soap
>
> build:
>      [echo] Building Babeldoc in: D:\Program Files\babeldoc\src
>
> build:
>      [echo] Building core
>     [javac] Compiling 144 source files to D:\Program
> Files\babeldoc\src\modules\core\build
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\LogService.java:28:
>
> cannot resolve symbol
>     [javac] symbol  : class StackTraceElement
>     [javac] location: package lang
>     [javac] import java.lang.StackTraceElement;
>     [javac]                  ^
>
>
> This is simple ... we just need to comment out the "import" statement in
> LogService.java
>
>
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>lDecoderPipelineStage.java:28:
>
> cannot resolve symbol
>     [javac] symbol  : class XMLDecoder
>     [javac] location: package beans
>     [javac] import java.beans.XMLDecoder;
>     [javac]                   ^
>
>
> I'm not sure how to handle this ... this class does not exist in the
> java.beans package in JDK 1.3.1.  Do you know if this came from a
> "previously optional" Jar, such as JAXP that I could put in the
> classpath?  I looked through the JAXP and JAXB Jars (the best I could
> find) and did not see this class in either one.  Any ideas?
>
>
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\I18n.java:133:
> MessageFormat(java.lang.String,java.util.Locale) has private acces
> s in java.text.MessageFormat
>     [javac]     format = new MessageFormat(escape(formatString),
> locale);
>     [javac]              ^
>
>
> This constructor does not exist in the JDK 1.3.1.  Rather, I believe
> this can be implemented as:
> format = new MessageFormat(escape(formatString));
> format.setLocale(locale);
>
> Any objection?
>
>
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\PipelineDocu
>ment.java:296:
>
> cannot resolve symbol
>     [javac] symbol  : method toString  (boolean)
>     [javac] location: class java.lang.Boolean
>     [javac]     String bool = Boolean.toString(binary);
>     [javac]                          ^
>
>
> This static method does not exist in JDK 1.3.1.  My workaround for it
> is:
> (Boolean.valueOf(binary)).toString();
>
> Any objection?
>
>
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\command\Pipe
>lineCommand.java:126:
>
> cannot resolve symbol
>     [javac] symbol  : method toString  (boolean)
>     [javac] location: class java.lang.Boolean
>     [javac]           System.out.print(I18n.get("008004",
> Boolean.toString(tracked)));
>     [javac]                                                      ^
>
>
> See above
>
>
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>lDecoderPipelineStage.java:74:
>
> cannot resolve symbol
>     [javac] symbol  : class XMLDecoder
>     [javac] location: class
> com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
>     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
>     [javac]     ^
>
>
> See above
>
>
>     [javac] D:\Program
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>lDecoderPipelineStage.java:74:
>
> cannot resolve symbol
>     [javac] symbol  : class XMLDecoder
>     [javac] location: class
> com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
>     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
>     [javac]                        ^
>
>
> See above
>
>
>     [javac] 7 errors
>
> BUILD FAILED
> file:D:/Program Files/babeldoc/src/./modules/core/build.xml:23: Compile
> failed; see the compiler error output for details.
>
> Total time: 14 seconds
>
>
> The information in this e-mail, and any attachment therein, is
> confidential and for use by the addressee only. If you are not the
> intended recipient, please return the e-mail to the sender and delete it
> from your computer. Although The Bank of New York attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that either
> are virus-free and accepts no liability for any damage sustained as a
> result of viruses.

[Babeldoc-devel] Re: JDK 1.3.x Compatibility

[bruce <br...@mc...>]

You will need to read and implement these instructions:

0.  Get a login to SF.net 

1.  Intro to CVS
http://sourceforge.net/docman/display_doc.php?docid=14033&group_id=1    

2.  Developers and CVS
http://sourceforge.net/docman/display_doc.php?docid=768&group_id=1

3.  Details about using CVS on windows.
http://sourceforge.net/docman/display_doc.php?docid=766&group_id=1

On Monday 31 March 2003 11:05 am, ek...@ba... wrote:
> Ok, how do I get CVS access?  I used winCVS a few years ago ... but I'm
> no CVS expert.
>
>
>
>
>
> bruce <br...@mc...> on 03/31/2003 11:03:58 AM
>
> To:    ek...@ba...
> cc:    Dejan Krsmanovic <dej...@ya...>
> Subject:    Re: JDK 1.3.x Compatibility
>
>
> Ok,
>
> Getting on it now.  Eric you need CVS access...
>
> regards,
> Bruce.
>
> On Monday 31 March 2003 11:01 am, ek...@ba... wrote:
> > ---------------------- Forwarded by Erik Klein/NY/DOMESTIC/BNY on
> > 03/31/2003 11:01 AM ---------------------------
> >
> >
> > Erik Klein
> > 03/31/2003 10:42 AM
> >
> > To:    "Babeldoc Developers List"
>
> <bab...@li...>
>
> > cc:
> > Subject:    JDK 1.3.x Compatibility  (Document link: Erik Klein)
> >
> >
> > Bruce,
> >
> > I have downloaded the three programs you have modified since I have
> > shown interest in Babeldoc (LogService.java, ConfigService.java, and
> > XslTransformPipelineStage.java).  This morning I attempted to do an
>
> ant
>
> > build using my JDK 1.3.1 compiler (and the programs listed above) and
> > received the following compiler errors:
> >
> >
> > D:\Program Files\babeldoc\src>build
> > Buildfile: build.xml
> >
> > declare:
> >
> > depends:
> >      [echo] Build order: core babelfish conversion crypto sql scanner
> > gui web soap
> >
> > build:
> >      [echo] Building Babeldoc in: D:\Program Files\babeldoc\src
> >
> > build:
> >      [echo] Building core
> >     [javac] Compiling 144 source files to D:\Program
> > Files\babeldoc\src\modules\core\build
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\LogService.java:28:
> > cannot resolve symbol
> >     [javac] symbol  : class StackTraceElement
> >     [javac] location: package lang
> >     [javac] import java.lang.StackTraceElement;
> >     [javac]                  ^
> >
> >
> > This is simple ... we just need to comment out the "import" statement
>
> in
>
> > LogService.java
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>
> >lDecoderPipelineStage.java:28:
> >
> > cannot resolve symbol
> >     [javac] symbol  : class XMLDecoder
> >     [javac] location: package beans
> >     [javac] import java.beans.XMLDecoder;
> >     [javac]                   ^
> >
> >
> > I'm not sure how to handle this ... this class does not exist in the
> > java.beans package in JDK 1.3.1.  Do you know if this came from a
> > "previously optional" Jar, such as JAXP that I could put in the
> > classpath?  I looked through the JAXP and JAXB Jars (the best I could
> > find) and did not see this class in either one.  Any ideas?
> >
> >
> >     [javac] D:\Program
> > Files\babeldoc\src\modules\core\src\com\babeldoc\core\I18n.java:133:
> > MessageFormat(java.lang.String,java.util.Locale) has private acces
> > s in java.text.MessageFormat
> >     [javac]     format = new MessageFormat(escape(formatString),
> > locale);
> >     [javac]              ^
> >
> >
> > This constructor does not exist in the JDK 1.3.1.  Rather, I believe
> > this can be implemented as:
> > format = new MessageFormat(escape(formatString));
> > format.setLocale(locale);
> >
> > Any objection?
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\PipelineDocu
>
> >ment.java:296:
> >
> > cannot resolve symbol
> >     [javac] symbol  : method toString  (boolean)
> >     [javac] location: class java.lang.Boolean
> >     [javac]     String bool = Boolean.toString(binary);
> >     [javac]                          ^
> >
> >
> > This static method does not exist in JDK 1.3.1.  My workaround for it
> > is:
> > (Boolean.valueOf(binary)).toString();
> >
> > Any objection?
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\command\Pipe
>
> >lineCommand.java:126:
> >
> > cannot resolve symbol
> >     [javac] symbol  : method toString  (boolean)
> >     [javac] location: class java.lang.Boolean
> >     [javac]           System.out.print(I18n.get("008004",
> > Boolean.toString(tracked)));
> >     [javac]                                                      ^
> >
> >
> > See above
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>
> >lDecoderPipelineStage.java:74:
> >
> > cannot resolve symbol
> >     [javac] symbol  : class XMLDecoder
> >     [javac] location: class
> > com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
> >     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
> >     [javac]     ^
> >
> >
> > See above
> >
> >
> >     [javac] D:\Program
>
> Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXm
>
> >lDecoderPipelineStage.java:74:
> >
> > cannot resolve symbol
> >     [javac] symbol  : class XMLDecoder
> >     [javac] location: class
> > com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
> >     [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
> >     [javac]                        ^
> >
> >
> > See above
> >
> >
> >     [javac] 7 errors
> >
> > BUILD FAILED
> > file:D:/Program Files/babeldoc/src/./modules/core/build.xml:23:
>
> Compile
>
> > failed; see the compiler error output for details.
> >
> > Total time: 14 seconds
> >
> >
> > The information in this e-mail, and any attachment therein, is
> > confidential and for use by the addressee only. If you are not the
> > intended recipient, please return the e-mail to the sender and delete
>
> it
>
> > from your computer. Although The Bank of New York attempts to sweep
> > e-mail and attachments for viruses, it does not guarantee that either
> > are virus-free and accepts no liability for any damage sustained as a
> > result of viruses.

[Babeldoc-devel] JDK 1.3.x Compatibility

[<ek...@ba...>]

Bruce,

I have downloaded the three programs you have modified since I have
shown interest in Babeldoc (LogService.java, ConfigService.java, and
XslTransformPipelineStage.java).  This morning I attempted to do an ant
build using my JDK 1.3.1 compiler (and the programs listed above) and
received the following compiler errors:


D:\Program Files\babeldoc\src>build
Buildfile: build.xml

declare:

depends:
     [echo] Build order: core babelfish conversion crypto sql scanner
gui web soap

build:
     [echo] Building Babeldoc in: D:\Program Files\babeldoc\src

build:
     [echo] Building core
    [javac] Compiling 144 source files to D:\Program
Files\babeldoc\src\modules\core\build
    [javac] D:\Program
Files\babeldoc\src\modules\core\src\com\babeldoc\core\LogService.java:28:

cannot resolve symbol
    [javac] symbol  : class StackTraceElement
    [javac] location: package lang
    [javac] import java.lang.StackTraceElement;
    [javac]                  ^


This is simple ... we just need to comment out the "import" statement in
LogService.java


    [javac] D:\Program
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXmlDecoderPipelineStage.java:28:

cannot resolve symbol
    [javac] symbol  : class XMLDecoder
    [javac] location: package beans
    [javac] import java.beans.XMLDecoder;
    [javac]                   ^


I'm not sure how to handle this ... this class does not exist in the
java.beans package in JDK 1.3.1.  Do you know if this came from a
"previously optional" Jar, such as JAXP that I could put in the
classpath?  I looked through the JAXP and JAXB Jars (the best I could
find) and did not see this class in either one.  Any ideas?


    [javac] D:\Program
Files\babeldoc\src\modules\core\src\com\babeldoc\core\I18n.java:133:
MessageFormat(java.lang.String,java.util.Locale) has private acces
s in java.text.MessageFormat
    [javac]     format = new MessageFormat(escape(formatString),
locale);
    [javac]              ^


This constructor does not exist in the JDK 1.3.1.  Rather, I believe
this can be implemented as:
format = new MessageFormat(escape(formatString));
format.setLocale(locale);

Any objection?


    [javac] D:\Program
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\PipelineDocument.java:296:

cannot resolve symbol
    [javac] symbol  : method toString  (boolean)
    [javac] location: class java.lang.Boolean
    [javac]     String bool = Boolean.toString(binary);
    [javac]                          ^


This static method does not exist in JDK 1.3.1.  My workaround for it
is:
(Boolean.valueOf(binary)).toString();

Any objection?


    [javac] D:\Program
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\command\PipelineCommand.java:126:

cannot resolve symbol
    [javac] symbol  : method toString  (boolean)
    [javac] location: class java.lang.Boolean
    [javac]           System.out.print(I18n.get("008004",
Boolean.toString(tracked)));
    [javac]                                                      ^


See above


    [javac] D:\Program
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXmlDecoderPipelineStage.java:74:

cannot resolve symbol
    [javac] symbol  : class XMLDecoder
    [javac] location: class
com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
    [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
    [javac]     ^


See above


    [javac] D:\Program
Files\babeldoc\src\modules\core\src\com\babeldoc\core\pipeline\stage\JavaXmlDecoderPipelineStage.java:74:

cannot resolve symbol
    [javac] symbol  : class XMLDecoder
    [javac] location: class
com.babeldoc.core.pipeline.stage.JavaXmlDecoderPipelineStage
    [javac]     XMLDecoder d = new XMLDecoder(doc.getInputStream());
    [javac]                        ^


See above


    [javac] 7 errors

BUILD FAILED
file:D:/Program Files/babeldoc/src/./modules/core/build.xml:23: Compile
failed; see the compiler error output for details.

Total time: 14 seconds

[Babeldoc-devel] SqlEnrich stage

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

>Is "sqlScript" a SELECT statement in this case? What
goes in "attributeSql"? 

SqlEnrich can use sqlScript or attributeSql (or both).
When sqlScript is used, a first row that is returned
will contain data for attribute values. Attribute
names will be set using column names. So if you have:
sqlScript=SELECT ATTR1, ATTR2 FROM SOME_TABLE WHERE
ID=5
a document will get two attributes named ATTR1 and
ATTR2 and their values will be values returned from
query. Note that only first row will be used others
will be ignored.

If you want every attribute have specific sql query
for setting attribute value you can use attributeSql
options:
attributeSql.attr1= SELECT DATA FROM SOME_TABLE WHERE
ID=10
attributeSql.attr2=SELECT .....
You can have as many attributeSql options (with
different attribute names) as you want. Note that only
first column of first row will be used for setting
attribute value.

>Is this Stage capable of reading a Long ?VarChar /
CLOB? 


I am not sure if it can handle CLOBS (I am pretty sure
it won't work on Oracle) but Varchar and Long should
work. I have worked with Oracle so I really don't know
how Sysbase will work.

>Can "resourceName" be pointed to a Weblogic Database
Connection Pool? 

resourceName is name of connection defined as Babeldoc
resource. I believe currently it won't work with
Weblogic db conn pool, but I think it is possible to
implement using JNDI data sources (Bruce, what you
think?)

>So, this is where I would use "transformationScript"?
What value do I give it, the value given in
"attributeSql" for the SqlEnrich Stage? 
Since transformationScript is used as 'inline' value
you should use Velocity script to get the value of
document attribute. So if you have set attribute
xslScript in previous step (SqlEnrich) you shoud have
something like:
transformationScript=${document.get('xslScript')}
This will be evaluated to value of attribute xslScript
which is value that you have slected using sql in
previous step

> Also, "transformationFile" becomes a 0..n, right?

Right!

Best Regards,
Dejan


__________________________________________________
Do you Yahoo!?
Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop!
http://platinum.yahoo.com

Re: [Babeldoc-devel] Database Tables

[<ek...@ba...>]

I'm sorry I seem so dense on this matter, but I need to understand how
to configure this.

I will have two stages to do an XMLTransformation.
1. SQLEnrich
2. XslTransform

I will need to do the SQLEnrich to get the Xsl logic, which will then be
fed into the XslTranform step, right?

SqlEnrich


Enrich documents with values based on sql queries


|------------+------------+------->
|    Name    |    Type    | number|
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  |                                                      description                                                     |
  >----------------------------------------------------------------------------------------------------------------------|
|------------+------------+------->
| sqlScript  | string     | 0..1  |
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  | Error getting the resource                                                                                           |
  >----------------------------------------------------------------------------------------------------------------------|
|------------+------------+------->
| ignored    | boolean    | 0..1  |
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  | Is this stage ignored                                                                                                |
  >----------------------------------------------------------------------------------------------------------------------|
|------------+------------+------->
| stageType  | service-nam| 1..n  |
|            | e          |       |
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  | Type of pipeline stage                                                                                               |
  >----------------------------------------------------------------------------------------------------------------------|
|------------+------------+------->
| tracked    | boolean    | 0..1  |
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  | Is this stage tracked                                                                                                |
  >----------------------------------------------------------------------------------------------------------------------|
|------------+------------+------->
| attributeSq| complex    | 0..1  |
| l          |            |       |
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  | List of scripts that can return multiple columns (but single row). An atttribute will get created for each column.   |
  | The name of the attribute will be the same as the column name and the value will be the column value                 |
  >----------------------------------------------------------------------------------------------------------------------|
|------------+------------+------->
| nextStage  | string     | 1..n  |
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  | Type of scanner                                                                                                      |
  >----------------------------------------------------------------------------------------------------------------------|
|------------+------------+------->
| resourceNam| string     | 0..1  |
| e          |            |       |
|------------+------------+------->
  >----------------------------------------------------------------------------------------------------------------------|
  | Name of the resource that contains Database Connection                                                               |
  >----------------------------------------------------------------------------------------------------------------------|



Is "sqlScript" a SELECT statement in this case?
What goes in "attributeSql"?
Is this Stage capable of reading a Long VarChar / CLOB?
Can "resourceName" be pointed to a Weblogic Database Connection Pool?

XslTransform


Transform the document using XSL


|------------------+--------------+-------+------------------------------------|
|       Name       |     Type     | number|             description            |
|------------------+--------------+-------+------------------------------------|
| ignored          | boolean      | 0..1  | Is this stage ignored              |
|------------------+--------------+-------+------------------------------------|
| stageType        | service-name | 1..n  | Type of pipeline stage             |
|------------------+--------------+-------+------------------------------------|
| bufferSize       | integer      | 0..1  | The buffer size to use             |
|------------------+--------------+-------+------------------------------------|
| tracked          | boolean      | 0..1  | Is this stage tracked              |
|------------------+--------------+-------+------------------------------------|
| transformationFil| directory-pat| 1..n  | The name of the XSL to convert the |
| e                | h            |       | document                           |
|------------------+--------------+-------+------------------------------------|
| nextStage        | string       | 1..n  | Type of scanner                    |
|------------------+--------------+-------+------------------------------------|



So, this is where I would use "transformationScript"?  What value do I
give it, the value given in "attributeSql" for the SqlEnrich Stage?
Also, "transformationFile" becomes a 0..n, right?

<<
I would prefer it not to change the sql configuration tables.  We can do
everything you need with the SqlEnrichPipelineStage selecting the XSL
data
from another table of your choice, placing that data in an attribute and
then
getting that data using the new configuration parameter.
>>

Re: [Babeldoc-devel] Database Tables

[bruce <br...@mc...>]

On Friday 28 March 2003 03:07 pm, ek...@ba... wrote:
> Bruce, please advise:
> 1. What is the name of the class you have updated so I can download it
> from CVS?

com.babeldoc.core.pipeline.stage.XslTransformPipelineStage

> 2. Are we still undecided on which table will store the CLOB / Long
> Varchar field (CONFIG vs. "Other")?

I would prefer it not to change the sql configuration tables.  We can do 
everything you need with the SqlEnrichPipelineStage selecting the XSL data 
from another table of your choice, placing that data in an attribute and then 
getting that data using the new configuration parameter.


> Erik
>
> <<
> OK,
>
> I have implemented this and commited it to the CVS repository.  This
> means
> that there is now a configuration parameter on the XslTransform pipeline
> stage that accepts a script "inline".  The parameter is called
> "transformationScript".
>
> There is one problem with this.  Since the XSL is not based on a URL
> (file or
> otherwise) it cannot load relative XML fragments.  This is probably not
> a big
> issue.
>
> regards,
> Bruce.
>
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

[<ek...@ba...>]

Bruce, please advise:
1. What is the name of the class you have updated so I can download it
from CVS?
2. Are we still undecided on which table will store the CLOB / Long
Varchar field (CONFIG vs. "Other")?

Erik

<<
OK,

I have implemented this and commited it to the CVS repository.  This
means
that there is now a configuration parameter on the XslTransform pipeline
stage that accepts a script "inline".  The parameter is called
"transformationScript".

There is one problem with this.  Since the XSL is not based on a URL
(file or
otherwise) it cannot load relative XML fragments.  This is probably not
a big
issue.

regards,
Bruce.
>>

Re: [Babeldoc-devel] Database Tables

[bruce <br...@mc...>]

OK,

I have implemented this and commited it to the CVS repository.  This means 
that there is now a configuration parameter on the XslTransform pipeline 
stage that accepts a script "inline".  The parameter is called 
"transformationScript".  

There is one problem with this.  Since the XSL is not based on a URL (file or 
otherwise) it cannot load relative XML fragments.  This is probably not a big 
issue.

regards,
Bruce.

On Friday 28 March 2003 01:36 pm, bruce wrote:
> On Friday 28 March 2003 12:59 pm, ek...@ba... wrote:
> > As another alternative, we *could* have an additional column in CONFIG
> > named cfg_script of type "text" / long varchar which is nullable.  We
> > could keep cfg_value as a varchar and add cfg_script which is nullable.
> > If cfg_script had a value, then this could be used in place of the
> > cfg_value in the internal hashmap.  That way, most entries would only
> > use cfg_value ... not elegant, but an idea.
>
> Yes, it will work but it wont solve the immediate problem that we have -
> that the XslTransform stage wants to load its data from a file or a url.  I
> have made a change to this so that the pipeline stage can accept the XSL
> script inline OR as a file.
>
> > ---------------------- Forwarded by Erik Klein/NY/DOMESTIC/BNY on
> > 03/28/2003 12:56 PM ---------------------------
> >
> >
> > Erik Klein
> > 03/28/2003 12:52 PM
> >
> > To:    "Babeldoc Developers List" <bab...@li...>
> > cc:
> > Subject:    Re: [Babeldoc-devel] Database Tables  (Document link: Erik
> >        Klein)
> >
> >
> > Let me attempt to understand what this implies.
> >
> > 1. Does this mean that in order for me to do an XSL transformation, I
> > will need 2 stages?  One for SQLEnrich to read the transformation script
> > from the database and another to perform the XslTransform?
> >
> > 2. Where would I store the XSL Transformation text in the database?  Not
> > in CONFIG, right?  Yet, it would have to be "aligned" with the specific
> > Pipeline Name and Pipeline Stage for which it is intended.  So, this
> > other table would still need to have the same "key", namely CFG_NAME.
> > In that case, database normalization rules tell me that they should be
> > in the same table, right?  Otherwise, I would have two tables with the
> > same key.
> >
> > Tends to lead me toward including it in CONFIG.  Our "problem" is based
> > on database implementations (varchar vs. text) ... which we should
> > really try to abstract ourselves from when writing our Java code.  I am
> > *very* confident that JDBC 2.0 supports BLOBs and CLOBs (text) just like
> > every other SQL data type in that you can issue getBlob(), setBlob()
> > just as you would setInt(), getInt() on a prepared statement (i.e. no
> > "stupid stuff" like the Oracle BLOB implementation ... which I am sure
> > is only JDBC 1.0 dependent).  In addition, depending on the database
> > implementation, even using getString(), setString() is possible as long
> > as the data length of the underlying driver is not exceeded (which can
> > be determined by using Statement.getMaxFieldSize()) ... I don't
> > recommend this, just thought you might find it interesting.
> >
> > Here's a link for more info:
> > http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame7.html#4
> >14 9
> >
> > Erik
> >
> > <<
> > Does this meet want you need?
> >
> > On Friday 28 March 2003 09:56 am, bruce wrote:
> > > On Friday 28 March 2003 09:49 am, Dejan Krsmanovic wrote:
> > > > You could store script as document atribute. There is pipeline stage
> > > > called sqlEnrich wich you can use to get data from database using
> >
> > any sql
> >
> > > > query and store the result as document attribute. That way you can
> >
> > use it
> >
> > > > as inline script in XslTransform witout changing original babeldoc
> >
> > db
> >
> > > > schema
> > >
> > > Yes - thats a great idea.  But even so, we will still have to make the
> > > change to the XslTransformPipelineStage to load the script inline.  I
> >
> > will
> >
> > > make this change.
> >
> > The information in this e-mail, and any attachment therein, is
> > confidential and for use by the addressee only. If you are not the
> > intended recipient, please return the e-mail to the sender and delete it
> > from your computer. Although The Bank of New York attempts to sweep
> > e-mail and attachments for viruses, it does not guarantee that either
> > are virus-free and accepts no liability for any damage sustained as a
> > result of viruses.
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:
> > The Definitive IT and Networking Event. Be There!
> > NetWorld+Interop Las Vegas 2003 -- Register today!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

[bruce <br...@mc...>]

On Friday 28 March 2003 12:59 pm, ek...@ba... wrote:
> As another alternative, we *could* have an additional column in CONFIG
> named cfg_script of type "text" / long varchar which is nullable.  We
> could keep cfg_value as a varchar and add cfg_script which is nullable.
> If cfg_script had a value, then this could be used in place of the
> cfg_value in the internal hashmap.  That way, most entries would only
> use cfg_value ... not elegant, but an idea.

Yes, it will work but it wont solve the immediate problem that we have - that 
the XslTransform stage wants to load its data from a file or a url.  I have 
made a change to this so that the pipeline stage can accept the XSL script 
inline OR as a file.


> ---------------------- Forwarded by Erik Klein/NY/DOMESTIC/BNY on
> 03/28/2003 12:56 PM ---------------------------
>
>
> Erik Klein
> 03/28/2003 12:52 PM
>
> To:    "Babeldoc Developers List" <bab...@li...>
> cc:
> Subject:    Re: [Babeldoc-devel] Database Tables  (Document link: Erik
>        Klein)
>
>
> Let me attempt to understand what this implies.
>
> 1. Does this mean that in order for me to do an XSL transformation, I
> will need 2 stages?  One for SQLEnrich to read the transformation script
> from the database and another to perform the XslTransform?
>
> 2. Where would I store the XSL Transformation text in the database?  Not
> in CONFIG, right?  Yet, it would have to be "aligned" with the specific
> Pipeline Name and Pipeline Stage for which it is intended.  So, this
> other table would still need to have the same "key", namely CFG_NAME.
> In that case, database normalization rules tell me that they should be
> in the same table, right?  Otherwise, I would have two tables with the
> same key.
>
> Tends to lead me toward including it in CONFIG.  Our "problem" is based
> on database implementations (varchar vs. text) ... which we should
> really try to abstract ourselves from when writing our Java code.  I am
> *very* confident that JDBC 2.0 supports BLOBs and CLOBs (text) just like
> every other SQL data type in that you can issue getBlob(), setBlob()
> just as you would setInt(), getInt() on a prepared statement (i.e. no
> "stupid stuff" like the Oracle BLOB implementation ... which I am sure
> is only JDBC 1.0 dependent).  In addition, depending on the database
> implementation, even using getString(), setString() is possible as long
> as the data length of the underlying driver is not exceeded (which can
> be determined by using Statement.getMaxFieldSize()) ... I don't
> recommend this, just thought you might find it interesting.
>
> Here's a link for more info:
> http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame7.html#414
>9
>
> Erik
>
> <<
> Does this meet want you need?
>
> On Friday 28 March 2003 09:56 am, bruce wrote:
> > On Friday 28 March 2003 09:49 am, Dejan Krsmanovic wrote:
> > > You could store script as document atribute. There is pipeline stage
> > > called sqlEnrich wich you can use to get data from database using
>
> any sql
>
> > > query and store the result as document attribute. That way you can
>
> use it
>
> > > as inline script in XslTransform witout changing original babeldoc
>
> db
>
> > > schema
> >
> > Yes - thats a great idea.  But even so, we will still have to make the
> > change to the XslTransformPipelineStage to load the script inline.  I
>
> will
>
> > make this change.
>
> The information in this e-mail, and any attachment therein, is
> confidential and for use by the addressee only. If you are not the
> intended recipient, please return the e-mail to the sender and delete it
> from your computer. Although The Bank of New York attempts to sweep
> e-mail and attachments for viruses, it does not guarantee that either
> are virus-free and accepts no liability for any damage sustained as a
> result of viruses.
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

[bruce <br...@mc...>]

Comments inline...

On Friday 28 March 2003 12:52 pm, ek...@ba... wrote:
> Let me attempt to understand what this implies.
>
> 1. Does this mean that in order for me to do an XSL transformation, I
> will need 2 stages?  One for SQLEnrich to read the transformation script
> from the database and another to perform the XslTransform?

Correct.  The scripts get stored in any table.

> 2. Where would I store the XSL Transformation text in the database?  Not
> in CONFIG, right?  Yet, it would have to be "aligned" with the specific
> Pipeline Name and Pipeline Stage for which it is intended.  So, this
> other table would still need to have the same "key", namely CFG_NAME.
> In that case, database normalization rules tell me that they should be
> in the same table, right?  Otherwise, I would have two tables with the
> same key.

Yes, it can be stored in any table but it does not need to be aligned with 
your pipeline except that you will need to provide the ID of the row - but 
that is done in the SQLEnrichPipeline stage as a configuration parameter.

> Tends to lead me toward including it in CONFIG.  Our "problem" is based
> on database implementations (varchar vs. text) ... which we should
> really try to abstract ourselves from when writing our Java code.  I am
> *very* confident that JDBC 2.0 supports BLOBs and CLOBs (text) just like
> every other SQL data type in that you can issue getBlob(), setBlob()
> just as you would setInt(), getInt() on a prepared statement (i.e. no
> "stupid stuff" like the Oracle BLOB implementation ... which I am sure
> is only JDBC 1.0 dependent).  In addition, depending on the database
> implementation, even using getString(), setString() is possible as long
> as the data length of the underlying driver is not exceeded (which can
> be determined by using Statement.getMaxFieldSize()) ... I don't
> recommend this, just thought you might find it interesting.

The problem here is not storing the script in the database - that is not the 
issue.  The issue is getting it from the database into the XslTransform 
pipelinestage.  The XslTransform pipeline stage *EXPLICITLY* wants to load 
the XSL file from either disk or from a URL datastream.  So I have added code 
to the XslTranform pipeline stage to accept the script "inline" from the 
configuration parameters to the pipeline stage.  This will allow you to place 
the XSL script "right-there" in the pipeline configuration along with the 
rest of the pipeline configuration.

Now, the issue now is that the configuration DB is not "wide-enough" to hold 
things like scripts.  That needs to be fixed:

1.  Make the SQL configuration service talk to blobs instead of varchars.  
This is a good solution and should fix future problems.
2.  Use Dejans solution and go with the SqlEnrich stage where the script is 
loaded from another table, attributed to the document.  The XslTransform 
pipeline stage then "inlines" that attribute (using a velocity macro).

The big difference is that option 2 does not require any further code changes.  
Ultimately the choice is yours.

> Here's a link for more info:
> http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame7.html#414
>9
>
> Erik
>
> <<
> Does this meet want you need?
>
> On Friday 28 March 2003 09:56 am, bruce wrote:
> > On Friday 28 March 2003 09:49 am, Dejan Krsmanovic wrote:
> > > You could store script as document atribute. There is pipeline stage
> > > called sqlEnrich wich you can use to get data from database using
>
> any sql
>
> > > query and store the result as document attribute. That way you can
>
> use it
>
> > > as inline script in XslTransform witout changing original babeldoc
>
> db
>
> > > schema
> >
> > Yes - thats a great idea.  But even so, we will still have to make the
> > change to the XslTransformPipelineStage to load the script inline.  I
>
> will
>
> > make this change.
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

[<ek...@ba...>]

As another alternative, we *could* have an additional column in CONFIG
named cfg_script of type "text" / long varchar which is nullable.  We
could keep cfg_value as a varchar and add cfg_script which is nullable.
If cfg_script had a value, then this could be used in place of the
cfg_value in the internal hashmap.  That way, most entries would only
use cfg_value ... not elegant, but an idea.

---------------------- Forwarded by Erik Klein/NY/DOMESTIC/BNY on
03/28/2003 12:56 PM ---------------------------


Erik Klein
03/28/2003 12:52 PM

To:    "Babeldoc Developers List" <bab...@li...>
cc:
Subject:    Re: [Babeldoc-devel] Database Tables  (Document link: Erik
       Klein)


Let me attempt to understand what this implies.

1. Does this mean that in order for me to do an XSL transformation, I
will need 2 stages?  One for SQLEnrich to read the transformation script
from the database and another to perform the XslTransform?

2. Where would I store the XSL Transformation text in the database?  Not
in CONFIG, right?  Yet, it would have to be "aligned" with the specific
Pipeline Name and Pipeline Stage for which it is intended.  So, this
other table would still need to have the same "key", namely CFG_NAME.
In that case, database normalization rules tell me that they should be
in the same table, right?  Otherwise, I would have two tables with the
same key.

Tends to lead me toward including it in CONFIG.  Our "problem" is based
on database implementations (varchar vs. text) ... which we should
really try to abstract ourselves from when writing our Java code.  I am
*very* confident that JDBC 2.0 supports BLOBs and CLOBs (text) just like
every other SQL data type in that you can issue getBlob(), setBlob()
just as you would setInt(), getInt() on a prepared statement (i.e. no
"stupid stuff" like the Oracle BLOB implementation ... which I am sure
is only JDBC 1.0 dependent).  In addition, depending on the database
implementation, even using getString(), setString() is possible as long
as the data length of the underlying driver is not exceeded (which can
be determined by using Statement.getMaxFieldSize()) ... I don't
recommend this, just thought you might find it interesting.

Here's a link for more info:
http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame7.html#4149

Erik

<<
Does this meet want you need?



On Friday 28 March 2003 09:56 am, bruce wrote:
> On Friday 28 March 2003 09:49 am, Dejan Krsmanovic wrote:
> > You could store script as document atribute. There is pipeline stage
> > called sqlEnrich wich you can use to get data from database using
any sql
> > query and store the result as document attribute. That way you can
use it
> > as inline script in XslTransform witout changing original babeldoc
db
> > schema
>
> Yes - thats a great idea.  But even so, we will still have to make the
> change to the XslTransformPipelineStage to load the script inline.  I
will
> make this change.
>>


The information in this e-mail, and any attachment therein, is
confidential and for use by the addressee only. If you are not the
intended recipient, please return the e-mail to the sender and delete it
from your computer. Although The Bank of New York attempts to sweep
e-mail and attachments for viruses, it does not guarantee that either
are virus-free and accepts no liability for any damage sustained as a
result of viruses.

Re: [Babeldoc-devel] Database Tables

[<ek...@ba...>]

Let me attempt to understand what this implies.

1. Does this mean that in order for me to do an XSL transformation, I
will need 2 stages?  One for SQLEnrich to read the transformation script
from the database and another to perform the XslTransform?

2. Where would I store the XSL Transformation text in the database?  Not
in CONFIG, right?  Yet, it would have to be "aligned" with the specific
Pipeline Name and Pipeline Stage for which it is intended.  So, this
other table would still need to have the same "key", namely CFG_NAME.
In that case, database normalization rules tell me that they should be
in the same table, right?  Otherwise, I would have two tables with the
same key.

Tends to lead me toward including it in CONFIG.  Our "problem" is based
on database implementations (varchar vs. text) ... which we should
really try to abstract ourselves from when writing our Java code.  I am
*very* confident that JDBC 2.0 supports BLOBs and CLOBs (text) just like
every other SQL data type in that you can issue getBlob(), setBlob()
just as you would setInt(), getInt() on a prepared statement (i.e. no
"stupid stuff" like the Oracle BLOB implementation ... which I am sure
is only JDBC 1.0 dependent).  In addition, depending on the database
implementation, even using getString(), setString() is possible as long
as the data length of the underlying driver is not exceeded (which can
be determined by using Statement.getMaxFieldSize()) ... I don't
recommend this, just thought you might find it interesting.

Here's a link for more info:
http://java.sun.com/j2se/1.3/docs/guide/jdbc/spec/jdbc-spec.frame7.html#4149

Erik

<<
Does this meet want you need?



On Friday 28 March 2003 09:56 am, bruce wrote:
> On Friday 28 March 2003 09:49 am, Dejan Krsmanovic wrote:
> > You could store script as document atribute. There is pipeline stage
> > called sqlEnrich wich you can use to get data from database using
any sql
> > query and store the result as document attribute. That way you can
use it
> > as inline script in XslTransform witout changing original babeldoc
db
> > schema
>
> Yes - thats a great idea.  But even so, we will still have to make the
> change to the XslTransformPipelineStage to load the script inline.  I
will
> make this change.
>>

Re: [Babeldoc-devel] Database Tables

[bruce <br...@mc...>]

Erik,

Does this meet want you need?



On Friday 28 March 2003 09:56 am, bruce wrote:
> On Friday 28 March 2003 09:49 am, Dejan Krsmanovic wrote:
> > You could store script as document atribute. There is pipeline stage
> > called sqlEnrich wich you can use to get data from database using any sql
> > query and store the result as document attribute. That way you can use it
> > as inline script in XslTransform witout changing original babeldoc db
> > schema
>
> Yes - thats a great idea.  But even so, we will still have to make the
> change to the XslTransformPipelineStage to load the script inline.  I will
> make this change.
>
> > Dejan
> >
> > ----- Original Message -----
> > From: <ek...@ba...>
> > To: "Babeldoc Developers List" <bab...@li...>
> > Sent: Friday, March 28, 2003 3:37 PM
> > Subject: Re: [Babeldoc-devel] Database Tables
> >
> > > <<
> > >
> > > > We add another configuration parameter to the XslTransform that
> > >
> > > provides
> > >
> > > > the
> > > > XSL document inline.  This will be in addition to the file
> > >
> > > configuration
> > >
> > > > parameter.  So the logic is:
> > > >
> > > > 1.  If the file/url parameter is not null, load from the url
> > > > 2.  if the inline parameter is not null, use the XSL in the parameter
> > > >
> > > >
> > > > I'm not sure of the method signature that would take this, but is it
> > > > possible to have an overloaded implementation that has one method
> > > > that takes a URL and another that takes a String?
> > >
> > > No, we have another configuration parameter for the XslTransform
> > > pipeline
> > > stage called, say transformationScript.  This contains the script
> > > inline
> > >
> > > > Also, how would this information be stored in the Properties Files /
> > > > CONFIG table?  An additional key/value pair or column?  Or are you
> > > > thinking of using the existing key / cfg_value field to store EITHER
> > >
> > > the
> > >
> > > > URL or the actual script?  If this is your choice, the db schema has
> > >
> > > to
> > >
> > > > change to support more than 255 chars.
> > >
> > > Bingo - we will have to increase the storage area.  The script will get
> > > stored
> > > in the cfg_value column.
> > >
> > >
> > > Sounds good to me.  However, I feel strongly that the database fields
> > > needs to be an unlimited length text field, which may require special
> > > JDBC processing like you have for BLOBs ... but I was under the
> > > assumption that JDBC 2.0 supported this directly without special
> > > coding.
> > >
> > > Also, is this type of functionality needed for other Pipeline Stages
> > > (other than XslTransform)?
> > >
> > > Erik
> > >
> > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by:
> > > The Definitive IT and Networking Event. Be There!
> > > NetWorld+Interop Las Vegas 2003 -- Register today!
> > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > > _______________________________________________
> > > Babeldoc-devel mailing list
> > > Bab...@li...
> > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:
> > The Definitive IT and Networking Event. Be There!
> > NetWorld+Interop Las Vegas 2003 -- Register today!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

[bruce <br...@mc...>]

On Friday 28 March 2003 09:49 am, Dejan Krsmanovic wrote:
> You could store script as document atribute. There is pipeline stage called
> sqlEnrich wich you can use to get data from database using any sql query
> and store the result as document attribute. That way you can use it as
> inline script in XslTransform witout changing original babeldoc db schema

Yes - thats a great idea.  But even so, we will still have to make the change 
to the XslTransformPipelineStage to load the script inline.  I will make this 
change.

> Dejan
>
> ----- Original Message -----
> From: <ek...@ba...>
> To: "Babeldoc Developers List" <bab...@li...>
> Sent: Friday, March 28, 2003 3:37 PM
> Subject: Re: [Babeldoc-devel] Database Tables
>
> > <<
> >
> > > We add another configuration parameter to the XslTransform that
> >
> > provides
> >
> > > the
> > > XSL document inline.  This will be in addition to the file
> >
> > configuration
> >
> > > parameter.  So the logic is:
> > >
> > > 1.  If the file/url parameter is not null, load from the url
> > > 2.  if the inline parameter is not null, use the XSL in the parameter
> > >
> > >
> > > I'm not sure of the method signature that would take this, but is it
> > > possible to have an overloaded implementation that has one method that
> > > takes a URL and another that takes a String?
> >
> > No, we have another configuration parameter for the XslTransform
> > pipeline
> > stage called, say transformationScript.  This contains the script inline
> >
> > > Also, how would this information be stored in the Properties Files /
> > > CONFIG table?  An additional key/value pair or column?  Or are you
> > > thinking of using the existing key / cfg_value field to store EITHER
> >
> > the
> >
> > > URL or the actual script?  If this is your choice, the db schema has
> >
> > to
> >
> > > change to support more than 255 chars.
> >
> > Bingo - we will have to increase the storage area.  The script will get
> > stored
> > in the cfg_value column.
> >
> >
> > Sounds good to me.  However, I feel strongly that the database fields
> > needs to be an unlimited length text field, which may require special
> > JDBC processing like you have for BLOBs ... but I was under the
> > assumption that JDBC 2.0 supported this directly without special coding.
> >
> > Also, is this type of functionality needed for other Pipeline Stages
> > (other than XslTransform)?
> >
> > Erik
> >
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:
> > The Definitive IT and Networking Event. Be There!
> > NetWorld+Interop Las Vegas 2003 -- Register today!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

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

I agree. VFS is still sandbox project and who know when jdbc file system
will be implemented (we could help them ;) )
So it should not be included for 1.0 release...
Dejan
----- Original Message -----
From: "bruce" <br...@mc...>
To: "Dejan Krsmanovic" <dej...@nb...>; "Babeldoc
Developers List" <bab...@li...>
Sent: Friday, March 28, 2003 3:08 PM
Subject: Re: [Babeldoc-devel] Database Tables


> Dejan
>
> Yes, I have been looking over commons-vfs - and it looks to be a great
> project.  My only issue is that I want to get 1.0 out and the change of
this
> fundamental portion of code is going to be (IMO) too many changes to
> fundamental code.
>
> regards,
> Bruce.
>
> On Friday 28 March 2003 02:33 am, Dejan Krsmanovic wrote:
> > Do you think it could be compatible with Commons VFS? I think it could
be
> > nice if we could use other VFS implementations...
> >
> > Dejan
> >
> > ----- Original Message -----
> > From: "bruce" <br...@mc...>
> > To: "Dejan Krsmanovic" <dej...@nb...>; "Babeldoc
> > Developers List" <bab...@li...>
> > Sent: Friday, March 28, 2003 3:11 AM
> > Subject: Re: [Babeldoc-devel] Database Tables
> >
> > > Erik,  Dejan:
> > >
> > > I think I have found a relatively simple solution:
> > >
> > > 1.  We implement a new URLStreamHandler so that we can have a new
> > > protocol (lets say, babelsql:) that can access the database just like
a
> > > filesystem. 2.  We implement the virtual filesystem using three
tables -
> > > a directory
> >
> > table
> >
> > > that knows about about its parent directory and maintains an id.  A
data
> > > table that knows about its directory table id and its own id and an
> >
> > "inode"
> >
> > > table that tracks common stuff for the two tables: permissions, last
> >
> > write,
> >
> > > access time, modification etc.
> > > 3.  Then we simply manage the data in the tables just like a regular
> > > filesystem and we access them in the same way.
> > >
> > > thoughts?
> > >
> > > regards,
> > > Bruce.
> > >
> > > On Wednesday 26 March 2003 12:29 pm, bruce wrote:
> > > > Dejan,
> > > >
> > > > This sounds just like what we need.   Let me look into it...
> > > >
> > > > regards,
> > > > Bruce.
> > > >
> > > > On Wednesday 26 March 2003 11:34 am, Dejan Krsmanovic wrote:
> > > > > Bruce, in future Babeldoc versions we should really think about
using
> > > > > Jakarta Commons VFS project. This component enables accessing data
> >
> > from
> >
> > > > > various sources. Currently local files, ftp files, WebDav, zip
files
> >
> > and
> >
> > > > > some others are supported. They plan to include JDBC "file system"
as
> > > > > well. When you have a time check that project out. I think it
could
> > > > > be valuable in future...
> > > > >
> > > > > Dejan
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "bruce" <br...@mc...>
> > > > > To: "Babeldoc Developers List"
<bab...@li...>
> > > > > Sent: Wednesday, March 26, 2003 3:18 PM
> > > > > Subject: Re: [Babeldoc-devel] Database Tables
> > > > >
> > > > > > On Wednesday 26 March 2003 08:23 am, ek...@ba... wrote:
> > > > > > > Well, I need both.  I need to store configuration information
in
> >
> > the
> >
> > > > > > > database and I would like to store XSLT scripts (and
everything
> >
> > else)
> >
> > > > > > > in the database also.
> > > > > >
> > > > > > The storing of the actual data in the database is the problem.
The
> > > > > > XslTransform pipeline stage expects to be given a filename or
URL
> > > > > > of
> >
> > a
> >
> > > > > data
> > > > >
> > > > > > source which will contain the XSL data.  Now, if that is not to
> > > > > > your
> > > > >
> > > > > liking,
> > > > >
> > > > > > then it will probably be necessary to implement either a general
> > > > > > solution
> > > > >
> > > > > to
> > > > >
> > > > > > this (probably using a URL scheme) or a specific
re-implementation
> >
> > of
> >
> > > > > > the pipeline stages to load from a database.
> > > > > >
> > > > > > > Good question though ... is the SQLConfig fully implemented /
> >
> > tested?
> >
> > > > > > It was working fine - about six months ago - you will have to do
a
> > > > > > little prototyping.  I certainly can help you with problems you
may
> > > > > > find.
> > > > > >
> > > > > > regards,
> > > > > > Bruce.
> > > > > >
> > > > > > > -------------------------------------------------------
> > > > > > > This SF.net email is sponsored by:
> > > > > > > The Definitive IT and Networking Event. Be There!
> > > > > > > NetWorld+Interop Las Vegas 2003 -- Register today!
> > > > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > > > > > > _______________________________________________
> > > > > > > Babeldoc-devel mailing list
> > > > > > > Bab...@li...
> > > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> > > > > >
> > > > > > -------------------------------------------------------
> > > > > > This SF.net email is sponsored by:
> > > > > > The Definitive IT and Networking Event. Be There!
> > > > > > NetWorld+Interop Las Vegas 2003 -- Register today!
> > > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > > > > > _______________________________________________
> > > > > > Babeldoc-devel mailing list
> > > > > > Bab...@li...
> > > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> > > > >
> > > > > -------------------------------------------------------
> > > > > This SF.net email is sponsored by:
> > > > > The Definitive IT and Networking Event. Be There!
> > > > > NetWorld+Interop Las Vegas 2003 -- Register today!
> > > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > > > > _______________________________________________
> > > > > Babeldoc-devel mailing list
> > > > > Bab...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> > > >
> > > > -------------------------------------------------------
> > > > This SF.net email is sponsored by:
> > > > The Definitive IT and Networking Event. Be There!
> > > > NetWorld+Interop Las Vegas 2003 -- Register today!
> > > > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > > > _______________________________________________
> > > > Babeldoc-devel mailing list
> > > > Bab...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by:
> > The Definitive IT and Networking Event. Be There!
> > NetWorld+Interop Las Vegas 2003 -- Register today!
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> > _______________________________________________
> > Babeldoc-devel mailing list
> > Bab...@li...
> > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

[bruce <br...@mc...>]

Comments inline

..snip..
On Friday 28 March 2003 09:37 am, ek...@ba... wrote:
> > change to support more than 255 chars.
>
> Bingo - we will have to increase the storage area.  The script will get
> stored
> in the cfg_value column.
>
>
> Sounds good to me.  However, I feel strongly that the database fields
> needs to be an unlimited length text field, which may require special
> JDBC processing like you have for BLOBs ... but I was under the
> assumption that JDBC 2.0 supported this directly without special coding.

Sounds good - lets hope that the bizarre oracle handling of blobs will not 
bite us on our collective asses - anyway,  we can deal with that later.   I 
will make the change to the XslTransformPipelineStage and the configuration 
stuff.

Do you want direct access to CVS repository - I think its probably a good idea 
at this time.

> Also, is this type of functionality needed for other Pipeline Stages
> (other than XslTransform)?
>
> Erik
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel

Re: [Babeldoc-devel] Database Tables

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

You could store script as document atribute. There is pipeline stage called
sqlEnrich wich you can use to get data from database using any sql query and
store the result as document attribute. That way you can use it as inline
script in XslTransform witout changing original babeldoc db schema

Dejan

----- Original Message -----
From: <ek...@ba...>
To: "Babeldoc Developers List" <bab...@li...>
Sent: Friday, March 28, 2003 3:37 PM
Subject: Re: [Babeldoc-devel] Database Tables


>
>
> <<
> > We add another configuration parameter to the XslTransform that
> provides
> > the
> > XSL document inline.  This will be in addition to the file
> configuration
> > parameter.  So the logic is:
> >
> > 1.  If the file/url parameter is not null, load from the url
> > 2.  if the inline parameter is not null, use the XSL in the parameter
> >
> >
> > I'm not sure of the method signature that would take this, but is it
> > possible to have an overloaded implementation that has one method that
> > takes a URL and another that takes a String?
>
> No, we have another configuration parameter for the XslTransform
> pipeline
> stage called, say transformationScript.  This contains the script inline
>
> > Also, how would this information be stored in the Properties Files /
> > CONFIG table?  An additional key/value pair or column?  Or are you
> > thinking of using the existing key / cfg_value field to store EITHER
> the
> > URL or the actual script?  If this is your choice, the db schema has
> to
> > change to support more than 255 chars.
>
> Bingo - we will have to increase the storage area.  The script will get
> stored
> in the cfg_value column.
> >>
>
> Sounds good to me.  However, I feel strongly that the database fields
> needs to be an unlimited length text field, which may require special
> JDBC processing like you have for BLOBs ... but I was under the
> assumption that JDBC 2.0 supported this directly without special coding.
>
> Also, is this type of functionality needed for other Pipeline Stages
> (other than XslTransform)?
>
> Erik
>
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by:
> The Definitive IT and Networking Event. Be There!
> NetWorld+Interop Las Vegas 2003 -- Register today!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en
> _______________________________________________
> Babeldoc-devel mailing list
> Bab...@li...
> https://lists.sourceforge.net/lists/listinfo/babeldoc-devel