-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR10, 7.1.0.DR11, 7.1.0.DR13
-
None
Description of problem:
RESTEasy doesn't print warning during deployment if war application contains end-points, but RESTEasy is not enabled. Example:
- Simple end-point:
@Path("example") public class ExampleResource { @GET @Produces("text/plain") public String get() { return "Hello world!"; } }
- Web.xml is not used.
- Example of application is attached.
Actual results - server logs after deploying:
14:17:55,604 INFO [org.jboss.as.repository] (management-handler-thread - 3) WFLYDR0001: Content added at location /home/mkopecky/playground/eap/7.1.0.DR10/jboss-eap-7.1/standalone/data/content/f3/8e631161bdab8c6bf1d538fc5bfc6f443f001b/content 14:17:55,617 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "application-path-example.war" (runtime-name: "application-path-example.war") 14:17:57,741 WARN [org.jboss.as.ee] (MSC service thread 1-2) WFLYEE0007: Not installing optional component org.springframework.http.server.ServletServerHttpAsyncRequestControl due to an exception (enable DEBUG log level to see the cause) 14:17:57,742 WARN [org.jboss.as.ee] (MSC service thread 1-2) WFLYEE0007: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to an exception (enable DEBUG log level to see the cause) 14:17:57,890 INFO [io.undertow.servlet] (ServerService Thread Pool -- 70) No Spring WebApplicationInitializer types detected on classpath 14:17:57,943 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 70) Initializing Mojarra 2.2.13.SP3 for context '/application-path-example' 14:17:58,438 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0021: Registered web context: '/application-path-example' for server 'default-server' 14:17:58,480 INFO [org.jboss.as.server] (management-handler-thread - 3) WFLYSRV0010: Deployed "application-path-example.war" (runtime-name : "application-path-example.war")
Expected results:
... 14:17:57,741 WARN [whatever] (whatever) RESTEASY123456: Deployed application contains end-poin, that are not enabled ...
Additional info:
RESTEasy is able to see also this disabled end-point, because read-resource operation can read basic information about end-point:
[standalone@localhost:9990 /] /deployment=application-path-example.war/subsystem=jaxrs:read-resource(recursive=true,include-runtime=true) { "outcome" => "success", "result" => {"rest-resource" => {"org.resteasy.ExampleResource" => { "resource-class" => "org.resteasy.ExampleResource", "rest-resource-paths" => [{ "resource-path" => "example", "consumes" => undefined, "produces" => ["text/plain"], "java-method" => "java.lang.String org.resteasy.ExampleResource.get()" }], "sub-resource-locators" => undefined }}} } [standalone@localhost:9990 /]
- causes
-
JBEAP-10392 Warning "WFLYRS0015: No Servlet declaration found for JAX-RS application." raised for non-JAX-RS submodules
- Verified
- is related to
-
JBEAP-8316 RESTEasy doesn't print warning if application contains end-points, but RESTEasy is not enabled
- Closed
-
WFLY-7873 JaxRS archive does not warn when no servlet is provided.
- Closed
- relates to
-
JBEAP-8316 RESTEasy doesn't print warning if application contains end-points, but RESTEasy is not enabled
- Closed
-
WFLY-7873 JaxRS archive does not warn when no servlet is provided.
- Closed