You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by co...@jakarta.apache.org on 2004/08/10 04:07:20 UTC
[jira] Updated: (JELLY-116) [PATCH] InvokeTag and InvokeStaticTag should export exception
The following issue has been updated:
Updater: Felipe Leme (mailto:jira@felipeal.net)
Date: Mon, 9 Aug 2004 7:06 PM
Comment:
Here is the patch and a snippet of the maven test:
[junit] Running org.apache.commons.jelly.core.TestInvokeStaticTag
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 3.896 sec
[junit] Running org.apache.commons.jelly.core.TestInvokeTag
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 3.146 sec
Note that I'm not sure if the tags.html has been updated correctly - I couldn't run maven site:generate
Changes:
Attachment changed to JELLY-116.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JELLY-116?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JELLY-116
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JELLY-116
Summary: [PATCH] InvokeTag and InvokeStaticTag should export exception
Type: New Feature
Status: Unassigned
Priority: Major
Project: jelly
Assignee:
Reporter: Felipe Leme
Created: Mon, 9 Aug 2004 6:55 PM
Updated: Mon, 9 Aug 2004 7:06 PM
Description:
If the method invoked throws a InvocationTargetException, invoke and invokeStatic should allow the caller to obtain the original exception.
So, I'm providing a patch (including test cases) that export that exception if the exceptionVar paramater is set (and in this case, it does not throw a JellyTagException). If that parameter is not set, it assumes the old behaviour (i.e., throws a JellyTagException).
---------------------------------------------------------------------
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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org