The following comment has been added to this issue:
Author: Luke Blanshard
Created: Mon, 16 Aug 2004 4:25 AM
Body:
Well, I must still be misunderstanding you then. You said you wanted to be
able to follow the cause chain through AppRuntimeExceptions, and you asked
Howard to do this by calling the initCause method -- which doesn't exist until
1.4. He refused because he doesn't want to depend on 1.4.
My suggestion is to simply have the ARE class implement a method called
"getCause", which does exactly the same thing that the current "getRootCause"
method does. In 1.3 and earlier, this is just a new method. But in 1.4 and
later, it overrides the getCause method from Throwable. Thus, in 1.4, you can
follow the cause chain right through an ARE without having to know about it or
its special root cause method.
More importantly from my point of view, when you print the stack trace you can
find out what really happened.
So if I've misunderstood you, can you please explain more clearly how?
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/HIVEMIND-16?page=comments#action_37282
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/HIVEMIND-16
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HIVEMIND-16
Summary: ApplicationRuntimeException does not init cause
Type: Improvement
Status: Closed
Priority: Major
Resolution: WON'T FIX
Project: HiveMind
Components:
framework
Versions:
1.0
Assignee: Howard M. Lewis Ship
Reporter: Christian Domsch
Created: Tue, 6 Jul 2004 7:18 AM
Updated: Mon, 16 Aug 2004 4:25 AM
Environment: Windows XP, jdk5.0 beta1, Eclipse 3.0
Description:
When you have the situation, that while setting a property through hivemind an
exception is thrown inside the set-method, you only get simple message, saying
that the update of a property failed with a
java.lang.reflect.InvocationTargetException. This is not very informative,
since the real cause can be anything, ranging from ClassNotFound to anything
imaginable. Therefore I enhanced the
org.apache.hivemind.ApplicationRuntimeException so that it inits the cause of
the ARE to the one supplied with its constructor. Very simple change, just add
the corresponding super-constructor argument. I have a patch file, that holds
these changes.
Greetings,
Christian Domsch
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
