|
From: Bill B. <bb...@re...> - 2008-08-25 13:51:22
|
You are right, i've added a jira task for this: https://jira.jboss.org/jira/browse/RESTEASY-111 Christian Sadilek wrote: > Hi, > > I just tried to call OPTIONS on a Resource and always get a "405 Method > not allowed". Should it work already using beta5? Also I could not find > @OPTIONS in javax.ws.rs as described in > http://wiki.jboss.org/wiki/UsingPathAndGETPOSTEtc. > > From the spec I get 3.3.5: > On receipt of an OPTIONS request an implementation MUST either: > 1. Call a method annotated with a request method designator for OPTIONS > or, if none present, > 2. Generate an automatic response using the metadata provided by the > JAX-RS annotations on the matching class and its methods. > > Is this still to be implemented or has there be any change in plan? I > think if no @OPTIONS is present RESTeasy should at least return the > Allow header. It might also make sense to annotate a resource method > with @OPTIONS to provide a custom response maybe a machine readable > description, but I am not sure about this. > > A while ago I also promised some more feedback on the client framework. > I can only say that I didn't have any problems and everything worked > fine for me. > I'm thinking of adding a client cache that can work with Cache-Control headers (like your browser). Bill -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |