[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-6046:
---------------------------------------
It is unlikely that an error message referencing the xml file will be provided; certainly
not in AS 7. The parsing is long finished by the time the missing dependency is detected
and the logic that detects the failure is generic and unaware that the faulty
configuration came from xml vs a management client like the CLI or admin console.
However, there should be an ERROR level log message during boot. There won't be if you
add the datasource post-boot via the CLI or admin console, since in that case the error
message is propagated to the client. But during boot there should be and if there
isn't, that's a bug.
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
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