[
https://issues.jboss.org/browse/WFCORE-87?page=com.atlassian.jira.plugin....
]
Claudio Miranda commented on WFCORE-87:
---------------------------------------
Hmm, are you talking about the 'last modified' time of the
deployment file itself?
Yes. This is related to a facility, where admin users can see when the application was
deployed, regardless of disable/enable. From an user perspective this is the deployment
time, that is when he uploaded the file to wildfly. If anyone asks the user admin
"when did you deploy this application ?", he can look at this deploy time (last
modified attribute).
When server restarts, the user can wrongly assume the application was replaced, if the
enable/disable attribute is used.
I understand your point related to the complexity of exploded deployments, I just wanted
to expose my thoughts related to the deployment time.
However I will follow your suggestion to use the following attribute:
You suggested the attributes as:
deployed-time (long)
deployed-timestamp (string with a format documented in the attribute description)
undeployed-time (long)
undeployed-timestamp (string)
Do you think the word "deploy" can wrongly suggests that is the timestamp user
uploaded the file to WF ?
What do you think of these, as they reflect the deploy status accordingly to the
STATUS/ENABLED attribute definition.
enabled-time (long)
enabled-timestamp (string with a format documented in the attribute description)
disabled-time (long)
disabled-timestamp (string)
Display deployment timestamp
----------------------------
Key: WFCORE-87
URL:
https://issues.jboss.org/browse/WFCORE-87
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 1.0.0.Alpha5
Reporter: Claudio Miranda
Assignee: Brian Stansberry
Priority: Minor
Display the deployment timestamp, that is the date of last modified deployment. It is
useful for users to see the date and time of deployments.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)