Unable to set filename for logging file handler in UI about core HOT 7 CLOSED

I just saw that the WildFly CLI command /subsystem=logging/periodic-rotating-file-handler= *:read-resource
returns that:

{
    "outcome" => "success",
    "result" => [
        {
            "address" => [
                ("subsystem" => "logging"),
                ("periodic-rotating-file-handler" => "FILE")
            ],
            "outcome" => "success",
            "result" => {
                "append" => true,
                "autoflush" => true,
                "enabled" => true,
                "encoding" => undefined,
                "file" => {
                    "relative-to" => "jboss.server.log.dir",
                    "path" => "server.log"
                },
                "filter" => undefined,
                "filter-spec" => undefined,
                "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%e%n",
                "level" => "ALL",
                "name" => "FILE",
                "named-formatter" => "PATTERN",
                "suffix" => ".yyyy-MM-dd"
            }
        }
    ]
}

Maybe file showing up as a sub-node is the reason for not being listed below attributes?

from core.

yes, good catch. that's the reason.

currently complex attributes are not supported in the mode based form elements (generated from the management model meta data). but obviously a log handler without the ability to configure the file attribute doesn't make much sense :)

I'll revisit this next week.

from core.

@hpehl maybe we should make complex (nested) attributes addressable so that their contents can be edited like regular resources? The downside would be that any complex attribute would have to be moved to a custom form (and tab)

i.e.

/subsystem=logging/periodic-rotating-file-handler#file

from core.

@sebasbaumh btw, you try the latest WF 10 Beta1 console. It's basically the same, but much improved. Any feedback is greatly appreciated. See http://blog.arungupta.me/wildfly-admin-console-updated-feedback-requested/

from core.

Thanks for looking at that issue.
I'll try the new beta console in the next days with the EAR, that I am building for my company.
The WildFly console is a great tool to allow administration of the server even for people without a deep knowledge of the XML configuration.

Maybe you can just show the contents of the complex type in another attribute form.
Or like in a small tree (inline), which can be expanded to configure the contents as an intended attribute list?

from core.

https://issues.jboss.org/browse/HAL-814

from core.

Please track the above issue. I am going to close this one.

from core.