[jboss-jira] [JBoss JIRA] (WFLY-5413) On IIOP migration default properties are not persisted

Tomasz Adamski (JIRA) issues at jboss.org
Tue Jul 11 17:26:00 EDT 2017


     [ https://issues.jboss.org/browse/WFLY-5413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomasz Adamski closed WFLY-5413.
--------------------------------
    Fix Version/s: 11.0.0.CR1
       Resolution: Done


In current upstream default properties are also persisted.

> On IIOP migration default properties are not persisted
> ------------------------------------------------------
>
>                 Key: WFLY-5413
>                 URL: https://issues.jboss.org/browse/WFLY-5413
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: IIOP
>    Affects Versions: 10.0.0.CR1
>            Reporter: Ondra Chaloupka
>            Assignee: Tomasz Adamski
>             Fix For: 11.0.0.CR1
>
>
> 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
(v7.2.3#72005)


More information about the jboss-jira mailing list