Message:

   The following issue has been resolved as WON'T FIX.

   Resolver: Howard M. Lewis Ship
       Date: Sat, 17 Jul 2004 2:40 PM

Can't proceed with this, as it introduces a dependency on JDK 1.4 that is 
unacceptable to most HiveMind and Tapestry users.

Tapestry includes a utility class, ExceptionAnalyzer, that is very smart at 
pulling apart a stack of exceptions and presenting information about them.  The 
class has no dependencies on Tapestry or HTML, so it could be reused in another 
web framework, or even to format output to the console.
---------------------------------------------------------------------
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: Resolved
   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: Sat, 17 Jul 2004 2:40 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