You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2009/09/01 20:48:32 UTC

[jira] Updated: (WINK-160) Consider content-type additional params in the resouce matching process

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

Bryant Luk updated WINK-160:
----------------------------

    Attachment: WINK-160.patch

A possible patch.

I'm assuming that the following is what is intended:
application/xml - postEntity
application/xml;type=collection - postEntities
application/xml;unknownparam=value - postEntity
application/xml;type=somethingelse = postEntity
application/xml;type=collection;param2=value2 - postEntities

{code}
@Consumes("application/xml")
public Response postEntity(Entity e) {

}

@Consumes("application/xml;type=collection")
public Response postEntities(EntitiesCollection e) {

}
{code}

> 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.