[jboss-jira] [JBoss JIRA] (WFLY-4378) Infinispan/JGroups subsystem check for and correct diffs in the default config we ship vs. what we persist
Radoslav Husar (JIRA)
issues at jboss.org
Tue Jun 9 17:38:02 EDT 2015
[ https://issues.jboss.org/browse/WFLY-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076437#comment-13076437 ]
Radoslav Husar commented on WFLY-4378:
--------------------------------------
If we were to not ignore new lines, the differences are in messaging (uses org.jboss.as.messaging.MessagingXMLWriter#writeNewLine) and between sections extensions/profile/interfaces/socket-binding-group.
> Infinispan/JGroups subsystem check for and correct diffs in the default config we ship vs. what we persist
> -----------------------------------------------------------------------------------------------------------
>
> Key: WFLY-4378
> URL: https://issues.jboss.org/browse/WFLY-4378
> Project: WildFly
> Issue Type: Task
> Components: Clustering
> Affects Versions: 9.0.0.Alpha1
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Fix For: 9.0.0.CR2, 10.0.0.Alpha3
>
>
> https://github.com/wildfly/wildfly/pull/7184#issuecomment-75439059
> Brian:
> {quote}Semi-tangent: could you guys check for and correct diffs in the default config we ship vs. what we persist? E.g.
> 1) Start a new server running standalone-full-ha.xml
> 2) Use cli to add a system prop (just to force persistence)
> 3) Diff standalone-full-ha.xml vs standalone/configuration/standalone_xml_history/standalone-full-ha.initial.xml
> There shouldn't be changes other than the added system prop. Any changes mean either our default configs are wrong or the marshalling is wrong. Both should match xsd. I did this for another reason a couple weeks ago and saw some changes in the clustering subsystems. Perhaps this PR fixes the problem, but I have a feeling I saw something else besides this.{quote}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jboss-jira
mailing list