Hi
On 14/10/11 17:20, Marek Potociar wrote:
> Hello experts,
>
> we've privately received some suggestions to make Req/Resp + builders generic.
>
> + The advantage would be the type safety as well as potential to preserve type information so that GenericEntity does
> not have to be utilized directly (e.g. HTTP resource methods that produce Response currently would be able to better
> declare the actual response entity type, provided the entity types produced share a common ancestor).
>
> - The main disadvantage I can think of is that generic req/response processing would (if correctly typed) require the
> extra "<?>" in many scenarios.
>
What advantage can that give to the client code, would that interfere
with the use of TypeLiteral in Response.getEntity ? Personally I can
live with the use of GenericEntity on the server side because IMHO the
use of explicit collections is not in 'mainstream', it seems most users
are happy with dealing with plain beans - those can be better validated,
extended and described
Cheers, Sergey
> Thoughts?
>
> Marek