I'm pretty sure I reported same issue as yours.
See:
https://issues.jboss.org/browse/WFLY-6015
Seems to be fixed, but it's not clear to me whether it will be part of
Wildfly 10 Final or not.
However you can easily work around: just add the datasource with with your
driver && config and DO NOT CLICK IN TEST CONNECTION, then while EDITING
the datasource you can test the connection as many times as you want. I did
that in Wildfly 10.0.0.CR5 and it worked just fine.
I wouldn't call that a blocker as there are couple of ways to create a
datasource.
Hope it helps.
Renann Prado
On Thu, Jan 28, 2016 at 11:58 PM, Danilo Cominotti Marques <
dcominottim(a)gmail.com> wrote:
Hello there,
I have seen the e-mail that listed the following issues as blockers for WildFly 10
Final,
1.
https://issues.jboss.org/browse/WFLY-5480
2.
https://issues.jboss.org/browse/WFCORE-1277
but I would clearly add the following one to that list,
3.
https://issues.jboss.org/browse/HAL-1030
because my company certainly wouldn't deploy WildFly 10 Final before this issue is
solved.
Any chances of having somebody look into it before the final release?
Thanks.
Danilo Cominotti Marques
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev