Loggers can be set to invalid log level

In CLI, the logging subystem lists the JUL logging levels as the valid choices. However, by default the loggers in standalone.xml and domain.xml are using the Log4J levels. This inconsistency allows loggers to have what appear to be invalid logging levels.

This causes a problem in the console because we fill the "levels" drop-down with the valid choices as read from dmr. Then when we try to set the value to the "invalid" level, nothing will appear.

Should it be considered an error if levels in standalone.xml are inconsistent with the valid levels in the management layer?