Rony G. Flatscher wrote:
Jim wrote:
You should double check the file name & path. The JAR file is
"ScriptFramework.jar". And the path is relative to your JAR.
So if your JAR file is in a directory other than <OOo App>/.../classes
where ScriptFramework.jar is located, then I would suggest copying
ScriptFramework.jar into the one where you put your JAR.
Well, either locations, the same error pops up.
As DEV300 has changed the configuration and not being able to find
any related hints/infos, I hope that someone on this list may be able
to help to come by this situation.
That the classpath handling of com/sun/star/script/framework/* has
changed yet again makes me happy that I simply eliminated dependence
on it for GroovyForOpenOffice and as a result my extension works for
all OOo 2.* and 3.0. It seems a bit wasteful to duplicate those
classes, but it is clear that the OOo developers are treating them as
internal to OOo (which is what Juergen said last year when this came
up with 2.3).
Hmm. If interested in adding new scripting languages, then by all means
these classes cannot be regarded to be "internal use only". Also, there
is no flagging/warning not to use these classes. As a matter of fact,
without the ScriptMetaData class one would not be able to fetch the
script's code at all.
It isn't necessary to use any of com.sun.star.script.framework.* as
GroovyForOpenOffice demonstrates. They are simply helper classes in
Java which make it convenient to use the underlying UNO API which are in
com.sun.star.script.X* and com.sun.star.script.provider.X*.
My speculation is that due to configuration and class loader changes
there are a few corners where currently we hit bugs or holes. Sometimes,
if those in the know can think of a reason why currently it does not
work, then one was able to come by the problem one way or the other,
hoping that the GA version would take care of this. (However, should I
file an issue for problems like this or not?)
You can file an issue of course, but I'm pretty sure you will get the
response that this is not bug. OTOH, if you can get the handling of
ScriptFramework.jar changed back to the way it was so that extensions
can use it, then I'd be happy with that (I was contemplating switching
G4OO back to using c.s.s.s.framework until you reported that it won't
work in DEV300).
The OOo policy (as someone has said somewhere) is that the public
interfaces are strictly those which are also UNO. One might debate the
merits of that approach, but I doubt that will help with this situation.
Certainly, I have not seen any of this discussed in this list (nor at
api or dev), nor know of URLs where these points are documented for the
GA and for the beta versions.
When I get time I'll add some of what I've learned to the Developer
Guide on the wiki. But that probably won't be very soon.
Jim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
