[jboss-jira] [JBoss JIRA] (WFLY-6274) Please improve deployment logging

[David Lloyd (JIRA)]

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

David Lloyd commented on WFLY-6274:
-----------------------------------

Unless someone has a quick fix for this, I think this falls squarely under the deployment revamp work in my queue.

> Please improve deployment logging
> ---------------------------------
>
>                 Key: WFLY-6274
>                 URL: https://issues.jboss.org/browse/WFLY-6274
>             Project: WildFly
>          Issue Type: Feature Request
>            Reporter: Rick Wagner
>            Assignee: David Lloyd
>
> Wildfly attempts to deploy mal-formed artifacts and does not provide useful feedback to the user.  (In fact, it provides feedback that hints that things are ok, when really they are not.)
> As an example, deploying a flawed XML descriptor (targeted at no particular Wildfly subsystem) brings this:
> 08:30:37,675 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015876: Starting deployment of "bogus.xml" (runtime-name: "bogus.xml")
> 08:30:38,085 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015859: Deployed "bogus.xml" (runtime-name : "bogus.xml")
> If the user is attempting to make use of a Wildfly subsystem (say Wildlfy-Camel) but has an unacceptable descriptor, no useful feedback is provided.  The user will think their application is 'deployed' (as logged) when really it has been ignored.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)