"timfox" wrote : You just need to add the users in the sql properties of JDBCJMSUserManager
I will add a new user to the MockSecurityManager.
And I would need to add an user to mysql-persistence-service.xml.
I mean... I don't think it would be such a good to add a test user to mysql-persistence-service.xml, as that file is also distributed with the release. I guess JBossMQ does distribute those test users, but I'm not sure if we should do the same.
I have the same issue with the integration testsuite... JBossMQ has those users pre-configured out of the box.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012237#4012237
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012237
I had to add a new method to JDBCSupport to act as a hook.
JDBCSupport is doing a crosscheck betwen sqlProperties and default statements. When you define POPULATE.TABLES... JDBCSupport throws an exception during start.
protected boolean ignoreVerificationOnStartup(String statementName)
| {
| // Do not cross-check on POPULATE.TABLES. as we just load the tables with them
| if (statementName.startsWith("POPULATE.TABLES."))
| {
| return true;
| }
| return false;
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4012228#4012228
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4012228