In my case, I wanted a small-scale solution for development. I found that I could do either of the following to get around the issue and still use HSQL. Both involved an edit of deploy/ejb-deployer.xml
| a) turn off EJBTimer persistence by uncommenting the NoopPersistencePolicy and commenting out the DatabasePersistencePolicy- this can eliminate the use of multiple data sources and avoid the need for XA, or | | b) change the EJBTimer DatabasePersistencePolicy DataSource attribute to be the same data source that my EJB is accessing - this causes both data sources to be the same resource and seems to be smart enough to avoid XA. | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052319#4052319 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052319 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
