[jboss-jira] [JBoss JIRA] (AS7-6046) Logging indicates "missing dependency" not the cause of the error.

[Brian Stansberry (JIRA)]

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

Brian Stansberry commented on AS7-6046:
---------------------------------------

OK, I see the problem. ServiceVerificationHandler is reporting the error by calling OperationContext.getFailureDescription() and modifying that, and not by throwing an OperationFailedException. The logic that logs at ERROR during boot is in a catch block for an OFE, so it doesn't get invoked.
                
> Logging indicates "missing dependency" not the cause of the error.
> ------------------------------------------------------------------
>
>                 Key: AS7-6046
>                 URL: https://issues.jboss.org/browse/AS7-6046
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Domain Management
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: Paul Hinds
>            Priority: Minor
>             Fix For: 7.2.0.CR1
>
>
> If the Data sources config is incorrect so that the <driver> element does not match an existing driver, the error message is cryptic.
> JBAS014775:    New missing/unsatisfied dependencies:
>       service jboss.jdbc-driver.db2xa (missing) dependents: [service jboss.data-source.java:jboss/datasources/myDS]
> I would expect a log message at ERROR level, there is no error message while other data sources are loaded.
> Missing dependencies is printed on a line with no error level and the text of the message does not relate to the XML.
> I would expect the error message to indicate something about where to fix the error.
> e.g an XPath 
> subsystem[xmlns="urn:jboss:domain:datasources:1.0"]/datasources/datasource/driver.
> or some text that indicates the <driver> element is the problem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira