Java and OpenOffice.org
Java is required for complete OpenOffice.org functionality. Java is mainly required to use the new embedded Java technology based HSQLDB database engine, or to make use of accessibility and assistive technologies. If you do not require database tables or accessibility integration or some wizards, then you do not need to download and install Java. Base (the database component) for example completely relies on Java technologies to run, but other programs (like Writer, Calc, and Impress) only need Java for special functionality (see below).
If you already have Java installed there is no need to download the OpenOffice.org installer with Java.
If you choose not to download Java you can easily install Java afterwards to get the missing functionality to work.
The Java Runtime Environment (JRE) or complete Java Development Kit (JDK) can be downloaded from java.com.
Some aspects of Java in OpenOffice.org are platform-specific. See the Platform FAQs. For installing Java on Windows machines, one might appreciate: Download Instructions for Windows offline. Mac_OS_X_10.5 comes with Java pre-installed; there is nothing to download. However, OpenOffice 2.3 doesn't work with Java on Mac OS 10.5; you need OpenOffice 2.4. See the Mac_OS_X_10.5 FAQs.
- 1 OpenOffice.org Functionality depending on Java
- 2 Java detection in OpenOffice.org 2 and StarOffice 8
- 3 External links
OpenOffice.org Functionality depending on Java
For the policy for Java use in OpenOffice.org, please see
- Create Form Wizard
- Letter Wizard
- Fax Wizard
- Agenda Wizard
- HTML Wizard
- SaveAs -> AportisDoc (Palm)
- SaveAs -> DocBook
- SaveAs -> Pocket Word (*.psw)
- SaveAs -> Pocket Excel
Java detection in OpenOffice.org 2 and StarOffice 8
Which Java will be used?
StarOffice tries to detect the newest Java version installed. StarOffice only detects Sun Java versions, while OpenOffice.org also detects Java versions from other vendors.
When using versions from different vendors, the numbering system might be different so maybe not the newest version is used. You can change the Java version in StarOffice via tools/options/Java.
On GNOME, if AT tool support is enabled, StarOffice will use that latest version where the Java Access Bridge is enabled.
When is Java detection done?
On Windows, detection is done the first time Java is used. On Linux/Solaris, detection is done the first time a user starts StarOffice.
How do I see the System.out.println output of Java components in OpenOffice.org?
You'll find some suggestions here :
Does any one know the real answer?
How do I debug Java components in OpenOffice.org?
You must go to Tools.Options.OpenOffice.org.Java, and click 'Parameters' for your chosen JVM. This allows you to pass options into the JVM when it is initialised. At a minimum you will need something similar to:
Note that when you are running a JVM with 'suspend=y' and you attempt to register a Java component, it will hang waiting for you to connect a debugger. In this case, you need to close down Office, change the configuration back, register the component, then re-start office, add in the JVM parameters, then call the Java component again. To speed this process up a bit, you can edit the java settings file contained in your user config directory, which on windows will be something like:
C:\Documents and Settings\<windows username>\Application Data\OpenOffice.org2\user\config\java_settings_Windows_x86.xml
It contains an element called 'vmParameters'. When you have java debugging enabled it will look something like:
<vmParameters xsi:nil="false"> <param>-Xdebug</param> <param>-Xnoagent</param> <param>-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=8000</param> </vmParameters>
If you are not running with debug it will contain:
It is a little bit quicker to manually edit this file between restarts then to use the UI.
How can I reset the Java configuration?
The configuration is stored in
< staroffice-config > /user/config/javasettings_ < platform > .xml
Just delete this file if you want StarOffice to detect again. The Java configuration file cannot be modified manually. The data format is not specified and may change anytime without further notice. Don't try to modify that file to change the Java version. The < location > and < version > entries are only for 'documentation', the Java version is accessed via the < vendorData > , which is binary.