[ https://issues.jboss.org/browse/AS7-1674?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-1674: -------------------------------- Assignee: Bill Burke (was: Alessio Soldano) Component/s: REST -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1674?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-1674. --------------------------------- Assignee: Stuart Douglas (was: Bill Burke) Resolution: Won't Fix According to the JAX-RS spec there are three ways to activate a restful endpoint. These three methods are specified in the JAX-RS 1.1 specification in section 2.3.2. 1) Not including an application class and using web.xml as described above 2) subclassing javax.ws.rs.core.Application and using web.xml 3) subclassing javax.ws.rs.core.Application and using the ApplicationPath annotation. See https://docs.jboss.org/author/display/AS7/JAX-RS+Reference+Guide The idea that resteasy should be activated if there happens to be a JAX-RS annotation in the deployment does not really work. For one thing, where would you map it to? For another, this means that if a 3rd party app library includes a class with a JAX-RS annotation then resteasy would be activated wether you wanted it or not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira