[
https://jira.jboss.org/browse/SEAMCATCH-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Porter resolved SEAMCATCH-22.
-----------------------------------
Resolution: Done
> Name improvements for flow directives
> -------------------------------------
>
> Key: SEAMCATCH-22
> URL: https://jira.jboss.org/browse/SEAMCATCH-22
> Project: Seam Catch
> Issue Type: Feature Request
> Components: Core API
> Affects Versions: Alpha2
> Reporter: Dan Allen
> Assignee: Jason Porter
> Fix For: Alpha3
>
>
> 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.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
