Hi, me again, the guy that wants client-side stack traces.
I have a BacktraceCarrier class derived from ServerException
that can be used to carry the RuntimeExceptions back to the
client and print out a good stack trace by overriding the
printStackTrace() methods.
But I don't see a good way to handle application and library
Exceptions that appear in throws clauses and catch blocks. The
proxy can't throw a ServerException, because it needs to throw
the same Application Exception that was thrown by the user
application on the server.
So I need to get the application Exception to print out a stack
trace. I can't pass the Throwable.backtrace Object between JVMs,
because it has pointers to native stuff. And even though I can
know what the stack trace is supposed to look like I can't
reconstruct a good Throwable.backtrace Object on the client side
without writing native code, which would produce more of a
maintenance headache than its worth I imagine.
So here is what I'm thinking. When <carry-stacktrace> is enabled
in jboss.xml, Go ahead and carry the stack trace as a String back
to the client, and log the stack trace somewhere (using log4j).
Is it ok to use log4j in the proxy classes on the client side, or
does that add to the jar files that need to be in the client's
CLASSPATH?
- rick
--
Richard Kilgore
[EMAIL PROTECTED]
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development