[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

[ https://issues.jboss.org/browse/WFLY-5321?page=com.atlassian.jira.plugin.... ] Geoffrey De Smet edited comment on WFLY-5321 at 9/11/15 3:33 AM: ----------------------------------------------------------------- That log line doesn't show up, not in a fresh install of 9.0.1.Final (downloaded again this morning), nor in 8.1.0.Final. In the wildfly admin console I can see the deployment listed as succeeded, but I again don't find any reference to the web context nor the localhost url, not even in the undertow component. Seeing as I can't guess it either, I think the http service isn't actually there - but it would be nice to somehow confirm this. Note: this issue is NOT about whatever is causing my http service to be not available (I must have made a mistake somewhere), instead it's about me not having enough feedback from wildfly 9 to determine what's going on: it says it's deployed, it's a war with html files, but I can't find the http service. It should it say where it is or why it's failed. Especially because deploying a war is a typical first user action, the error message experience is important to improve adoption. was (Author: ge0ffrey): That log line doesn't show up, not in a fresh install of 9.0.1.Final (downloaded again this morning), nor in 8.1.0.Final. In the wildfly admin console I can see the deployment listed as succeeded, but I again don't find any reference to the web context nor the localhost url, not even in the undertow component. Seeing as I can't guess it either, I think the http service isn't actually there - but it would be nice to somehow confirm this. Note: this issue is NOT about whatever is causing my http service to be not available (I must have made a mistake somewhere), instead it's about me not having enough feedback from wildfly 9 to determine what's going on: it says it's deployed, it's a war with html files, but I can't find it. It should it say where it is or why it's failed. Especially because deploying a war is a typical first user action, the error message experience is important to improve adoption. -- This message was sent by Atlassian JIRA (v6.4.11#64026)