You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2013/02/24 17:20:12 UTC

[jira] [Updated] (WINK-380) Support "structured syntax suffix"/"fragid"s in media type providers

     [ https://issues.apache.org/jira/browse/WINK-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J.W. Janssen updated WINK-380:
------------------------------

    Attachment: WINK380-initial.patch

Initial patch allowing SSS to be supported by the provider registry. It allows a REST-method producing a mimetype like "application/vnd.custom+json" to be handled by the "application/json" provider.

I'm not sure whether there are more places that should be adapted in order to support SSS.
                
> Support "structured syntax suffix"/"fragid"s in media type providers
> --------------------------------------------------------------------
>
>                 Key: WINK-380
>                 URL: https://issues.apache.org/jira/browse/WINK-380
>             Project: Wink
>          Issue Type: Improvement
>          Components: Common
>    Affects Versions: 1.3
>            Reporter: J.W. Janssen
>         Attachments: WINK380-initial.patch
>
>
> Mimetypes can contain a "structured syntax suffix" (SSS, specified in RFC6838 section 4.2.8). For example "application/vnd.custom+json", should be regarded as "application/json".
> Currently, providers are returned that are strictly compatible with a requested mimetype, meaning that for "application/vnd.custom+json" only a provider with that particular mimetype is to be returned. While that works, it should also be possible to let a provider registered for "application/json" to be returned. This would make it easier for "vendor specific mimetypes" based on JSON to use the generic JSON provider.
> I've worked out a patch for Wink already, but want to give it some additional testing. When this is done, I'll attach it to this issue...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira