I'm just wondering, would it make sense to replace all those 6 or so parameters in writeTo/readFrom
with something similar to ApplicationConfig - this way there could be getBodyAnnotations(), would return null at the moment for
MessageBodyWriter and corresponding Method.getParameterAnnotations for MessageBodyReader, and it woudl also have
getMethodAnnotations(), etc...
Cheers, Sergey
>
>
> Marc Hadley wrote:
>> On Jun 30, 2008, at 11:31 AM, Stephan Koops wrote:
>>>>> I think ever the ones of the resource method -> @AnnotationA. Perhaps it is not clear enough.
>>>> Annotations from the type returned, not the method returning the type.
>>> Why should the runtime inject the annotations of the class? The class is available, so the runtime is not required to inject
>>> them. If this is meant, we could IMO remove the Annotation[] parameter.
>>>
>> We could remove that parameter. I guess its mainly there for symmetry with MessageBodyReader - is this a big deal ?
>>
>
> ...and when annotations on return types may be supported by the JRE, so we avoid having to change the interface later on.
>
> IIRC those were the two reasons why that parameter is present and my understanding was that currently it should always be null.
>
> Paul.
>
> --
> | ? + ? = To question
> ----------------\
> Paul Sandoz
> x38109
> +33-4-76188109
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jsr311.dev.java.net
> For additional commands, e-mail: users-help_at_jsr311.dev.java.net
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland