Details
-
Type:
Feature Request
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 3.0.0.Beta1
-
Component/s: Core
-
Labels:None
-
Estimated Difficulty:Low
Description
PROCEED -> MARK_HANDLED
The directive PROCEED is too vague, and doesn't address the fact that the exception is being marked as handled. Better is to name the directive MARK_HANDLED. This is similar to JTA's setRollbackOnly(). It doesn't perform the action until the frame is complete, but it does mark the eventual action.
PROCEED_TO_CAUSE -> DROP_CAUSE
The directive PROCEED_TO_CAUSE is problematic on two accounts. First, it has the same problem as PROCEED in that it's too vague. Second, we aren't moving to the cause, we are moving from the cause to the wrapper. So what we are really doing is dropping the cause, hence DROP_CAUSE. Also, this should not mark the exception as handled.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy
