3 Replies Latest reply on Aug 8, 2003 9:05 PM by null null

    Where and what should be included in remoting

    Tom Elrod Master

      On the dev mailing list there has been some discussion on where and what should be included in the remoting and jboss build. As it stands right now, remoting is part of core because it is part of jmx (to provide jmx remoting). I'm not sure that it is used anywhere else currently, but think the plan is to use the generic remoting transport for all the sub projects, to gain consistency.

      Since the inherent purpose of remoting is to provide a transparent transport layer to provide remoting of services and POJOs, as well as detection of these, it make sense that there are (and will continue to be) a wide assortment of transport and protocol layers used.

      Thus we have a problem, since we don't want all this extra stuff in core (i.e. SOAP, JNP, etc.). There are many different ways to solve this, so please post your suggestion. Mine is to remove remoting from the core jmx and make it (yet another) a sub project dependant on both remoting and jmx. This will get remoting out of core and allow us to put in any of the extra protocols into the remoting project. Another solution would be to make the remoting project so that it will allow users to specify what they want included (not sure what to do about compile time though). This route will require a standard approach for configuring the what it to be included (anyone want to take this on?).