[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - http://jira.jboss.org/jira/browse/JBMESSAGING-861

[sergeypk]

http://jira.jboss.org/jira/browse/JBMESSAGING-861 - Change the test framework to use remoting-service.xml configuration for testing, and drop ServiceContainer duplicate remoting configuration.

I have an implementation of this ready but I'm not sure on certain points:

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?

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?

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?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4052644#4052644

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4052644