[jboss-jira] [JBoss JIRA] (WFLY-1333) access log "prefix" configuration required

[Remy Maucherat (JIRA)]

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

Remy Maucherat resolved WFLY-1333.
----------------------------------

    Fix Version/s: 8.0.0.Alpha1
       Resolution: Done

    
> access log "prefix" configuration required
> ------------------------------------------
>
>                 Key: WFLY-1333
>                 URL: https://issues.jboss.org/browse/WFLY-1333
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web (JBoss Web)
>         Environment: Windows 7 64bit, JBoss AS 7.2.0
>            Reporter: Bart Van Dosselaer
>            Assignee: Remy Maucherat
>            Priority: Minor
>              Labels: access-log, jboss, web
>             Fix For: 8.0.0.Alpha1
>
>
> The virtual server access-log configuration (subsystem xmlns="urn:jboss:domain:web:1.4") requires that the prefix attribute is present.
> If the configuration is like this:
>                 <access-log pattern="%t-[%a] %s %r@%p %b bytes %Ts"/>
> ... the server creates a file named "false2013-05-13"
> Only when the attribute prefix="access_log." is added to the configuration, is the file nicely created like "access_log.2013-05-13".
> According to the jboss-as-web_1_4.xsd file it shouldn't be required to provide the prefix attribute, as there is a default value already supplied:
>    <xs:complexType name="http-access-logType">
>       <xs:sequence>
>          <xs:element name="directory" type="directoryType" />
>       </xs:sequence>
>       <xs:attribute name="pattern" default="common" />
>       <xs:attribute name="resolve-hosts" default="false" type="xs:boolean" />
>       <xs:attribute name="extended" default="false" type="xs:boolean" />
>       <xs:attribute name="prefix" default="access_log." />
>       <xs:attribute name="rotate" default="true" type="xs:boolean" />
>    </xs:complexType>

--
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