Tobias Krais wrote:
Hi Matthias,
Check if everything works with OOo 2.2. If it does, you're being hit by
http://qa.openoffice.org/issues/show_bug.cgi?id=80100
(which won't be fixed. So you may have to brush up your knowledge of
classloaders (a somewhat obscure and tricky topic) to get your problem
fixed).
that's it! Thanks for the hint. I would like to add some notes to this
issue. Classpath is a common technique, used by many frameworks, e.g.
Spring. Due to this issue, it is not possible to use external frameworks
- and these might be extremely useful - without patching them (most
frameworks rely on classpath technology. Is this the design goal for
extensions? If I think of the future of OO: might this be a no-go
criteria for developers?
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".
Jim
http://www.ifcx.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
