Hi Raymond,
Exceptions are handled by formatters particular to an environment -
cf ExceptionFormatter and FormatterRegistry. Formatters are
responsible for an exception type or set of types and know how to
"print" all relevant exception information to a PrintWriter. For
example, there are formatters for core exceptions.
Formatters may or may not be used by particular Monitor
implementations. For example, we could have an Eclipse or IDEA
runtime that handles exceptions display in a more integrated fashion.
SCATestCase is already configured with a monitor factory
implementation that uses the core formatters.
Jim
On Jan 19, 2007, at 1:15 PM, Raymond Feng wrote:
Hi,
I just noticed that now "contextStack" and "identifier" are not
dumped in the stacktrace of TuscanyException and
TuscanyRuntimeException any more. What's the rationale behind this?
I now find very diffcult to trouble shoot exceptions like:
org.apache.tuscany.spi.loader.UnrecognizedElementException:
Unrecognized element
at
org.apache.tuscany.core.runtime.AbstractRuntime.deployApplication
(AbstractRuntime.java:284)
Please note the QName of the element is not in the stack trace.
Thanks,
Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
