[
https://issues.jboss.org/browse/WFLY-2589?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-2589:
----------------------------------------
I'm looking at making this a configurable item. In a case where a new attribute is
added, with a default, but it can be discarded if undefined *by the user*, the current
test infrastructure can't cope. The fact the user wasn't the one who set the
default values ends up being lost and tests fail.
ReadTransformedResourceOperation should set include-defaults=false
when calling read-resource
---------------------------------------------------------------------------------------------
Key: WFLY-2589
URL:
https://issues.jboss.org/browse/WFLY-2589
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Domain Management
Affects Versions: 8.0.0.Beta1
Reporter: Kabir Khan
Assignee: Kabir Khan
This needs further investigation, but it seems to mean that we have a lot of ModelFixers
used in the wrong situation. i.e. the when transforming resources, attributes that should
be undefined reach the transformers as defined with the default value set instead.
This needs a bit of thinking about [~jmesnil] mentioned this a few weeks ago as well.
I'd like to see if he remembers before fixing
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira