Type: required
Title: Empty Java class path
Posted by: [EMAIL PROTECTED]
Affected: -
Effective from: SRC680 CWS sb36
*Summary*
--------
jvmfwk3rc:
cleaned up UNO_JAVA_JFW_CLASSPATH_URLS
unorc:
+ URE_INTERNAL_JAVA_CLASSPATH
com.sun.star.lib.unoloader.UnoClassLoader:
- UnoClassLoader(URL, ClassLoader)
- UnoClassLoader(URL, ClassLoader, URL[])
+ UnoClassLoader(URL, URL[], ClassLoader)
sj2/sjapplet.hxx:
- void Init(Window *, INetURLObject const &, SvCommandList const &)
+ void
Init(com::sun::star::uno::Reference<com::sun::star::uno::XComponentContext>
const &, Window *, INetURLObject const &, SvCommandList const &)
udkapi:
+ com.sun.star.uri.UriSchemeParser_vndDOTsunDOTstarDOTexpand
+ com.sun.star.uri.XVndSunStarExpandUrl
+ com.sun.star.uri.XVndSunStarExpandUrlReference
offapi:
com.sun.star.sdbc.XDriver: + JavaDriverClassPath
com.sun.star.sdbc.JDBCConnectionProperties:
+ [optional, property] string JavaDriverClassPath;
+ jvmaccess/classpath.hxx
*Description*
-------------
Until now, almost every jar from program/classes has been on the OOo
Java class path (jvmfwk3rc UNO_JAVA_JFW_CLASSPATH_URLS), which has
both performance and name clash implications. That has been changed
by completely emptying the class path, making sure that OOo explicitly
locates all the jars it calls, and that each jar finds any jars it
depends on:
- In general, a jar that depends on another jar has to make this
dependency explicit via its manifest Class-Path. An exception are
Java UNO components which should not list dependencies on the UNO
runtime jars (ridl.jar, jurt.jar, juh.jar) or the OOo UNO types
unoil.jar, but instead are guaranteed to be executed in an environment
where those jars are available. (However, each Java UNO components
should specify whether it supplies any UNO types via a manifest
UNO-Type-Path, see
<http://www.openoffice.org/servlets/ReadMsg?list=interface-announce&msgNo=740>).
- OOo code that uses JNI to call Java needs to explicitly set up an
appropriate class loader.
- The com.sun.star.sdbc framework has been extended with a
JavaDriverClassPath to explicitly locate the JavaDriverClass.
In a default build, the class path (jvmfwk3rc
UNO_JAVA_JFW_CLASSPATH_URLS) will now be emtpy. However, when
building with any system jars (SYSTEM_BSH, SYSTEM_HSQLDB, etc.) those
system jars are still put on the class path. I assume that is the
right thing to do, but have no experience with such builds.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
