Hi Andreas
Andreas Saeger escribió:
Mmmh, personally I have no problem to point the office to the jar. I
think an extension is overkill, particularly if the functions provide
nothing OOo-specific.
I think that the idea under the extension concept is to *extend* OOo.
Extra functions for HSQLB are something at least extend OOoBase when is
used with embedded databases.
However, it would be interesting to embed the
library within a database, so queries simply work without installing
anything. Impossible? Security issues?
maybe when the ODB supports scripting libraries (Basic, python,
JavaSript, and Java of course). I usually store jars within Writer docs
to call them via the scripting framework. I'm not sure if OOo will load
a JAR file that isn't called by this framework at all, although it is
stored in the ODF file. The problem here is that the JAR must be in the
class path, so HSQLDB can invoke its method.
A possible solution is to store the JAR in the installation directory
program/classes: the Dev's Guide says that every JAR there is added to
the class path.
But you still have the problem of creating the aliases: unless you
modify the source code of HSQLD to include the functions you want, you
have to tell HSQLDB where to find your methods. The alias tells what
class and method to look, and if it is in the class path, it will find it.
The solution for this problem of creating aliases every time, is an XJob
(== an UNO component); a simpler solution, add some macros to the Tools
- Customize - Events, as I explained in other mail...
Bye and thanks,
Ariel.
--
Ariel Constenla-Haile
La Plata, Argentina
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.arielconstenlahaile.com.ar/ooo/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
