Perhaps we should test with both so we could always fall back to MQ if things don't work out. Then we have zero extra risk. Messaging and MQ should be very easily changeable so swapping them in and out and running the tests shouldn't be a big overhead. Dimitris Andreadis wrote: > The point is JbossAS 4.2.0.CR1 needs *a lot* of testing before it goes > out, so we need to have the messaging implementation available by > January, or else delay the whole thing. > >> On a related note: >> >> What are people's thoughts on having JBoss Messaging 1.2 GA as the >> default messaging provider in AS 4.2 (as well as AS 5 clearly), >> rather than JBoss MQ. >> >> By 4.2 GA we should be fully functional with clustering etc.... > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development >