Andrew Douglas Pitonyak wrote:
Thats what I do also, I have created a message system that I can call
from basic that will open a dialog that holds all debug information for
me, unfourtunally this does not cover everything..
what wil happen with all those uncaught RuntimeExceptions? like
NullpointerException? as you have not done any try catch for those (I
said uncaught above) , you will never see them, and what if there is an
exeption when calling createUnoService, ie the class could not be
created because it threw an exception? those you can't catch either,
since you don't have any try catch around this.
it is for those kind of uncaught exceptions that I would like to get a
hold of stdout/stderr and see what is going on...
Write it all out to a log file... Remove the logging code when you are
finished.
what if the problem is the instantiation of the class that does the
writing? for example, I get an exception creating the class, trying to
open the file to write to?
there is still quite valid reasons to be able to see what gets written
out to stdout/stderr from java, not everything can be solved by
"manually" logging stuff..
If I could have told java itself via some parameter that stdout/stderr
should be redirected to a file, that would also work, since I can add
parameters to how java will start inside openoffice. But from what I can
see, that is not possible either.
--
Christian Andersson
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
