[jboss-jira] [JBoss JIRA] (WFLY-5455) [Migration operation] [Web to Undertow] migration of access-log prefix attribute doesn't take into account default value resulting in incosistent result.

[Radim Hatlapatka (JIRA)]

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

Radim Hatlapatka updated WFLY-5455:
-----------------------------------
    Affects Version/s: 10.0.0.CR2


> [Migration operation] [Web to Undertow] migration of access-log prefix attribute doesn't take into account default value resulting in incosistent result.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-5455
>                 URL: https://issues.jboss.org/browse/WFLY-5455
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (Undertow)
>    Affects Versions: 10.0.0.CR2
>            Reporter: Radim Hatlapatka
>            Assignee: Stuart Douglas
>            Priority: Optional
>
> Access log prefix in web subsystem is by default {{access-log.}}, in Undertow subsystem it is {{access-log}}. Note the difference, there is "." at the end in case of Web.
> There is inconsistency of migrate operation when migrating {{prefix}} attribute. When {{prefix}} is not explicitly defined in Web (=> default is used => {{access-log.}}, note the dot at the end. It is migrated to default Undertow prefix, which is {{access-log}} (missing "." at the end). 
> In case of having explicitely set {{prefix="access-log."}}, it is the same value as the default value in Web and in this case this is migrated to {{access-log.}} (the "." is there).
> => two equivalent Web subsystem configuration of access-log result in two different configurations in Undertow, which is not expected behaviour.
> As this impacts only access-log naming, I am considering this only as minor issue.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)