[
https://issues.apache.org/jira/browse/WINK-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12750314#action_12750314
]
Shay Tsadok commented on WINK-160:
----------------------------------
Sounds to me like a good solution.
There are some edge cases, for example:
{code}
@Consumes("application/xml;param2=value2")
public Response postEntity(Entity e) {
}
@Consumes("application/xml;type=collection")
public Response postEntities(EntitiesCollection e) {
}
{code}
What happens if we send application/xml;type=collection;param2=value2?
IMO, we shouldn't define the behavior of those cases now, we can simple set
some limitations in which support the "simple cases".
> Consider content-type additional params in the resouce matching process
> -----------------------------------------------------------------------
>
> Key: WINK-160
> URL: https://issues.apache.org/jira/browse/WINK-160
> Project: Wink
> Issue Type: New Feature
> Components: Server
> Reporter: Shay Tsadok
> Attachments: WINK-160.patch
>
>
> Following our discussion in the mailing-list
> (http://n2.nabble.com/POSTing-collection-of-entities-td3560945.html#a3560945)
> We should be able to consider the content-type params in the resource
> matching process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
