[ https://issues.jboss.org/browse/AS7-3214?page=com.atlassian.jira.plugin.s... ] Pavel Janousek updated AS7-3214: -------------------------------- Priority: Blocker (was: Major) Description: Section 3.3.2.1. of JAX-RS 1.1. specs says: <cite> 3.3.2.1 Entity Parameters The value of a non-annotated parameter, called the entity parameter, is mapped from the request entity body. Conversion between an entity body and a Java type is the responsibility of an entity provider, see section 4.2. Resource methods MUST NOT have more than one parameter that is not annotated with one of the above-listed annotations. </cite> Although a resource contains "endpoint" with method(s) goes against this specs, request is processed normally, without any error(s) occurred or reported. was: Section 3.3.2.1. of JAX-RS 1.1. specs says: <cite> 3.3.2.1 Entity Parameters The value of a non-annotated parameter, called the entity parameter, is mapped from the request entity body. Conversion between an entity body and a Java type is the responsibility of an entity provider, see section 4.2. Resource methods MUST NOT have more than one parameter that is not annotated with one of the above-listed annotations. </cite> If Reource contains methos that isn't conformed with second paragraph,actual behavior is only saying "404 - not found" when someone do access to a such "endpoint". I think we should provide better handling of this situation - I prefer rejecting of a such resource during deploying the JAX-RS application, but at least some warning could be generated at this situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira