If went piecemeal, would need to reference http://labs.jboss.com/portal/jbossremoting/docs/guide/ch04.html for the components. As for the tomcat libs, should only be a problem if web container is using the same classloader as jbossas (which at least used to not be the default). If web container is using same classloader, then is certainly a problem (and a known one for a while - http://jira.jboss.com/jira/browse/JBAS-2766). I don't know how to solve this other than making sure remoting is tested with all the different tomcat releases and hope that there are no changes to the tomcat api between its releases that would cause remoting to not be compatible with all the versions. On top of all this is JBossWeb which seems to not be using apache-tomcat libs at all. Don't know what their API looks like, but if is different from tomcat connector api, will need to re-write a remoting http server for it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4022303#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...