[
https://issues.apache.org/jira/browse/ISIS-2502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17280539#comment-17280539
]
ASF subversion and git services commented on ISIS-2502:
-------------------------------------------------------
Commit 3a9bce30d4eb5a3366cc21267dbd70ffdadebc5a in isis's branch
refs/heads/ISIS-2502-ex.recog from Andi Huber
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=3a9bce3 ]
Merge pull request #367 from apache/ISIS-2502-ex.recog
Yet just an intermediate step.
TransactionService deals with the lower levels of exception translation now.
However, when transaction boundaries are not handled by the TransactionService,
but directly by Spring, translation will only kick in on beans annotated with
@Respository. In other words I could not find a mechanism such that any DB
interaction automatically yield translated Exceptions.
> Convert existing Exception Recognizers from JDO to Spring Data
> --------------------------------------------------------------
>
> Key: ISIS-2502
> URL: https://issues.apache.org/jira/browse/ISIS-2502
> Project: Isis
> Issue Type: Improvement
> Components: Isis Persistence JDO
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-M5
>
>
> {color:#1d1c1d}just testing helloworld on latest - slight regression; we seem
> to have lost some of our ExceptionRecognizers. If I create a helloworld
> object, and then another one with the same name, then the exception isnt'
> recognised and I get an error page{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
