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

[Brian Stansberry (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated WFLY-300:
----------------------------------

    Git Pull Request: https://github.com/wildfly/wildfly/pull/4414  (was: https://github.com/jbossas/jboss-as/pull/4414)

    
> Logging indicates "missing dependency" not the cause of the error.
> ------------------------------------------------------------------
>
>                 Key: WFLY-300
>                 URL: https://issues.jboss.org/browse/WFLY-300
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Domain Management
>            Reporter: Paul Hinds
>            Assignee: Brian Stansberry
>             Fix For: 8.0.0.Alpha1
>
>
> 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