[jboss-jira] [JBoss JIRA] (AS7-4917) paths need to allow expressions in its 'path' attribute

[Brian Stansberry (JIRA)]

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

Brian Stansberry resolved AS7-4917.
-----------------------------------

    Resolution: Done

    
> paths need to allow expressions in its 'path' attribute
> -------------------------------------------------------
>
>                 Key: AS7-4917
>                 URL: https://issues.jboss.org/browse/AS7-4917
>             Project: Application Server 7
>          Issue Type: Sub-task
>          Components: Logging
>    Affects Versions: 7.1.2.Final (EAP)
>            Reporter: Tom Fonteyne
>            Assignee: Brian Stansberry
>             Fix For: 7.2.0.Alpha1
>
>
> The "paths" section should allow expressions for "path" elements
> Rationale is the fact that customers often want the log files to be send to another directory "outside" of the JBoss directory.
> <periodic-rotating-file-handler name="FILE">
> ...
> <file relative-to="jboss.server.log.dir" path="server.log"/>
> You can change the above and hardcode to : <file path="/logs/jboss/server.log"/>
> but that means that as soon as you have two servers on the same machine, using the same profile, they will write to a single logfile.
> The "file"s "path" attribute does not allow expressions; this RFE is however not for this attribute.
> As relative-to="jboss.server.log.dir" can use self-defined names paths, we looked at the "paths" section.
> <paths>
> <path name="my.log" path="/logs/jboss/${my.system.propery}"/>
> </paths>
> but as it turns out, the "path" attribute of the "path" tag also does not allow expressions, and the above entry fails.
> Hence: please allow the "path" attribute of the "path" tag to allow expressions so that the above "paths" example works.
> Note that we consider this "Major" as customer do/want this functionality often.

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