Hi Stephan, That is the nice side of being late in Restlet 1.1 release cycle, we can catch up with JAX-RS API changes :-) Regarding the conneg feature, you are right to be conservative while the debate is still open.
Best regards, Jerome _____ De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : samedi 12 juillet 2008 00:15 À : [email protected] Objet : Restlet JAX-RS extension Hi, I've just updated the JAX-RS extension to API version 0.9. Here the most important API changes, that are incompatible to the JAX-RS 0.8 * renamed @ProducedMime to @Produces * renamed @ConsumedMime to @Consumes * renamed MessageBodyWorkers to Providers (provides also access to exception mapper and context resolver * the JAX-RS API uses java.util.Locale instead of String * UriInfo.getPlatonicRequestBuilder() and getPathExtension() removed; add getConnegExtension() All old JUnit tests passing, except the tests for UriInfo.getPlatonicRequestBuilder(), which will not run now. The content negotiation by file extension will perhaps get fully removed from the JAX-RS-API for design reasons. See: * https://jsr311.dev.java.net/servlets/ReadMsg?list=dev <https://jsr311.dev.java.net/servlets/ReadMsg?list=dev&msgNo=1458> &msgNo=1458 (by Roy Fielding) * https://jsr311.dev.java.net/servlets/ReadMsg?list=dev <https://jsr311.dev.java.net/servlets/ReadMsg?list=dev&msgNo=1459> &msgNo=1459 (by Marc Hadley, JAX-RS specifiation leader) Because of that I will not update this feature, until there is a decision about that. If you use the userAgentTunnel, the content negotiation by file extension is typically not needed. And Restlet supports the content negotiation by file extension for GET and HEAD, so it could be optionally available, if someone needs it. best regards Stephan
