Looks like only solution so that JBossAS does not have conflict (where remoting specifies dependency on apache-tomcat) is to remove import of apache-tomcat from the remoting component-info.xml (as well as declaration of jboss-remoting-http.jar as an artifact). Then create a new jboss/remoting-http within the repository that declares jboss-remoting-http.jar as artifact and export with apache-tomcat as import. 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. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022286#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...