I'm surprised this doesn't work, as I coded for it, and I thought we had
a unit test for it.
So, its the form parameter that doesn't show up, correct? Query
parameters in Resteasy come directly from parsing the request URI.
On 1/23/2013 4:49 AM, Weinan Li wrote:
> Thanks Denica! I've assigned
Thanks Denica! I've assigned this issue to me and will work on it.
--
Weinan Li
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Wednesday, January 23, 2013 at 5:20 PM, Denica Gencheva wrote:
> >
> > Could you please explain why you need to send "action" parameter both in
> > reque
>
>
> Could you please explain why you need to send "action" parameter both in
> request param and in form param?
>
I don't need to, but when I expose a web service people hit it like this
and in the HTTP RFC this is no forbidden. However we opened task about
this: https://issues.jboss.org/browse/
--
Weinan Li
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, January 22, 2013 at 9:46 PM, Denica Gencheva wrote:
> Hi, I'm facing the following problem: @Path("/my_path")
> @Produces(MediaType.TEXT_HTML) public interface MyService { @GET Response
> readAction(@QueryParam(
Hi,
I'm facing the following problem:
@Path("/my_path")
@Produces(MediaType.TEXT_HTML)
public interface MyService {
@GET
Response readAction(@QueryParam("action") String action);
@POST
Response postReadAction(@FormParam("action") String action)
}
$ curl -d "action=test
