Is there any value in allowing a method to respond to both GET and POST
requests?
Currently something like:
class Foo {
@GET
@POST
public String test() {...}
}
Only responds to @GET but does not respond to @POST.
I agree that conceptually, @GET and @POST should be completely different
methods. This is just something random that came up when working on our
application. One of the clients that we're using sends GET in some situations
and POST in other situations. As other libraries generally handle GETs and
POSTs interchangably, this wasn't an issue until we migrated this to CXF.
In any case, it was easy enough to work around this, and I'm not even if I
think it should be changed. Mostly just curious to hear the team's thoughts
and see if this issue has come up before.
Cheers,
Gary
--------------------------------------------------------------------------
NOTICE: If received in error, please destroy and notify sender. Sender does not
intend to waive confidentiality or privilege. Use of this email is prohibited
when received in error.
