Kind of a grab bag dumping ground for issues I've noted with the new transformation logging stuff.

Here's an example message I saw posted in an unrelated discussion:

subsystem 'infinispan' model version 'null' – attributes null JBAS014886: are not understood in that model version and this resource will need to be ignored on that host.

I'm not sure about the model version 'null' bit. Maybe that was a dev error, or perhaps a bug. If there are valid cases for 'null' there the logic needs to account for that and output something nicer.

The "attributes null" bit: we need to deal with cases where no attribute names are passed in. (There are cases like this.) If that happens the entire "attributes xxx" bit should be skipped.

The message param passed in is going to be an i18n message, so the message structure should account for that and not try to assume some particular English grammar. For example

Subsystem 'infinispan' model version '1.2.3' – attribute(s) abc, def had the following problem: JBAS014886: Attributes are not understood in that model version and this resource will need to be ignored on that host.