[
https://issues.apache.org/jira/browse/ISIS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-351.
------------------------------
Resolution: Fixed
> Provide the ability for certain runtime exceptions to be recognized as
> non-fatal, for rendering to the user.
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-351
> URL: https://issues.apache.org/jira/browse/ISIS-351
> Project: Isis
> Issue Type: New Feature
> Components: Core, Viewer: Wicket
> Affects Versions: viewer-wicket-1.1.0, core-1.1.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: viewer-wicket-1.2.0, core-1.2.0
>
>
> For example, if a low-level exception thrown as a result of a unique index
> constraint is thrown, then this isn't really a problem, so should be rendered
> appropriately for the user.
> The JDO object store throws a stack trace whose causal chain contains both:
> javax.jdo.JDODataStoreException
> Insert of object "dom.todo.ToDoItem@5a538af7" using statement "INSERT INTO
> TODOITEM
> (ATTACHMENT,COMPLETE,OWNEDBY,DESCRIPTION,CATEGORY,NOTES,DUEBY,VERSION) VALUES
> (?,?,?,?,?,?,?,?)" failed : integrity constraint violation: unique constraint
> or index violation; TODOITEM_U1 table: TODOITEM
> and even more low level below it:
> java.sql.SQLIntegrityConstraintViolationException
> integrity constraint violation: unique constraint or index violation;
> TODOITEM_U1 table: TODOITEM
> It ought to be possible to render to the user as "Sorry, a ToDoItem already
> exists" or something similar.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
