All that is needed is to change the InvokerLocator attribute value. So, for rmi, would be:
rmi://${jboss.bind.address}:8084 A handler will need to be specified if using the service xml to start the remoting connector service. Also worth noting that am currently adding ability for finer grained configuration (for the specific transports), which will be in beta release next month (or can get it from CVS HEAD). Another note about transports, the soap and async transports are being removed. The soap transport does not make sense, as no way to provide a standard SOAP interface for thirdparties to use, so will be replaced with HTTP invoker. The async will be replaced with nio transport (but this is further out). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859636#3859636 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859636 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development