Message:
The following issue has been closed.
Resolver: Howard M. Lewis Ship
Date: Thu, 19 Aug 2004 6:28 AM
Run the full compile/test cycle with both JDK 1.4 and JDK 1.3.
---------------------------------------------------------------------
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: FIXED
Project: HiveMind
Components:
framework
Versions:
1.0
Assignee: Howard M. Lewis Ship
Reporter: Christian Domsch
Created: Tue, 6 Jul 2004 7:18 AM
Updated: Thu, 19 Aug 2004 6:28 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]
