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

scott.stark@jboss.org do-not-reply at jboss.com
Tue Apr 14 17:48:46 EDT 2009


"emuckenhuber" wrote : One of the failures i mentioned was about restoring JMS destinations. The updates does not work
  | when the ManagedObjectClass(..) is not present in the deployment descriptor.
  | So the tests with this annotation element are passing, the one without is failing.
  | 
I don't understand why the ManagedObjectBuilder for the destination class is not seen. I'll try to look into why that is.

"emuckenhuber" wrote : 
  | One other problem i think we could have is that ManagedObjectFactory.initMO does not create the same output, as ManagementView (as this would require e.g. KernelDeploymentManagedObjectCreator)
  | 
  | Additionally the failures which can be seen during the bootstrap (https://jira.jboss.org/jira/browse/JBAS-6524)
  | seem also somehow related to this - as when processing the collection in the ManagedObjectFactory,
  | does not have access to the ComponentDeploymentContext.getMetaData() for each bean.
  | Not really sure about this, as it's been a while since i last looked into this.
  | 
  | So the main issue with that is when restoring the persisted information it is (of course) relying on the same ManagedObject structure as it was persisted before. Only the values are getting persisted and restored (which makes sense, as the metaType should not change)
  | 
  | Therefore i think that this kind of 'override' done by the InstanceClassFactories (getManagedObjectClass),
  | should be done outside the deployers - e.g. in ManagementView when creating the ManagedComponents.
  | So that it always creates the same MO for the attachment persistence.
  | Maybe a related topic Scott created: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222668
  | 
  | This does not not cover partial persistence and removing components, but i think we can discuss that later.
  |  
Ok, I see. We need to move the managed object factory extension behavior out of the deployers. I'll start looking at that.


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

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



More information about the jboss-dev-forums mailing list