cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-4473) PathParam null when @Path annotations are the same
Date Wed, 15 Aug 2012 16:38:38 GMT


Sergey Beryozkin commented on CXF-4473:

@GET @Path("/users/{username}/foo")
public List<Foo> getFooOfUsers(@MatrixParam("username") List<String> usernames)

is technically a valid syntax, as you may have '/users/bob;username=mary;username=fred' and
the above should capture 'mary' & 'fred, with 'bob' captured but not explicitly requested
in the code;
But I can see where the confusion may be coming from. 

I guess I'm going to close it as Not A Problem ?
> PathParam null when @Path annotations are the same
> --------------------------------------------------
>                 Key: CXF-4473
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.5.4
>         Environment: java version "1.6.0_24"
> OpenJDK Runtime Environment (IcedTea6 1.11.3) (6b24-1.11.3-1ubuntu0.12.04.1)
> OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
>            Reporter: Chris Eineke
> For some reason, the JAX-RS runtime doesn't provide the value of a @GET-annotated method
and @PathParam-annotated method parameter if another @PUT-annotated method with the same @ParamParam-annotated
method parameter has the same @Path annotation:
>   @GET @Path("/users/{username}/foo")
>   public Foo getFoo(
>     @PathParam("username") String username)
>   @PUT @Path("/users/{username}/foo")
>   public Foo setFoo(
>     @PathParam("username") String username,
>     Foo foo)
> The runtime correctly invokes the first method for a GET. If I change the last path segment
of the first method to anything but "foo", the runtime will provide the method parameter properly,
but if I keep them the same the value of username will always be null.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message