[
https://issues.jboss.org/browse/WFLY-5413?page=com.atlassian.jira.plugin....
]
Tomasz Adamski reassigned WFLY-5413:
------------------------------------
Assignee: Ondřej Chaloupka (was: Tomasz Adamski)
To make the change that you ask for we would need a change to
PersistentResourceXMLDescription class in wildfly-core which currently does not marshall
default values. Will make this change when possible.
I don't agree with "Bug" status of this Jira though - migration is working
correctly, attributes have correct values which can be checked in CLI - this is only a
presentation issue.
Can you switch it's type to enhancement please?
On IIOP migration default properties are not persisted
------------------------------------------------------
Key: WFLY-5413
URL:
https://issues.jboss.org/browse/WFLY-5413
Project: WildFly
Issue Type: Bug
Components: IIOP
Affects Versions: 10.0.0.CR1
Reporter: Ondřej Chaloupka
Assignee: Ondřej Chaloupka
If there are some enumeration set in {{jacorb}} subsystem that should be migrate to new
{{iiop}} subsystem with the {{:migrate}} operation then if value of such property matches
the the defaults set for the new {{iiop}} such property with value is not persisted to
XML.
It would be nice if properties would be persisted for user can see what's happened
after migration directly and not being confused that migration forgot for some value. Or
he will need to check what are defaults and if all settings was migrated correctly.
The example of such properties which do not persist because of its default values are
* initializers: security="none"
* security: client-supports="ServerAuth" server-supports="MutualAuth"
* security: client-requires="None" server-requires="None"
* transport-config: detect-misordering="none"
* as-context: auth-method="username_password" required="false"
* sas-context caller-propagation="none"
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)