[jboss-jira] [JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present

[Pavel Janousek (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12670792#comment-12670792 ] 

Pavel Janousek commented on AS7-3199:
-------------------------------------

Could be (at least) generated error message something aka "unsupported case" and not pure confusing exception?

Anyway - which backward compatibility case breaks this requirement? One Application sub-class will be supported faraway, when being deploy more App. sub-class behavior will be the same as in reference impl. (Jersey) - which customer's expectation will be broken?
                
> RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present
> ---------------------------------------------------------------------------------------------
>
>                 Key: AS7-3199
>                 URL: https://issues.jboss.org/browse/AS7-3199
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: REST
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Pavel Janousek
>            Assignee: Stuart Douglas
>            Priority: Critical
>              Labels: eap6_prd_req
>             Fix For: 7.1.1.Final
>
>         Attachments: ExampleJAXRS.war
>
>
> If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed."
> This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for
> more than one application to be deployed +at the same effective servlet mapping+".
> If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+.

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