[
https://jira.jboss.org/jira/browse/JBAS-6862?page=com.atlassian.jira.plug...
]
Emanuel Muckenhuber resolved JBAS-6862.
---------------------------------------
Resolution: Done
ManagedDeploymentImpl unitMOs does not use name from
@ManagementObjectID
------------------------------------------------------------------------
Key: JBAS-6862
URL:
https://jira.jboss.org/jira/browse/JBAS-6862
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.1.0.CR1
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: JBossAS-5.1.0.GA
I've found that using the ManagementView to update the ServiceBindingSets deployed in
conf/bindings-jboss-beans.xml [1] does not result in the changed configs being persisted.
Ive traced the problem to the following call in AbstractAttachmentStore.updateDeployment:
ManagedObject managedObject =
comp.getDeployment().getManagedObject(parent.getName());
That returns null.
Reason it returns null is the name of the updated deployment is "ports-03",
which is set via a @ManagementObjectID annotation on ServiceBindingSet's
"name" property. But the above call results in a lookup in the
ManagedDeploymentImpl.unitMOs map. There the ManagedObject is stored under key
"Ports03Bindings", not "ports-03". "Ports03Bindings" is the
MC name of the underlying bean. Looks like whatever is populating this map is using the
wrong name as the key.
[1]
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_5_x/server/src/etc...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira