On Wed, 2006-05-10 at 08:56 -0500, Dan Lewis wrote:
> Comments in line:
> 
> On Wednesday May 10 2006 07:47 am, Andrew Douglas Pitonyak wrote:
> > Last I heard, if that JRE is not version 1.5.06, then the Base component
> > will have unexplained problems. When I say "heard", I mean that numerous
> > people have experienced mysterious perplexing crashes and failures that
> > went away after switching to version 1.5.06. The biggest problem is
> > trying to use 1.4.
> >
> > I personally experienced this both on Windows and Linux. You might want
> > to add a tip.
> 
>     I have gone a little farther than giving this information as a tip: I 
> placed the following Caution in the Getting Started with Base:
> ________________________________________________________________________
> The database in OOo requires Sun’s Java JRE. If you do not have it on your 
> computer, download it from www.java.com and install it following the 
> instructions on the site. It should be Java 5.0 or higher. In OOo, use 
> Tools > Options > OpenOffice.org > Java to register Java.
> ________________________________________________________________________
>      As mentioned below, Jean has altered the "Sun's Java JRE" to "Sun's 
> Java Runtime Environment (JRE)", but the rest remains intact. I feel it 
> needs to be a caution for Base and the wizards. (Base has to have it to 
> work.)  In other areas, a tip might be fine. Although I am not convinced 
> that a presentation can be created without JRE. (It uses a wizard to 
> create it.)
> 
> Dan
> >
> > Jean Hollis Weber wrote:
> > > Dan Lewis wrote:
> > >> On Wednesday May 10 2006 05:51 am, Perry Spiller wrote:
> > >>> Jean said:
> > >>>> In the "Getting Started with Base" chapter is this statement:
> > >>>> "The database in OOo requires Sun's Java JRE."
> > >>>
> > >>> I make the observation that "Sun's Java JRE" contains a redundancy.
> > >>> Should it not be Sun's JRE?
> > >>
> > >>      At first glance, it would seem so. However, when it comes to
> > >> Java there is the JRE and SKD. So the redundancy might well be
> > >> needed.
> > >
> > > I changed it to Sun's Java Runtime Environment (JRE), which is the
> > > term used in Chapter 1 "What is OOo?" and other places in the books.
> > >
> > > -- Jean

I based my writing on the requirements as noted on the OOo website:
http://www.openoffice.org/dev_docs/source/sys_reqs_20.html

Recently, I also read on the OOo forum that the JRE is required to use
some types of embedded media, such as mpegs. If someone has the time
maybe this question should be asked on either the OOo Users or Dev
mailing lists.

Maybe just saying JDK and JRE without mentioning Sun is a good idea, I'm
not sure if they work with OOo, but there are other JREs, like
Blackdown:
http://www.blackdown.org/

************from the OOo website****************
Java

The minimum JDK/JRE version required to use OpenOffice.org features that
require java is JDK/JRE version 1.3.1. 

To use the XSLT filters with JDK 1.3.1 you should download the files
xalan.jar and xml-apis.jar from Xalan website and crimson.jar from
Crimson website. The files also need to be added to the OpenOffice.org
classpath, this can be accomplished with
Tools->options->OpenOffice.org->Security 

For full functionality, jdk/jre 1.4.0_02 or newer or jdk/jre 1.4.1_01 or
newer is required

*************************************************

-- 
Regards,

Rick Barnes
www.nostabo.net

View my OOo tutorials and other references at:
http://www.nostabo.net/openoffice.php

*******************************************************************
PRIVILEGED - PRIVATE AND CONFIDENTIAL
This electronic mail is solely for the use of the addressee and may
contain information which is confidential or privileged. If you receive
this electronic mail in error, please delete it from your system
immediately and notify the sender by electronic mail or using any of the
contact details noted herein.

This e-mail sent via Evolution 2.6.1 running on a Linux 2.6.16 64 bit kernel.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to