"scott.stark(a)jboss.org" wrote : "emuckenhuber" wrote : | | Furthermore - what's actually DeploymentTemplate.updateTemplate supposed to do? | | It's not implemented and i'm wondering why you should not call ManagementView.updateComponent ? | | Which is then the last thing referencing a VFSDeployment. | | | The notion was that the template might need to create the attachments that define the deployment after it has a VFSDeployment because it may not have put out enough information in the VirtualFile returned by the first phase when applyTemplate was called. A template may not want to have a complete xml or file based view of the properties what it writes out. | Hmm looking at applyTemplate() in ManagementView again, i noticed that applyTemplate() is actually creating a real file in a profile and therefore bypassing the minimal synchronization we have for ModifiedDeployments. I think it would make more sense to use the DeploymentManager for this. So it could write the template into a temp file and then use deploymentManager to distribute and deploy it? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211559#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...