Tobias Krais wrote:
I read that OOo framework knows two modes: application mode and direct
mode. Direct mode is what I need, because it does not read existing
configuration. How can I start soffice or unopkg in direct mode?
The problem with OOo is that it is configured to use application mode.
That is, all java-related settings are made persistent and the options
dialog relies on the persistend data. To this end there is jvmfwkrc
which contains a path to the javasettings_xyz.xml.
However you could of course try the direct mode. But bear in mind that
the options dialog is not prepared to deal with it. You may run into
trouble here.
What must my jvmfwk3rc look like for direct mode? Is this OK:
-----%<-----
[Bootstrap]
UNO_JAVA_JFW_ENV_JREHOME=true
UNO_JAVA_JFW_ENV_CLASSPATH=true
UNO_JAVA_JFW_VENDOR_SETTINGS=javavendors.xml
-----%<-----
You've got this certainly from your build environment. The direct mode
was initially designed to support java in the build environment where
there are no user settings.
The jvmfwk3rc above may work if you adapt the path to the
javavendors.xml. Have also a look into the jvmfwk3rc in the program
directory of your office. It contains a variable:
UNO_JAVA_JFW_CLASSPATH_URLS
which contains jar files which are put on the class path. I am not sure
if this value is also used if using direct mode.
The header jvmfwk/framework.h contains also some helpful information.
There is also a variable UNO_JAVA_JFW_JREHOME which can be used to point
directly to a JRE. The paths have to be file URLs. You could for example
start soffice this way.
soffice -env:UNO_JAVA_JFW_JREHOME=file:///java/myJRE
I am not sure if this automatically overrides the value from the user
settings. But if you remove UNO_JAVA_JFW_USER_DATA and perhaps
UNO_JAVA_JFW_SHARED_DATA then it may work.
And thus javavendors.xml must look like the javasettings_Linux_x86.xml.
Is this correct?
No, leave the javavedors.xml as it is. It contains information about the
supported JREs.
If I am correct, these steps will enable me to start OOo with my own
settings, thus also my own JRE. Right?
With a bit of luck, yes. A good idea is to build the jvmfwk3 project
with debug information. Then you will get a lot of console output which
you could use to narrow down problems.
Good luck
Joachim
Greetings, Tobias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
