[ http://jira.jboss.com/jira/browse/JBMESSAGING-658?page=comments#action_12... ] Juha Lindfors commented on JBMESSAGING-658: ------------------------------------------- Fixed the failures raised by the JDBCPersistenceManager API change. The remaining failures on XATests were temporarily resolved by rolling back some Xid massaging changes that were part of original JBMESSAGING-407 patch. The reasoning was an unexpected Xid formatting from JBossTS. This is yet to be verified but if it is the case, another solution needs to be found. This is part of JBMESSAGING-647. If there really is a need for special Xid handling this would naturally fit into AS XAResourceWrapper implementation that is currently used for JBossTS/AS/Messaging integration (JBMESSAGING-645). However, XAResourceWrapper is not at this point decoupled from jboss.jar (see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=95276). Therefore, something else needs to be done for standalone deployment and integration of JBossMessaging and JBossTS (this is assuming the original issue that lead to 'funny' xids from JBossTS reveals itself again while resolving issue #647). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBMESSAGING-658?page=all ] Ovidiu Feodorov reopened JBMESSAGING-658: ----------------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira