[jboss-jira] [JBoss JIRA] (AS7-6412) Transformation logging issues

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar commented on AS7-6412:
----------------------------------

that "subsystem 'infinispan' model version 'null'" is problem with tests not with actual runtime, but need to be addressed in any case.
                
> Transformation logging issues
> -----------------------------
>
>                 Key: AS7-6412
>                 URL: https://issues.jboss.org/browse/AS7-6412
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: 7.2.0.Alpha1
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira