[
https://issues.redhat.com/browse/WFCORE-408?page=com.atlassian.jira.plugi...
]
Darran Lofthouse commented on WFCORE-408:
-----------------------------------------
The need may have been dropped a bit TBH moving to persistent resource definitions has
helped with a lot of the mismatch type problems we used to have - I wouldn't worry too
much about this one now.
Add a TRACE level category for the operations used to start a
server.
---------------------------------------------------------------------
Key: WFCORE-408
URL:
https://issues.redhat.com/browse/WFCORE-408
Project: WildFly Core
Issue Type: Enhancement
Components: Logging, Management
Reporter: Darran Lofthouse
Priority: Major
Sometimes after being able to start a server from the XML configuration it is useful to
be able to identify the actual operations that are executed to start the server.
From a development perspective this is useful for double checking the operations are as
we expect.
From an end user perspective this can be useful to identify the set of equivalent
operations needed if the same was to be achieved in a CLI script.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)