The following comment has been added to this issue:

     Author: Christian Domsch
    Created: Sun, 15 Aug 2004 11:35 PM
       Body:
I think I am getting misunderstood here. This is not about getting the cause 
when I *catch* a ApplicationRuntimeException. It's all about, when I *don't* 
catch them (which should be the major part of the time, because catching 
RuntimeException is bad style). Another time, when this is important, when I 
catch exceptions, and somewhere in the cause-chain is a ARE hidden. All I see 
then, is the ARE as a final cause, and not what's the real problem. And I don't 
think, that manually parsing the exception-chain is a good answer to this 
problem.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/HIVEMIND-16?page=comments#action_37266

---------------------------------------------------------------------
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: Sun, 15 Aug 2004 11:35 PM
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]

Reply via email to