Hi Peter,
thank you very much for coming back to this!
I do not have the SDK installed. Unfortunately, the exact details have escaped me since (having done
too many other things in between).
Background: many, many years ago I have authored a bridge for the scripting language ooRexx taking
advantage of the AOO scripting framework which is Java based. Basically I copied the BeanShell
engine (editor and dispatching the scripts) and adjusted it for ooRexx (is C++ but there is a Java
bridge). The packaging was done copying some other samples, but could get it done only after
receiving help from some developers back then who knew about the uno packaging process and what the
xml configuration files need to contain. (Also, I reverse-engineered the file layout for scripting
language scripts in order to place ooRexx samples there.)
So my problem in essence is lack of knowledge of how to properly debug Java code in this context
when the Java exceptions are not carried over and displayed. Also, I have no real working knowledge
of how one could/should go about configuring uno packages.
It would be of great help if there was (and maybe there is, yet, not found so far) a minimal, but
working ("nutshell") Java example that would demonstrate and briefly explain how to create an uno
package in Java, being able to deploy it (maybe with a method/function that returns "hello, world
from a Java uno extension") and explaining the minimal configuration definitions.
If you would be aware of such examples I would be grateful for any links.
Again, thank you very much for taking time for this!
---rony
On 6/4/2022 7:40 AM, Peter Kovacs wrote:
I going through old emails and no one seems to answer you.
Can you describe your setup? OS, have you sdk installed?
All the best
Peter
Am 03.10.21 um 15:12 schrieb Rony G. Flatscher:
Searched on the Internet but found no pointers so asking here.
Problem: something goes wrong while registering a Java based extension (an oxt
), but no information
is supplied.
Question: how to get debug (logging) information from a Java based extension?
Maybe with a Java
stacktrace?
---rony
P.S.: Could find the cause in the oxt, but this was really quite time consuming
(and therefore
effortful). Some new Java code caused a Runtime exception such that the
registering of the oxt could
not conclude; it would have helped a lot, if the Runtime exception was supplied
rather an empty
message was given (using unopkg from the commandline).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
