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

Change generic exceptions to more specific exceptions #714

Merged
merged 1 commit into from Feb 16, 2015

Conversation

// TODO determine problems that should be runtime errors
}
} catch (Exception e) {
throw new RepositoryRuntimeException(e);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I may be being really too picky here, but to my understanding, this is not a RepositoryRuntimeException precisely because the repository is not running. We could put in a new RepositoryFailedStartup kind of thing, or maybe MODE already has such thing, or maybe I'm just being too picky...

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sounds very reasonable. But since @osmandin does not appear to agree, let's move this through for now.

@ajs6f
Copy link
Contributor

ajs6f commented Feb 12, 2015

This is good stuff and I'm all in favor, but I do want to record here (for my own failing memory) that we probably ought to be subclassing RepositoryRuntimeException and using the subclasses a little more. Which in no way is any vote against this PR.

awoods pushed a commit that referenced this pull request Feb 16, 2015
Change generic exceptions to more specific exceptions
@awoods awoods merged commit 0b3dd39 into fcrepo:master Feb 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants