[
https://issues.jboss.org/browse/AS7-3214?page=com.atlassian.jira.plugin.s...
]
Pavel Janousek moved JBPAPP-7874 to AS7-3214:
---------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform)
Key: AS7-3214 (was: JBPAPP-7874)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.0.CR1b
(was: EAP 6.0.0 DR 9)
Component/s: REST
(was: RESTEasy)
Security: (was: JBoss Internal)
Docs QE Status: (was: NEW)
RESTEasy: Resource with resource method with more than one parameter
that is not annotated isn't rejected, nor warning generated
--------------------------------------------------------------------------------------------------------------------------------
Key: AS7-3214
URL:
https://issues.jboss.org/browse/AS7-3214
Project: Application Server 7
Issue Type: Bug
Components: REST
Affects Versions: 7.1.0.CR1b
Reporter: Pavel Janousek
Assignee: Weinan Li
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