[
https://issues.jboss.org/browse/WFLY-5321?page=com.atlassian.jira.plugin....
]
Geoffrey De Smet edited comment on WFLY-5321 at 9/11/15 4:16 AM:
-----------------------------------------------------------------
After only doing this change:
https://github.com/ge0ffrey/optaconf/commit/fa9f20fe6495e2f59e327d8155650...
I do get the log line:
{code}
09:59:21,709 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 17)
WFLYUT0021: Registered web context: /optaconf-webapp
{code}
But without that change, I don't get the log line (nor can I find my html's).
I don't see how that change, which adds the `<finalname>` in the pom.xml and
removes the jboss-web.xml file can fix it so undertow does expose it. I can only see how
it could affect the url, but not how it could disable exposure alltogether.
Note: I deploy from IntelliJ IDEA 14.1.4 (= latest version).
So it seems that wildfly has been stating correct info all the time: it did deploy, but
undertow exposed nothing. Although I would expect an error message from undertow as to why
it didn't expose it. Furthermore, the question is what's causing undertow not to
expose it:
- a bug in WildFly?
- a bug in IntelliJ?
- something wrong in those few lines that my github commit above changes? I can't see
how it could be that.
was (Author: ge0ffrey):
By only doing this change:
https://github.com/ge0ffrey/optaconf/commit/fa9f20fe6495e2f59e327d8155650...
I do get the log line:
{code}
09:59:21,709 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 17)
WFLYUT0021: Registered web context: /optaconf-webapp
{code}
But without that change, I don't get the log line (nor can I find my html's).
However I don't see how that change, which adds the `<finalname>` in the pom.xml
and removes the jboss-web.xml file can fix it so undertow does expose it.
Note: I deploy from IntelliJ IDEA 14.1.4 (= latest version).
So it seems that wildfly has been stating correct info all the time: it did deploy, but
undertow exposed nothing. Although I would expect an error message from undertow as to why
it didn't expose it. Furthermore, the question is what's causing undertow not to
expose it:
- a bug in WildFly?
- a bug in IntelliJ?
- something wrong in those few lines that my github commit above changes? I can't see
how it could be that.
Deploying a war to wildfly should mention the localhost url including
context root of that war in the log
---------------------------------------------------------------------------------------------------------
Key: WFLY-5321
URL:
https://issues.jboss.org/browse/WFLY-5321
Project: WildFly
Issue Type: Enhancement
Components: Web (Undertow)
Reporter: Geoffrey De Smet
Assignee: Tomaz Cerar
Priority: Minor
Here what I see now in the log:
{code}
[2015-09-10 04:56:44,211] Artifact optaconf-webapp:war exploded: Artifact is being
deployed, please wait...
16:56:44,235 INFO [org.jboss.weld.deployer] (MSC service thread 1-9) JBAS016009:
Stopping weld service for deployment optaconf-webapp-0.1.0-SNAPSHOT
16:56:44,244 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877:
Stopped deployment optaconf-webapp-0.1.0-SNAPSHOT (runtime-name:
optaconf-webapp-0.1.0-SNAPSHOT) in 15ms
16:56:44,255 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018558:
Undeployed "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name:
"optaconf-webapp-0.1.0-SNAPSHOT")
16:56:44,322 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876:
Starting deployment of "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name:
"optaconf-webapp-0.1.0-SNAPSHOT")
...
16:56:44,508 INFO [org.jboss.as.server] (management-handler-thread - 3) JBAS018559:
Deployed "optaconf-webapp-0.1.0-SNAPSHOT" (runtime-name :
"optaconf-webapp-0.1.0-SNAPSHOT")
[2015-09-10 04:56:44,519] Artifact optaconf-webapp:war exploded: Artifact is deployed
successfully
[2015-09-10 04:56:44,519] Artifact optaconf-webapp:war exploded: Deploy took 308
milliseconds
{code}
But as a developer, it's very hard to figure out the url to test the app, especially
if someone changed it recently. Note that in my case it could be any of these, depending
on the state of the jboss-web.xml, war file name (potentially exploded), IDE
configuration, etc:
-
http://localhost:8080/optaconf-webapp-0.1.0-SNAPSHOT/
-
http://localhost:8080/optaconf-webapp/
-
http://localhost:8080/optaconf/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)