[
https://issues.jboss.org/browse/WFCORE-2944?page=com.atlassian.jira.plugi...
]
Brian Stansberry edited comment on WFCORE-2944 at 6/12/17 10:13 AM:
--------------------------------------------------------------------
I don't think it's likely we'll change this as doing it would be probably be
quite invasive and bug prone.
The issue is a particular deployment resource is persistent or not due to the value of a
special attribute in that resource. The kernel, which decides whether the model has been
modified, knows nothing about this special value, only the xml marshaller of the resource
does. It's not a general concept of the model; it's kind of a specialized hack for
one resource type.
was (Author: brian.stansberry):
I think there was another issue about this, or perhaps an internal support list
discussion. I don't think it's likely we'll change this as doing it would be
probably be quite invasive and bug prone.
The issue is a particular deployment resource is persistent or not due to the value of a
special attribute in that resource. The kernel, which decides whether the model has been
modified, knows nothing about this special value, only the xml marshaller of the resource
does. It's not a general concept of the model; it's kind of a specialized hack for
one resource type.
Unexpected update of configuration file standalone.xml if an archive
is dropped to deployments folder
-----------------------------------------------------------------------------------------------------
Key: WFCORE-2944
URL:
https://issues.jboss.org/browse/WFCORE-2944
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Reporter: Wolf-Dieter Fink
Priority: Minor
It is not expected that the standalone.xml is written and versions or other content is
updated.
e.g. the top level element
<server xmlns="urn:jboss:domain:x.y">
It is expected that the standalone configuration is updated with the latest namespace
versions, or other changes, if the configuration needs to be persisted.
But for any unmanged deployment it is not expected and not necessary to update the
configuration file.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)