Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

True exception causes lost when there is no cause chain #555

Closed
tstordyallison opened this issue Jul 16, 2013 · 2 comments
Closed

True exception causes lost when there is no cause chain #555

tstordyallison opened this issue Jul 16, 2013 · 2 comments
Labels

Comments

@tstordyallison
Copy link

Bug is in ExceptionUtils.getRootCause(Throwable throwable) - when the given exception is the root cause (e.g. it has no further causes) the method returns null, instead of e.

Led to quite a lot of digging and the eventual check out and debug of the code to find out what was actually causing my script to fail (a custom FlywayException that told me that I was not replacing on my placeholders...)!

Cheers,

Tom

@axelfontaine
Copy link
Contributor

This was actually working as designed. I have however now changed the design, so that the API calls become simpler and don't need to deal with the null check anymore.

@tstordyallison
Copy link
Author

Thanks Axel.

On 17 Jul 2013, at 10:37, "Axel Fontaine" <notifications@github.commailto:notifications@github.com> wrote:

This was actually working as designed. I have however now changed the design, so that the API calls become simpler and don't need to deal with the null check anymore.


Reply to this email directly or view it on GitHubhttps://github.com//issues/555#issuecomment-21102013.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants