&quot;bill.burke(a)jboss.com&quot; wrote : I'm thinking of: | | | | DeploymentContext.getAttachments().addAttachment(key, value, List<VirtualFile> metaSources); | | | | Then, when getAttachment() is called, DC scans and checks to see if that attachment should be killed. | It should be the repository that scans the deployment and throws aways preprocessed content, not the DC. The repository could already have an index of metadata files, etc. I would rather have the api just provide the DC relative metadata file path than the full VirtualFile. &quot;bill.burke(a)jboss.com&quot; wrote : | Also, there should be additional methods on DeploymentContext: | | | | getAttachments(); | | getManagedObjects(); | | | | These attachments would actually be serialized with the profile while getTransientAttachments() would not. | | If i'm being too obvious, then apologies. | There is no difference between getAttachments() and getManagedObjects(). Both are attachments, or are you saying you want to express a DC ManagedObject at that level rather than use the ManagedObjectBuilder: | public interface ManagedObjectBuilder | { | /** | * Build managed objects for this deployment context | * | * @param unit the deployment unit | * @param managedObjects the managed objects | * @throws DeploymentException | */ | void build(DeploymentUnit unit, Map<String, ManagedObject> managedObjects) throws DeploymentException; | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002948#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...