[ https://issues.jboss.org/browse/WFCORE-1667?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-1667: ---------------------------------- Description: When executing a {{full-replace-deployment}} in a composite operation the deployment associated with the first step does not get it's {{enabled-time}} attribute updated. The second one always has an updated attribute. I've created a test to show the odd behavior, https://github.com/wildfly/wildfly-core/commit/452e2149571c87ff4cfcdfbd78.... Note that if you change the order of the archive arguments on the redeploy you'll see the failure happens on the second deployment instead of the first. Do note that this test may not be needed, but it was an easy way to show what the issue is. was:When executing a {{full-replace-deployment}} in a composite operation the deployment associated with the first step does not get it's {{enabled-time}} attribute updated. The second one always has an updated attribute. Steps to Reproduce: See test commit https://github.com/wildfly/wildfly-core/commit/452e2149571c87ff4cfcdfbd78... Summary: After a full-replace-deployment operation on a managed domain in a composite operation onf of the enabled timestamp is not updated (was: After a full-replace-deployment operation on a managed domain in a composite operation the first enabled timestamp is not updated) -- This message was sent by Atlassian JIRA (v6.4.11#64026)