Client view of the VFSDeployment more restricted for profile

[starksm64]

The client view VFSDeployment restricts what the profile service ManagementView can provide to the managed object layer in terms of creating deployments. Previously one could create a stub deployment file and add the real metadata as attachments to the DeploymentContext. Now the template needs to take the input managed properties and write out a complete deployment file, and the DeploymentTemplate.updateTemplateDeployment now has no value.

I'm not sure that this matters at this point, but wanted to mention this as the DeploymentTemplate interface should change as well.

[adrian.brock]

VFSDeployment is an interface. You can implement it how you like.

The default is predertermined attachments stored in a HashMap.

There's nothing to stop you using something else, e.g. deserializing them
from the file system (which is what I think you are trying to do)?

[adrian.brock]

Perhaps it would be easier if the parent Deployment interface had a
setAttachments() instead of implementing Attachments?

That way you use the same implementation and choose how you want
to pass your attachments.

The default should still be a HashMap.