[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ] Bill Burke commented on AS7-3199: --------------------------------- Its really bad practice for third-party libs to include Application classes as there is no way to exclude them from a scan. FWIW, you think my comments are angry, well, its more frustration that I have to keep repeating myself. I'll elaborate a little bit more to give a better picture: Anybody using the ServletContextListener to bootstrap resteasy would become broken if I fixed the Application problem. This includes anybody using the Spring and Guice integrations. Does that paint a clearer picture? What I think can be done is to change the JAX-RS AS deployer so that it only barfs if there are multiple Application classes annotated with @ApplicationPath and ignore any other non-annotated Application class. Anything other than that will have to wait. Sorry, but that's just the way it is. BTW, if you decide to remove Resteasy from AS and/or EAP or offer an alternative, please let me know so I can look for another job. Thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira