[jboss-dev-forums] [Design of POJO Server] - Re: Behavior with AbstractKernelController

[scott.stark@jboss.org]

The test runs multiple times now in head, but fails at each point because of:


  | junit.framework.ComparisonFailure: state is Destroyed expected:<DESTROY...> but was:<FAIL...>
  | 	at junit.framework.Assert.assertEquals(Assert.java:81)
  | 	at org.jboss.test.security.test.DynamicLoginConfigServiceUnitTestCase.testAuthConf(DynamicLoginConfigServiceUnitTestCase.java:165)
  | 

There is a change in the ServiceController to ignore requests to destroy a service that is in a FAILED state. Previouly only requests for services in ServiceContext.DESTROYED or ServiceContext.NOTYETINSTALLED were ignored.


  | 2006-08-25 12:01:26,641 DEBUG [org.jboss.system.ServiceController] destroying se
  | rvice: jboss:service=TestDynamicLoginConfig
  | 2006-08-25 12:01:26,641 DEBUG [org.jboss.system.ServiceController] Ignoring dest
  | roy request for service: jboss:service=TestDynamicLoginConfig at state FAILED
  | 

If we want backward compatibility we need to define the service state machine diagram with all transitions and require the same under the mc. I'm doubtful that this would be useful as we really should not allow a service to go from an error state liked FAILED to DESTROYED. At this point the service state diagram needs to be defined along with the expected semantics and code updated to conform to it in my view.


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

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