Hi Stephan, > > "Application classes can declare the supported request and response > media types using the @Consumes and @Produces annotations respectively. > [...] In the absence of either of these annotations, support for any > media type (“*/*”) is assumed." > > For details see > http://download.oracle.com/otn-pub/jcp/jaxrs-1.1-mrel-eval-oth-JSpec/jax_rs-1_1-mrel-spec.pdf, > > Chapter 3.5, page 15. > > By itself, ConverterProvider is OK. But it must not be wrapped with > > AbstractProviderWrapper. > Why not?
Thanks for the link. Then we have a problem. The ConverterProvider delegates to the ConverterService, which in turn delegates to the available ConverterHelper objects, which are resolved at run-time. Hence, the set of the MIME types supported by the ConverterProvider cannot be declared using an annotation, simply because it is unknown at the compilation time. I think that there is no choice, but process the ConverterProvider in a special way. The JAX-RS spec probably relates to the ideal world, where there is no need to integrate with the legacy systems. In our case, ConverterProvider is a bridge between JAX-RS and Restlet, which makes it so special. ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2890727
