[jboss-jira] [JBoss JIRA] (WFLY-5321) Deploying a war to wildfly should mention the localhost url including context root of that war in the log

[Tomaz Cerar (Jira)]

    [ https://issues.jboss.org/browse/WFLY-5321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687864#comment-13687864 ] 

Tomaz Cerar commented on WFLY-5321:
-----------------------------------

Ideal enhancement for this log message would be if it could display full URLs under which app is available for example

http://localhost:8080/helloworld
http://127.0.0.1:8080/helloworld
http://:::1:8080/helloworld 
https://127.0.0.1:8443/helloworld (if ssl is enabled)
...

for simple cases like default config, this is easy. 
but it gets tricky when you  have multiple virtual hosts and multiple servers configured all with different interface configuration.

as well as knowing the host name of the machine (which can be an expensive blocking operation, which is not a good thing to do on boot)

> 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
>            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
(v7.12.1#712002)