I've gave it a try yesterday night. I got it working on my machine, and the integration tests pass in a significant percentage. However, there are a couple of things that need to be cleared out, either internally or with third parties. Here's a list: 1. jbossws depends on Remoting 2.2.0.Alpha2 and we need Remoting 2.2.0.Alpha7. Unless jbossws doesn't declare itself compatible with Alpha7, we can't go unscoped. 2. For some reason that's not entirely clear to me, there's a apache-logging version conflict in apache-tomcat. I don't know how to fix this. Scott? 3. For real clustering, hypersonic won't do. We need a real database. However, I probably could bend the configuration files so if started in non-clustered mode, Messaging would use hypersonic, so people can give Messaging a try in non-clustered configuration. Again, for serious stuff, people should get rid of hypersonic. If we go for MySQL, we'll need to install drivers, etc. This is related to point 5. below. 4. I badly hacked org.jboss.mq.server.jmx and I need to return to it to do it right. Scott, what do we need that package for? 5. Need two different configurations (clustered and non-clustered). Need to modify jboss's build system for that. This way, we avoid needing jgroups.jar in non-clustered mode. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018134#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...