I'm pretty sure you can get Spring to work within an OOo extension.
It's possible all you need to do is set the context classloader. I
don't have time to do that myself at the moment, but I'm interested in
hearing about your progress as I might have use for Spring myself.
These notes might help:
http://forum.springframework.org/showthread.php?t=18870
http://extensions.openoffice.org/servlets/ReadMsg?list=dev&msgNo=913
http://www.javaworld.com/javaworld/javaqa/2003-06/01-qa-0606-load.html
I can understand the reasons why the classpath was cleansed, but I am
not sure if this is the best way for OO's future.
And I think this is a point that should be mentioned in the developers
guide!
Indeed. It was quite traumatic when 2.3 came out with effectively no
notice of this drastic breaking change and there was no help available
explaining what had happened and how to fix things, just oblique BS
about "badly written extensions".
Also, there is a group of applications and use cases which become
impossible: all classes with are reachable to *any* Java application on
a system that are listed on the process' default environment variable
CLASSPATH. At the moment is seems to be the case that OOo face-2-face to
Java-OOo-extensions hides the CLASSPATH settings from them! [The
behaviour would be comparable to removing the settings of the PATH
environment variable from apps that are deployed via OOo or its
extensions, sort of blinding and deafing them.]
All use-cases where Java classes embedded in OOo-Java-extensions
therefore are not able access classes pointed to by CLASSPATH [or with
other words: globally available Java classes are hidden from
OOo-Java-extensions or Java programs deployed by them]. In the context
of scripts which employ the OOo Java-based scripting framework this
means that many use cases are simply not possible from OOo, e.g.
accessing and using ImageMagick via Java (having the Java-interfaces on
CLASSPATH) or any other library possessing a Java-interface or e.g.
"tools.jar" in JDK-environments (in this use case it would be impossible
to bundle the jar with one's Java extensions if one needs/wants to use
the version that matches the latest Java JDK on a system) and the like.
There is an issue (# 81973) about this from last September, cf.
<http://www.openoffice.org/issues/show_bug.cgi?id=81973>.
Certainly, I would like very much that this can be rectified as soon as
it may be possible (its implication to versatility and power of
OOo-Java-extensions seems to be rather high and long-reaching).
HTH,
---rony
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
