|
From: <ek...@ba...> - 2003-03-25 16:54:57
|
If these are the only restrictions on using JVM 1.3.1, then I would happily download the change to the Call Stack Inspection routine to make it compatible with JVM 1.3.1 and then await its inclusion in the next release. I would not, however, want to diverge from the standard codebase. Also, are you aware of a modification to the Throwable.printStackTrace( ) format from JVM 1.3 to JVM 1.4? If so, this will impact another project that I have worked on. Please advise. Thanks. Erik bruce <br...@mc...>@lists.sourceforge.net on 03/25/2003 11:47:04 AM Sent by: bab...@li... To: bab...@li... cc: Subject: Re: [Babeldoc-devel] Minimum Java VM Version On Tuesday 25 March 2003 11:42 am, you wrote: > I assume you wanted me to email you directly on this since you did not > post the reply to the listserv? Let me know how you'd like me to > proceed in the future on this. A mistake on my part - sorry. > I am very confident that JVM 1.4 is not possible in our environment. > > I was under the assumption that the security classes implemented in JVM > 1.4 were simply embedded from JCE 1.2.1, which used to be a standalone > Jar. I used JCE 1.2.1 last year in a JVM 1.3.1 implementation without > problems. Additionally, I looked at your import statements for your > classes in com.babeldoc.crypto.pipeline.stage and found that all the > classes exist in JCE 1.2.1. I do not currently expect to need to use > cryptography, but if I do I suppose I could implement jce_1_2_1.jar into > the LIB directory and add it to the Classpath, right? Correct. > As far as Call Stack inspection goes, are you indicating that the format > of the stack trace has changed since JVM 1.3? What impact would this > have? This is a feature that is of limited utility. I can make a small change - you will have to download from CVS to get this immediately or wait for a release. Bruce. > Erik > > > > > bruce <br...@mc...> on 03/25/2003 11:27:01 AM > > To: ek...@ba... > cc: > Subject: Re: [Babeldoc-devel] Minimum Java VM Version > > > Babeldoc does require at least a 1.4 jvm. This is for two reasons - the > crypto stuff and the call stack inspection. Now, if neither of these is > particularly crucial to you, lets talk about how to work around these > two > areas. > > On Tuesday 25 March 2003 11:21 am, ek...@ba... wrote: > > What is the minimum acceptable JVM version that Babeldoc requires to > > operate properly? We are thinking of using it within a Weblogic > > Server > > > v6.1 sp3 environment which uses Sun's Java 1.3.1_03 > > > > Here's the version info from the jvm > > > > C:\bea\wlserver6.1sp3\jdk131\bin>.\java -version > > java version "1.3.1_03" > > Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1_03-b03) > > Java HotSpot(TM) Client VM (build 1.3.1_03-b03, mixed mode) > > > > Is this acceptable? > > > > Erik > > The information in this e-mail, and any attachment therein, is > > confidential and for use by the addressee only. If you are not the > > intended recipient, please return the e-mail to the sender and delete > > it > > > from your computer. Although The Bank of New York attempts to sweep > > e-mail and attachments for viruses, it does not guarantee that either > > are virus-free and accepts no liability for any damage sustained as a > > result of viruses. > > > > > > > > > > ------------------------------------------------------- > > 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 |