I didn't get any response in #wildfly, but I tested this and I found it to be true:

03:23:11 PM) mazz: I need a sanity check please. I'm trying to run unit tests on my module subsystem (via my subclass of org.jboss.as.subsystem.test.AbstractSubsystemBaseTest). My test DID work on WF8.2 but FAIL when I move to WF9 CR2.
(03:23:11 PM) mazz: The error is : 
(03:23:11 PM) mazz:     failure description: "WFLYCTL0201: Unknown attribute 'org'"
(03:23:11 PM) mazz: in my custom subsystem, I have several attributes of the form "org.abc.xyz" such as:
(03:23:11 PM) mazz:     <element org.hawkular.package.name.foo="test1"  org.hawkular.another.package.blah-blah="test2" />
(03:23:44 PM) mazz: could it be possible that attribute names can no longer have "." in their names?
(03:24:11 PM) mazz: I have no attributes called "org" but plenty that look like "org.some.name.here"
(03:47:24 PM) mazz: uh-oh. Yeah, I thikn that's a problem
(03:47:48 PM) mazz: in WildFly 9 CR2, it is no longer possible to have a dot (".") in attribute names. 
(03:47:50 PM) mazz: This makes me sad
(03:48:06 PM) mazz: this was possible in WildFly 8.2.Final
(03:48:36 PM) mazz: I just changed all my "." to "-" in my custom module subsystem extension (in the java code and the .xml) and now my tests pass
(03:50:06 PM) mazz: I don't know if that is also true for element names.
(03:50:25 PM) mazz: I have "org.abc.xyz" element names as well. but the error message I got just mentioned attribute name

I suppose we could change these names so the "." is replaced with "-" (they are also sysprop names that are used to replace ${key} tokens in bus config files, so i used the standard "." notation for these names).

What should we do? Ask WF to fix this (it probably is a bug - I doubt they meant to make that change) or just deal with it and workaround by changing our attribute names?
_______________________________________________
hawkular-dev mailing list
hawkular-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev