[
https://issues.jboss.org/browse/AS7-3534?page=com.atlassian.jira.plugin.s...
]
Ondrej Zizka edited comment on AS7-3534 at 2/7/12 1:54 PM:
-----------------------------------------------------------
standalone.xml snippet fixed;
Also, this problem happens when the testsuite harness changes the datasource config to set
up different DB.
We don't have this covered per se.
For that reason, I created AS7-3659.
was (Author: ozizka):
Oops, wrong XML. To be fixed in few minutes.
TS: Fix datasource info test - check whether it's a module or a
deployment.
---------------------------------------------------------------------------
Key: AS7-3534
URL:
https://issues.jboss.org/browse/AS7-3534
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.0.CR1b
Reporter: Ondrej Zizka
Assignee: Vladimir Rastseluev
Priority: Critical
Fix For: 7.1.0.Final
Datasources deployed to deployments/ do not have some metadata.
Causes this:
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-param-pull/852...
Pls verify and fix the test:
{code:java}
final ModelNode result2 = result.get(0);
Assert.assertTrue(result2 != null);
Assert.assertTrue(result2.hasDefined("driver-module-name"));
Assert.assertTrue(result2.hasDefined("module-slot"));
Assert.assertTrue(result2.hasDefined("driver-name"));
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira