Jim White wrote:
Something I just learned that I do regard as a bug (or at least critically needed enhancement) is that although the OOo 2.3 classpath change did move the OOo implementation classes out of the extensions' classpath, all extensions are in the same classpath (same URLClassLoader actually). That is even worse that having OOo classes visible since it is totally unpredicatable and uncontrollable what extensions users might install. But as I say, that is probably unrelated to your issue.
That should not be the case. Only old extensions that include jars that miss a UNO-Type-Path (see <http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/WritingUNO/Possible_Structures_for_Java_Components#Additional_UNO_Types>) are (and have to be) loaded by the basic UNO class loader (which has to know about all classes that represent UNO types).
-Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
