[jboss-jira] [JBoss JIRA] (AS7-3222) RESTEasy: Ambiguity constructors of Resource aren't reported

[Pavel Janousek (Moved) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Janousek moved JBPAPP-7878 to AS7-3222:
---------------------------------------------

              Project: Application Server 7  (was: JBoss Enterprise Application Platform)
                  Key: AS7-3222  (was: JBPAPP-7878)
             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: Ambiguity constructors of Resource aren't reported
> ------------------------------------------------------------
>
>                 Key: AS7-3222
>                 URL: https://issues.jboss.org/browse/AS7-3222
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Pavel Janousek
>            Assignee: Weinan Li
>            Priority: Blocker
>
> Section 3.1.2. of JAX-RS specs says:
> <cite>
> A public constructor MAY include parameters annotated with one of the following: @Context, @Header-Param, @CookieParam, @MatrixParam, @QueryParam or @PathParam. However, depending on the resource class lifecycle and concurrency, per-request information may not make sense in a constructor. If more than one public constructor is suitable then an implementation MUST use the one with the most parameters. +Choosing amongst suitable constructors with the same number of parameters is implementation specific, implementations SHOULD generate a warning about such ambiguity.+
> <cite>
> Actual behavior is that none of warning is generated and some of suitable constructor is chosen silently. This is against implemented specs.

--
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