"sergeypk" a) the HTTP invoker is configured differently from socket-based invokers. If we are to configure the HTTP invoker from XML as well, should remoting-service.xml then be split into remoting-service-http.xml and remoting-service-bisocket.xml? Or should remoting-service.xml contain settings for both invokers? [/quote wrote : | | Ideally we should maintain a directory somewhere which has a remoting-service-http.xml and remoting-service-bisocket.xml and remoting-service-sslbisocket.xml in it. | | The test framework should then choose one of these based upon the test config. | | The same config should also be used when building the sar file and by the examples, since we don't want to duplicate the config anywhere. | | anonymous wrote : | | b) Should the bisocket configuration be shared among other socket-based invokers (socket, sslsocket, sslbisocket), or should I add a separate file for each of the invokers, thus duplicating the common settings? | | | | See above. | | Actually we only support http, bisocket and sslbisocket in JBM so don't worry about the others, but the ones we DO support should be in their own file. | | anonymous wrote : | | c) The way I've implemented this is I load remoting-service.xml, get hold of the configuration, fetch all attributes with isParam set and combine their keys and values to form the URL, since as far as I understand, the URL should only contain those attributes marked with isParam=true. However, serverSocketClass was originally included in the URL even though it is not marked with isParam. Is this the way it should be or is this an oversight? | | I don't understand why you are generating a locator URI, this should be unnecessary. | | You just need to deploy the remoting connector service from the xml. Certainly there should be no need to parse the xml and manually create a URI. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053186#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...