[
https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s...
]
Ryan Connolly commented on AS7-3199:
------------------------------------
I have run into this a couple of times now. Workaround for internal code means a single
API base URI which probably makes sense for most web apps. The problem comes into play
when using thiribs that supply classes that extend Application. I hit this recently while
evaluating
http://velopers.helloreverb.com/swagger/ for instance.
Re-reading this thread, I'm still amazed at how angry bill sounds in the first few
comments. Read your book, bill. Thanks for the read. Hope you got some rest. (No pun
intended).
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
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
For more information on JIRA, see:
http://www.atlassian.com/software/jira