[jboss-jira] [JBoss JIRA] (WFCORE-637) /subsystem=logging/log-file resource cannot cope with an expression in the path

[James Perkins (JIRA)]

    [ https://issues.jboss.org/browse/WFCORE-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062974#comment-13062974 ] 

James Perkins commented on WFCORE-637:
--------------------------------------

I'm changing this to an optional enhancement. We already have a limitation that the file-handlers must be in the {{jboss.server.log.dir}} directory. Having a limitation of not being able to resolve expressions in the path name seems okay to me. I can understand the use-case where a user would like to use an expression for the path. 

The issue is there's no good way to dynamically resolve an expression in a resource. This would lead to some sort of collection which stores the resolved path names. Which could only be done in the {{RUNTIME}} stage and would lead to files not being able to be listed or read in the something like admin-only mode.

For now we just need to keep things as they are and consider an enhancement to this limitation in the future.

> /subsystem=logging/log-file resource cannot cope with an expression in the path
> -------------------------------------------------------------------------------
>
>                 Key: WFCORE-637
>                 URL: https://issues.jboss.org/browse/WFCORE-637
>             Project: WildFly Core
>          Issue Type: Enhancement
>          Components: Logging
>    Affects Versions: 1.0.0.Beta3
>            Reporter: Ivo Studensky
>            Assignee: James Perkins
>            Priority: Optional
>
> In log subsystem, nested expression can be used for path.
> {noformat}
> "path" => {
>                         "type" => STRING,
>                         "description" => "The filesystem path.",
>                         "expressions-allowed" => true,
>                         "nillable" => false,
>                         "min-length" => 1L,
>                         "max-length" => 2147483647L
>                     }
> {noformat}
> so if I use following log configuration :
> {noformat}
> <periodic-rotating-file-handler name="FILE" autoflush="true">
>                 <formatter>
>                     <named-formatter name="PATTERN"/>
>                 </formatter>
> 				<file relative-to="jboss.server.log.dir" path="${jboss.server.name}.log"/>
>                 <suffix value=".yyyy-MM-dd"/>
>                 <append value="true"/>
> {noformat}
> server log name will be HOST_NAME.log and there is no problems to write.
> However, there is no log-file resource for it. This also leads into an issue that it cannot be displayed in Admin console Log Viewer menu. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)