[jboss-jira] [JBoss JIRA] Commented: (JBREM-63) Get rid of the legacy configuration that embeds xml parsing

[ http://jira.jboss.com/jira/browse/JBREM-63?page=comments#action_12383509 ] Ron Sigal commented on JBREM-63: -------------------------------- org.jboss.remoting.transport.remoting.Connector can now be configured by way of an org.jboss.remoting.ServerConfiguration. ServerConfiguration holds four components: 1. transport (supplied by constructor) 2. invokerLocatorParameters: the is a map of all parameter names and values that will go into the org.jboss.remoting.InvokerLocator 3. serverParameters: this is a map of parameter names and values that will be used by the server but will not go into the InvokerLocator 4. invocationHandlers: this is a map of invocation handlers. The key is the subsystem, or comma separated list of subsystems. Note that parameter values in invokerLocatorParameters override values in serverParameters, if a parameter appears in both. ServerConfiguration may be used programmatically, but it is primarily intended to be constructed from a jboss-beans.xml file by a microcontainer and injected into a Connector. Unit test: org.jboss.test.remoting.transport.config.POJOConfigurationTestCase. Waiting for cruisecontrol results. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira