[
https://issues.apache.org/jira/browse/FINERACT-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Petri Tuomola resolved FINERACT-1157.
-------------------------------------
Resolution: Fixed
I had to fix this as part of porting to Jersey 2. Interop error handling is now
aligned with the rest of Fineract.
> UnsupportedOperationException at InteropServiceImpl
> ---------------------------------------------------
>
> Key: FINERACT-1157
> URL: https://issues.apache.org/jira/browse/FINERACT-1157
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Michael Vorburger
> Assignee: Petri Tuomola
> Priority: Blocker
> Labels: beginner
> Fix For: 1.6.0
>
>
> See FINERACT-932 for general background, and fix this problem by making it
> return an appropriate HTTP 4xx client validation error instead of an internal
> server UnsupportedOperationException:
> {code} java.lang.UnsupportedOperationException: Account not found for
> identifier ACCOUNT_ID/000000013
> at
> org.apache.fineract.interoperation.service.InteropServiceImpl.getAccountByIdentifier
> (InteropServiceImpl.java:179)
> at
> org.apache.fineract.interoperation.service.InteropServiceImpl$$FastClassBySpringCGLIB$$275e2ef6.invoke
> (<generated>) {code}
> [~edcable] do you know who may be interested in fixing bugs in InterOp?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
