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.

Sign up for GitHub

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

Jump to bottom

Non-JSON providers don't support custom MIME types with extensions #80

Closed
kleinsch opened this issue Apr 15, 2016 · 1 comment
Closed

Non-JSON providers don't support custom MIME types with extensions #80

kleinsch opened this issue Apr 15, 2016 · 1 comment
Milestone
2.7.4

Comments

@kleinsch
Copy link
Contributor

The JSON provider supports things like application/vnd.com.example.v1+json but none of the other providers do. Their hasMatchingMediaType method defines support for those extensions, but the @Consumes and @Produces annotations are not wildcard, so hasMatchingMediaType never runs.
@cowtowncoder
Copy link
Member

cowtowncoder commented Apr 15, 2016 •
edited
Loading

Actually, since the patch (#81) is just extending what JSON already this, it might be fine to include for 2.7.4.
Otherwise I'd be tempted to wait until 2.8. I'll have another look at the patch to make sure.

@cowtowncoder cowtowncoder added this to the 2.7.4 milestone Apr 16, 2016
cowtowncoder added a commit that referenced this issue Apr 16, 2016
@cowtowncoder
Update release notes for #80
569c119
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.7.4
Development

No branches or pull requests
2 participants
@cowtowncoder @kleinsch