[jboss-dev-forums] [Design of Management Features on JBoss] - Re: Applying persisted changes.

[scott.stark@jboss.org]

"emuckenhuber" wrote : 
  | Looks like the MODefinitions are getting installed too late (as they are in deploy/messaging).
  | Moving those definitions to deployers/ seems to work, although in the end this should not be needed?
  | 

I don't see this if I run the JmsDestinationRestartUnitTestCase after the JmsDestinationOverrideTestCase when the server is running. The JmsDestinationRestartUnitTestCase.testQueueTemplate fails if I run the JmsDestinationOverrideTestCase and then restart the server, so we are loading something too early it seems.

In general both the mbean and MODefinitions would only be visible to the class loader of the deployment, so needing these classes visible when the deployers first load is not correct. We don't processes any persisted attachments unless we see a deployment with a matching attachments, so it could just be that this is an implicit dependency issue where the destinations-service.xml is getting processed before the messaging-jboss-beans.xml during startup. 


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

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