[wildfly-dev] Pretty-printing XML validation errors

[Aleksandar Kostadinov]

Brian Stansberry wrote on 07/20/16 20:23:
>
>> On Jul 20, 2016, at 8:59 AM, Aleksandar Kostadinov
>> <akostadi at redhat.com <mailto:akostadi at redhat.com>> wrote:
>>
>> Tomaž Cerar wrote on 07/20/16 16:38:
>>> Most of my concerns about this ware already raised by Brian (l18n, extra
>>> size of distro, inconsistencies between subsystems, ...)
>>>
>>> Also on top of this, having something like that would glorify
>>> configuration of server via XML,
>>> which is something we are trying to discourage  in favor of CLI /
>>> mgmt api.
>>
>> Excuse my ignorance if this is already taken care of. But last time I
>> looked, using whatever management API was not very nice for container
>> runtime. i.e. configuration changed through API was not persisted.
>> I am wondering if this is already fixed somehow or is at least somebody
>> considering it as an important use case (I think it should).
>
> Persisting server configuration changes made via the supported
> management APIs back to the config file has been done in AS 7.0 and
> later. Its a fundamental requirement.

I should have explained better. The config is saved on container. But 
container being stateless loses changes on restart. At least for 
OpenShift v2 that has been an issue.

Shame on me I didn't look at OpenShift v3 integration. I'm not sure how 
it is handled there. Perhaps I should have done my homework before 
hijacking the thread. Sorry about that. Hopefully I can check wildfly on 
v3 next week.