[jboss-jira] [JBoss JIRA] (WFLY-8462) Improve feedback after invalid request for creating a datasource

[Harald Pehl (Jira)]

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

Harald Pehl commented on WFLY-8462:
-----------------------------------

I agree. In general, it's hard to come up with specific, user-friendly error messages. For very common use cases like data sources and deployments, I could try to be more specific when it comes to an error. That would require that I can rely on certain information in the error response e.g. error codes, specific information I can extract, ... 

> Improve feedback after invalid request for creating a datasource
> ----------------------------------------------------------------
>
>                 Key: WFLY-8462
>                 URL: https://issues.jboss.org/browse/WFLY-8462
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: JCA, Web Console
>    Affects Versions: 10.1.0.Final
>            Reporter: Karl-Philipp Richter
>            Assignee: Harald Pehl
>            Priority: Major
>
> After creating a Non-XA datasource in the web frontend and pressing finish on the last dialog page, I get the message "Unknown error" and the data entered into the form is lost. Clicking on "Unknown error" a dialog is displayed with the content
> ```
> Unexpected HTTP response: 500
> Request
> {
>     "name" => "jdbc/linuxtracker2",
>     "jta" => true,
>     "enabled" => true,
>     "user-name" => "APP",
>     "password" => "APP",
>     "jndi-name" => "java:/jdbc/linuxtracker2",
>     "use-ccm" => true,
>     "pool-name" => "jdbc/linuxtracker2_Pool",
>     "connection-url" => "jdbc:derby://localhost:1527/derby-pool",
>     "driver-class" => "org.apache.derby.jdbc.ClientDriver",
>     "driver-name" => "jdbc/linuxtracker2",
>     "operation" => "add",
>     "address" => [
>         ("subsystem" => "datasources"),
>         ("data-source" => "jdbc/linuxtracker2")
>     ]
> }
> Response
> Internal Server Error
> {
>     "outcome" => "failed",
>     "failure-description" => {
>         "WFLYCTL0412: Required services that are not installed:" => ["jboss.jdbc-driver.jdbc/linuxtracker2"],
>         "WFLYCTL0180: Services with missing/unavailable dependencies" => [
>             "org.wildfly.data-source.jdbc/linuxtracker2 is missing [jboss.jdbc-driver.jdbc/linuxtracker2]",
>             "jboss.driver-demander.java:/jdbc/linuxtracker2 is missing [jboss.jdbc-driver.jdbc/linuxtracker2]"
>         ]
>     },
>     "rolled-back" => true
> }
> ```
> which is extremely unhelpful given the fact that an error message listing and explaining the cause for the failure could be displayed (e.g. "the datasource xy couldn't be created because the name doesn't match the requirement yz").
> It's hard to guess that clicking on the "Unknown error" popup opens a dialog.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)