[jira] Commented: (WINK-239) Support for generics as return type

["Michael Elman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WINK-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792084#action_12792084 ] 

Michael Elman commented on WINK-239:
------------------------------------

One question regarding the packaging: what was the reason for creating a separate module under wink-providers for this functionality?
I briefly looked at the code and didn't see any additional dependencies...
I think that we decided to create new modules only for providers that need dependencies that were not already included in wink-server/wink-common.
I mean: if wink-common contains enough dependencies for the provider - put it there.
Otherwise if wink-server contains enough dependencies - put it there.
Otherwise put it in a separate module.

May be I'm missing something though...

> Support for generics as return type
> -----------------------------------
>
>                 Key: WINK-239
>                 URL: https://issues.apache.org/jira/browse/WINK-239
>             Project: Wink
>          Issue Type: New Feature
>          Components: Providers
>            Reporter: Juergen Zimmermann
>            Assignee: Jesse Ramos
>             Fix For: 1.0
>
>
> It would be good if Wink supports generics as a return type of resource methods (as does Jersey and RESTEasy), e.g.
> @GET
> @Path("/customers")
> @Produces({APPLICATION_XML, TEXT_XML, APPLICATION_JSON})
> public List<Customer> findCustomers(...)
> The Jersey solution: Use classname + "s", e.g. <Customers>
> The RESTEasy solution: Use classname + "Collection", e.g. "CustomerCollection"
> Actually I'd prefer the RESTEasy naming. The Jersey naming is also fine - it's more important that Wink supports generics at all.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.