[jboss-jira] [JBoss JIRA] (WFLY-3571) bad error message for invalid <resource-root path>

[Karl Pietrzak (JIRA)]

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

Karl Pietrzak commented on WFLY-3571:
-------------------------------------

@[~bstansberry]: Sorry about the description.  I just didn't test with anything other than a bad {{<resource-root>}} path, so I didn't want to make the claim that the h2 module always have bad error messages.

I just wish it printed a stack trace anywhere, or at least the related {{Exception.getMessage()}}; there are no logs at level ERROR or even WARN.  I'll take a look at {{AbstractOperationContext}}.

> bad error message for invalid <resource-root path>
> --------------------------------------------------
>
>                 Key: WFLY-3571
>                 URL: https://issues.jboss.org/browse/WFLY-3571
>             Project: WildFly
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Karl Pietrzak
>            Assignee: Brian Stansberry
>            Priority: Minor
>
> h3. What
> If you have a typo in your path for your module.xml for a JDBC driver, e.g.,
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <module xmlns="urn:jboss:module:1.0" name="com.mysql">
>         <resources>
>             <resource-root path="DOES.NOT.EXIST.jar"/>
>         </resources>
>         <dependencies>
>             <module name="javax.api"/>
>             <module name="javax.transaction.api"/>
>         </dependencies>
> </module>
> {code}
> WF just says:
> {noformat}
> 16:22:26,770 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 30) JBAS014613: Operation ("add") failed - address: ([
>     ("subsystem" => "datasources"),
>     ("jdbc-driver" => "com.mysql")
> {noformat}
> h3. Why
> This is not very informative, unfortunately.  Maybe it's logged as level DEBUG instead of WARN? If someone points me to the name of the class that handles this kind of thing, I can submit a patch/pull request.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)