[jboss-as7-dev] Logging Subsystem Changes

[Aleksandar Kostadinov]

Brian Stansberry wrote, On 27.11.2012 16:46 (EEST):
> On 11/27/12 12:13 AM, Stuart Douglas wrote:
>>
>>
>> James Perkins wrote:
>>> Mainly because the logging.properties is overwritten so it would only be
>>> there on the very first boot. After that everything is written to the
>>> server.log. Also resolving determining the path was an issue IIRC.
>>
>> Assuming of course that the first boot succeeds :-) Trying to figure out
>> why your new install won't boot sounds like it might be a problem.
>>
>>>
>>> Note too this is only on the very first boot and a clean install. On the
>>> next boot the JVM parameters and what not will be written out to the
>>> server.log file.
>>
>> So this means that after the first start the logging.properties will be
>> modified? Shouldn't we be trying to ship a logging.properties that
>> corresponds to the default standalone.xml settings? Or does the lack of
>> expressions mean that we now have to write absolute paths to this file?
>>
>
> Expressions should work to the extent they worked in the past. The
> parser hasn't changed -- it can handle expressions.
>
> The problem with expressions in the file is the file is parsed very
> early in the boot, before the host/standalone.xml file is processed and
> even before org.jboss.as.server.Main processes any -D values or -P
> passed on the command line. Basically only system properties set via
> standalone.conf are visible. This has always been a usability issue with
> the boot log -- configuring it requires some black art.
>
> The reason James isn't *writing* expressions back to logging.properties
> is because expressions that resolve properly when placed in the logging
> subsystem in standalone.xml might not resolve properly when placed in
> logging.properties. By the time the logging subsystem is processed, all
> system properties are set.

I think the point here was (at least my point) that the information from 
first boot is lost for automatic deployments. Can't logging.properties 
match default logging subsystem configuration so information from first 
boot is put somewhere (be it boot.log or server.log)?