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

Sealing methods should throw Exception instead of catching it #12

Closed
stklcode opened this Issue Aug 18, 2017 · 1 comment

Comments

Projects
None yet
1 participant
@stklcode
Owner

stklcode commented Aug 18, 2017

Currently seal() returns just a boolean value, if the sealing succeeded. The method should be refactored to throw an Exception instead.

Same for unseal() and sealStatus() which return null instead of a SealResponse.

Both methods print stack traces, which will also be removed.

@stklcode

This comment has been minimized.

Owner

stklcode commented Aug 28, 2017

Merged into develop branch => done.

@stklcode stklcode closed this Aug 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment