Updates to managed properties no longer persisting when changes made through embedded console --------------------------------------------------------------------------------------------- Key: JBAS-6742 URL: https://jira.jboss.org/jira/browse/JBAS-6742 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ProfileService Reporter: Charles Crouch Assignee: Scott M Stark Priority: Blocker Fix For: JBossAS-5.1.0.CR1 (11:58:12 AM) ips: changes are not sticking (11:58:41 AM) ips: i change max pool size for a DS or a CF, and then go back to the Configuration tab, and the value is back at what it was before my change (12:04:54 PM) ips: our code hasn't changed in that area (12:06:02 PM) ips: look at AbstractManagedComponent.updateResourceConfiguration() (12:07:22 PM) ips: we look up the managedComponet, then we update its props, then we look it up again, and then we call updateComponent() (12:07:45 PM) ips: that 2nd time we look it up, it's giving us a new reference that has the original props (12:07:54 PM) ips: it obviously didn't used to do that (12:14:38 PM) ips: i'm going to peek into the mgtviewimpl and see if i can figure out what's going on (12:16:58 PM) ccrouch: i guess if worst came to worst we could refactor this stuff to use a single managed component (12:17:05 PM) ccrouch: during the update (12:18:04 PM) ips: yeah, that will probably work. i just want to understand when (if ever) we need to get a fresh copy of the component from the view (12:22:36 PM) ips: ok, looks like the mgtview's map of managedcomponents is only updated when load() is called or applyTemplate() is called (12:23:35 PM) ips: so i'm not sure why we're getting back a different reference... have to debug this some more (2:50:43 PM) ips: ok, i think this is just broken (2:51:00 PM) ips: but can you try to make sure you see it as well? (2:51:06 PM) ips: using the latest AS5 bits I tried with HEAD of embjopr and r86866 and confirmed the problem described above. I tried the same embjopr code in r86436 and it worked fine. -- 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