This is done via JBoss mbean service (Connector) being deployed (see http://labs.jboss.com/portal/jbossremoting/docs/guide/ch04.html#d0e858 for example). This means that in order for the servlet part (ServerInvokerServlet) to be able to find the deployed remoting servlet invoker, must be done this way. I really don't like this approach (especially since depends on jmx), so am working on another way that will not require jmx (or mbean service deployment). Gets pretty sticky though as separation of classloaders can come into play, which makes it difficult. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957510#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...