[CXF-5214] Using BeanParam in a subresource results in exception

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.7.6
• Fix Version/s: 2.7.7, 3.0.0-milestone1
• Component/s: JAX-RS
• Estimated Complexity: Unknown
• Assignee: Sergey Beryozkin
• Reporter: Martijn Dashorst
• Created: 17/Aug/13 19:30
• Updated: 27/Sep/13 18:18
• Resolved: 20/Aug/13 13:16

Description

I'm unable to use a @BeanParam in subresource without specifying the bean parameter in the first method call as a method parameter in the resource call chain. In pseudo code:

class Bean {
@QueryParam("name")
private String name;
... getters/setters
}
@Path("/")
@Produces(MediaType.PLAIN_TEXT)
class Root {
@Context private ResourceContext resources;

@GET public String get()

{ return "/hello"; }

@Path("hello")
public HelloResource hello()

{ return resources.getResource(HelloResource.class); }

}

class HelloResource {
@BeanParam
private Bean params;

@GET
public String get()

{ return "Hello, " + params.getName() + "!"; }

}

This fails with an exception in JAXRSUtils.java line 1000 or so. Changing Root#hello's signature to:

@Path("hello")
public HelloResource hello(@SuppressWarnings("unused") @BeanParam Bean param) {
}

makes the exception go away and has the Bean injected into HelloResource.

In my opinion this should not be necessary, and indeed, Jersey and RestEasy both work support this construct without having to resort to introducing unused parameters.

I've attached a quickstart that shows the problem.