Author: ron.sigal(a)jboss.com Date: 2008-04-29 20:09:36 -0400 (Tue, 29 Apr 2008) New Revision: 4094 Modified: remoting2/branches/2.x/src/tests/org/jboss/test/remoting/deploy/DualDeploymentTestCase.java Log: JBREM-930: Eliminated testNoSubsystem(). Modified: remoting2/branches/2.x/src/tests/org/jboss/test/remoting/deploy/DualDeploymentTestCase.java =================================================================== --- remoting2/branches/2.x/src/tests/org/jboss/test/remoting/deploy/DualDeploymentTestCase.java 2008-04-29 08:41:39 UTC (rev 4093) +++ remoting2/branches/2.x/src/tests/org/jboss/test/remoting/deploy/DualDeploymentTestCase.java 2008-04-30 00:09:36 UTC (rev 4094) @@ -131,12 +131,26 @@ } /** + * Disabling this test. + * + * org.jboss.remoting.ServerInvoker is not written to support + * the assertion "should always use the last handler added" made below. + * + * There are two choices: + * + * 1. Implement the feature, or + * 2. Eliminate the test. + * + * Since there is no provision in the Remoting Guide that supports this feature, and + * it doesn't seem particularly useful, we'll leave the ServerInvoker code alone + * and eliminate the test. - Ron Sigal, 4/29/08 + * * If multiple handlers added to connector (thus server invoker) and subsystem is NOT * specified in client, then will be processed by last handler added. * * @throws Throwable */ - public void testNoSubsystem() throws Throwable + public void xtestNoSubsystem() throws Throwable { MBeanServer mbeanServer = MBeanServerFactory.createMBeanServer();