Don't see how the current logic could work with exploded archive. You have the "WATCH FILE" problem all over again. A deploymentContext could have a number of attachments associated with it that are loaded from different deployers and multiple files. One attachment could even be loaded from multiple files. This logic is going to need callbacks to the deployer that needs the attachment so that the deployer can identify timestamps to check the serialization event against. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002462#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...