]
Scott M Stark resolved JBAS-6219.
---------------------------------
Fix Version/s: JBossAS-5.1.0.Beta1
Resolution: Done
With the jboss-managed 2.1.0.CR3 and related JBAS changes this is fixed. The console
running in the server was seeing call by reference values from the getTemplate call.
ManagementView.getTemplate() should return a new copy of the
DeploymentTemplateInfo on every call
-------------------------------------------------------------------------------------------------
Key: JBAS-6219
URL:
https://jira.jboss.org/jira/browse/JBAS-6219
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Fix For: JBossAS-5.1.0.Beta1
In our create-resource code, we do the following:
DeploymentTemplateInfo template = managementView.getTemplate(templateName);
Map<String, ManagedProperty> managedProperties = template.getProperties();
// Update managedProperties according to the properties the user entered in the EmbJopr
UI.
managementView.applyTemplate(ManagedDeployment.DeploymentPhase.APPLICATION,
resourceName, template);
managementView.process();
This all works fine the first time through. The problem is the next time we execute the
above code using the same templateName, getTemplate(() returns the same
DeploymentTemplateInfo from the previous call (with the updates we made to its
managedProperties). Instead, it should return a new "fresh"
DeploymentTemplateInfo object that contains only the properties from the original
template.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: