[ https://issues.jboss.org/browse/WFCORE-87?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFCORE-87: ---------------------------------------- enabled/disabled-time[stamp] sound fine to me. I'm curious how that '"timestamp" => "Fri Sep 05 00:42:19 BRT 2014"' in your example was derived. Was it the time the deployment resource was added? That wouldn't be the upload time once the server is rebooted. Or you worked out some way to get hold of a file timestamp? I can think of a number of pieces of info a user might be interested in related to "deploying": 1) Identifying info about the content they uploaded. That is, *its* timestamp. Then they can compare the timestamp reported in the management resource with what they have locally, say in some content management system or just the filesystem location where they store the 'official' version of a deployment. I don't see how we can support this kind of thing though, since we don't even require the client or the server to have access to a physical file. (For example you could deploy by providing an HTTP URL, or any URL, so long as the server can open a URLConnection and get the content.) 2) When they actually installed the deployment into the runtime. This is the enabled-time. 3) When they did the add of the deployment resource. TBH, this seems like the least useful of the 3. The only way we could support this would be by persisting the value in the config file; otherwise following reboot the "add time" would no longer be that and it would just be the server start time. Trying to use a file timestamp won't work, because deployments don't have to be "managed", i.e. stored in the content repo, and if they aren't the timestamp of the file will be when it was created/modified, not when it was uploaded. -- This message was sent by Atlassian JIRA (v6.3.1#6329)