Based on my recent findings this seems to be only partially true.If I use the actual name of ear file as ear-level domain name then it seems to be true.
If I use something else (in ear/META-INF/jboss-classloading.xml) then it looks like war classloaders don't reflect this change and still work with ear file name so I have to setup their own jboss-classloading.xml
I think the war classloaders should pick up the change done on ear level by default but they seem like they don't.
Ah, I think you're right.
It's the WebClassLoaderDeployer that messes up things;
it's missing some more logic to address the new jboss-cl-domain.xml notion.
I'll fix this.
Too bad we didn't find this one before.