Skip to content

Conversation

@hyeonisism
Copy link
Contributor

@hyeonisism hyeonisism commented Jan 13, 2020

To be as specific as possible in catching exceptions.
As far as I can see, there is no problem.

@pivotal-issuemaster
Copy link

@hyeonisism Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@pivotal-issuemaster
Copy link

@hyeonisism Thank you for signing the Contributor License Agreement!

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jan 13, 2020
@sbrannen sbrannen self-assigned this Jan 13, 2020
@sbrannen sbrannen added in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jan 13, 2020
@sbrannen
Copy link
Member

Thanks for the PR.

I have revised the exception handling slightly differently in 7987448.

@sbrannen sbrannen closed this Jan 13, 2020
@sbrannen sbrannen added this to the 5.2.3 milestone Jan 13, 2020
@hyeonisism hyeonisism deleted the Update-catch-exception branch February 9, 2020 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in: data Issues in data modules (jdbc, orm, oxm, tx) type: enhancement A general enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants