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

Detect unregistered namespace prefixes and provide useful error messages... #459

Closed
wants to merge 3 commits into from

Conversation

whikloj
Copy link
Collaborator

@whikloj whikloj commented Sep 10, 2014

... in the UI.

if (e instanceof QueryParseException) {
return new QueryParseExceptionMapper().toResponse((QueryParseException) e);
}

if ( e.getCause() instanceof RepositoryException) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This isn't a comment on @whikloj 's work as much as a general comment: this class stinks. When I wrote it, it was really simple and just caught exceptions for which no other more appropriate mapper existed. Now it's full of brittle type testing. I'll open an issue.

- Removed from WildcardExceptionMapper
- Added Provider annotation to QueryParseExceptionMapper

Resolves: https://www.pivotaltracker.com/story/show/61500542
@awoods
Copy link

awoods commented Sep 10, 2014

Resolved with: be7d793

@awoods awoods closed this Sep 10, 2014
@whikloj whikloj deleted the topic-61500542 branch September 12, 2014 03:08
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