The test-example-binding-manager does not check enough details

The test-example-binding-manager is simply checking to see if the servers start and respond to their http ports. This is currently passing:

[starksm@banshee9100 testsuite]$ ant test-example-binding-manager
Buildfile: build.xml
Overriding previous definition of reference to xdoclet.task.classpath

test-example-binding-manager:
[echo] creating binding-manager1 config, jboss.dist=C:\cvs\JBoss4.0\jboss-4
.0\build\output\jboss-4.0.3beta
[copy] Copying 324 files to C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.
0.3beta\server\binding-manager1
[copy] Copied 79 empty directories to 1 empty directory under C:\cvs\JBoss4
.0\jboss-4.0\build\output\jboss-4.0.3beta\server\binding-manager1
[echo] creating binding-manager2 config, jboss.dist=C:\cvs\JBoss4.0\jboss-4
.0\build\output\jboss-4.0.3beta
[copy] Copying 324 files to C:\cvs\JBoss4.0\jboss-4.0\build\output\jboss-4.
0.3beta\server\binding-manager2
[copy] Copied 79 empty directories to 1 empty directory under C:\cvs\JBoss4
.0\jboss-4.0\build\output\jboss-4.0.3beta\server\binding-manager2
[echo] Will start the jboss instance localhost with binding-manager1
[echo] Waiting for http://localhost:8180
[echo] Will start the jboss instance localhost with binding-manager2
[echo] Waiting for http://localhost:8280
[echo] Will stop the jboss instance at url jnp://localhost:1299
[java] Shutdown message has been posted to the server.
[java] Server shutdown may take a while - check logfiles for completion
[echo] Will stop the jboss instance at url jnp://localhost:1199
[java] Shutdown message has been posted to the server.
[java] Server shutdown may take a while - check logfiles for completion

even though the example binding configuration has not been updated to including a binding for the PooledInvokerHA which was added to the cluster-service.xml:

2005-05-07 06:49:37,920 ERROR [org.jboss.invocation.pooled.server.PooledInvokerHA] Starting failed jboss:service=invoker,type=pooledha
java.lang.Exception: Port 4446 is already in use
at org.jboss.invocation.pooled.server.PooledInvoker.startService(PooledInvoker.java:179)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:272)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:222)
at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:897)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:418)
at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

There needs to be a run of a unit test that queries every mbean service in the server to validate that it has reached the started state to properly validate the binding service configuration.