"tom.elrod(a)jboss.com" wrote : Doing this would mean that messaging would then need to either pick out all the componentized remoting artifacts they need (i.e. jboss-remoting-core.jar, jboss-remoting-http.jar, etc.) or just get jboss-remoting.jar and jboss-remoting-http.jar. Messaging needs remoting HTTP support and it really doesn't care what version of Apache (or Jetty, or whatever) remoting uses. How would I know what jboss-remoting-http.jar version matches jboss-remoting.jar I am using? Let's say that Messaging takes a wild guess and arbitrarily decides that it should use Tomcat 5.5.15. That would create a conflict with JBossWeb 2.2.0. If Messaging instead declares it wants to a Tomcat version that makes JBossWeb happy, we end using Remoting with an untested tomcat version. How would our dependency map look like if you go for piecemeal jboss-remoting.jar/jboss-remoting-http.jar? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022291#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...