[api-dev] Runtime problems when using Introspection&Reflection via Java ...

[Rony G. Flatscher]

Hi there, since a few hours, "all of a sudden" it has not been possible anymore to successfully use [com.sun.star.lang.XMultiComponentFactory] (supplying a context) or [com.sun.star.lang.XMultiServiceFactory] to instantiate "com.sun.star.beans.Introspection" and/or "com.sun.star.reflection.CoreReflection". This worked and I was able to use XIntrospection and XIdlReflection to analyze UNO objects at runtime. Then, ever since I tried to "play" around with an empty array object (result of "XidlReflection.getFields()") errors occurred and "all of a sudden" I have not been able to instantiate the above two classes. Using a XMultiComponentFactory to create an instance yields the following error message: "method invocation failed: java.lang.reflect.InvocationTargetException target exception: com.sun.star.uno.Exception: Query for service factory for com.sun.star.loader.SharedLibrary failed." Using a XMultiServiceFactory to create an instance yields merely null. --- If you have *any* hints, ideas what can cause such a behavriour, or even more importantly, how once could solve that, I would highly appreciate it. Here is additional information: Operating system: WindowsXP, SP2, using OOo 1.1.4, English *and* OOo 1.9.m113. The test programs use native Java reflection to analyze and invoke Java UNO classes/objects. This part seems to (still) work flawlessly. Now, for making it even easier for ooRexx (http://www.ooRexx.org) users to use UNO, I would like to alleviate the need to explicitly request interface objects and have that part figure out by the ooRexx support. For that reason it is important to be able to use the UNO-reflection/introspection part via Java. This is what I did afterwards: De-installed OOo 1.9.m113, rebooted: program started to work again on 1.1.4, then I re-installed OOo 1.9.m113, rebooted, program neither works with 1.1.4 (setting up the classpath to use 1.1.4 jars) nor with 1.1.9 (setting up the classpath to use the 1.1.9 jars), then I de-installed OOo 1.9.m113, "repaired 1.1.4", rebooted, now the test program does not run on 1.1.4 either! The erroneous behaviour is in all circumstances as mentioned above. If it makes a difference: OOo uses the JRE version 1.4.1_02, whereas my test programs use Java 1.4.1_06 (have a setup which allows me to use arbitrarily any major Java version, i.e. 1.1, 1.2, 1.3, 1.4, 1.5). --- So, again, would someone have any ideas, clues which could help me out? TIA, ---rony