[
https://issues.apache.org/jira/browse/SYNCOPE-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-304.
--------------------------------------------
Resolution: Won't Fix
Unfortunately such low-level exceptions are thrown by low-level libraries and
not catch anywhere, to let Spring declarative transaction mechanism work
properly.
It seems that the current solution (e.g. group such persistence-related
exceptions in the RestServiceExceptionMapper) is the best compromise.
> Mapping low level exceptions in core
> ------------------------------------
>
> Key: SYNCOPE-304
> URL: https://issues.apache.org/jira/browse/SYNCOPE-304
> Project: Syncope
> Issue Type: Improvement
> Components: core
> Reporter: Andrei Shakirin
> Fix For: 1.2.0
>
>
> Actually service layer processes three relative low level exceptions from
> persistence:
> org.apache.ibatis.exceptions.PersistenceException;
> org.springframework.orm.jpa.JpaSystemException;
> javax.persistence.PersistenceException
> Suggestion: abstract service implementation from persistence a little bit
> more and wrap these three exceptions in high level Syncope
> PersistenceException.
> From my perspective it helps for the cases when Syncope will support
> alternative persistence technologies like Hibernate JPA, EclipseLink JPA or
> even LDAP, JCR, non-SQL DBs.
> https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions
--
This message was sent by Atlassian JIRA
(v6.1#6144)
