[
https://issues.jboss.org/browse/WFCORE-2441?page=com.atlassian.jira.plugi...
]
Brian Stansberry commented on WFCORE-2441:
------------------------------------------
Making a nillable attribute non-nillable is a breaking API change so it shouldn't be
done for less than critical reasons. Note that I'm talking about truly nillable here,
i.e. the attribute can be left undefined and you still get a properly functioning system.
If there is wrong metadata that says it can be undefined but it blows up if you try,
fixing the metadata is not a breaking change.
Inconsistency between DMR and XSD representation of Elytron
simple-permission-mapper
------------------------------------------------------------------------------------
Key: WFCORE-2441
URL:
https://issues.jboss.org/browse/WFCORE-2441
Project: WildFly Core
Issue Type: Bug
Components: Security
Affects Versions: 3.0.0.Beta7
Reporter: Ondrej Kotek
Assignee: Ilia Vassilev
Labels: user_experience
There are inconsistencies between DMR and XSD representation of
{{constant-permission-mapper}}.
According to XSD {{permission}} must occur at least one times in
{{constant-permission-mapper}}. According to DMR it is {{"nillable" =>
true}}. This should be unified.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)