WADLGenerator ignores header or query parameters when FormParam parameters are available

Having a signature like this

@POST
@Consumes(@Consumes(MediaType.APPLICATION_FORM_URLENCODED)
void form3(@HeaderParam("headerId") String headerId,
           @QueryParam("queryId") String queryId,
           @PathParam("id") String id, 
           @FormParam("field1") String f1);

will lead to WADLGenerator losing header and query parameters in the generated WADL. Having a query parameter alonside form parameters does not make much sense but is technically possible for POSTs. The loss of the header parameter is more serious