FINERACT-1089: Fixing 'Operation not allowed for a result set of type"#1980
Conversation
… ResultSet.TYPE_FORWARD_ONLY'
|
@vorburger this should fix one of the error messages you were seeing in the logs of fineract.dev. Btw it might be that someone has changed the password for the mifos account again? If yes we should really block that.. |
Cool! Ah yes I really should fix that ASAP. Could you keep bugging me about it? 😃 Hopefully I can get to it over the next week or two. I did kind of forget that, and am currently having much fun elsewhere... (There is that certain other little Apache project a few people lately heard a few things about, where I feel strangely compelled to make it a better place; FYI apache/logging-log4j2@release-2.x...vorburger:release-2.x_split-API and some related activities - do give me a shout by DM if you have any interest in putting our heads together about that?) |
Description
Fix as proposed by Victor Jo in the JIRA ticket
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!
Write the commit message as per https://github.com/apache/fineract/#pull-requests
Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
Create/update unit or integration tests for verifying the changes made.
Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.
Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm with details of any API changes
Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the developer mailing list for guidance, if required.)
FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.