The "deployment" you are talking about doesn't go through the deployers at all,
so there is no POST_CLASSLOADER or REAL.
It is a part of the bootstrap "before" the deployers exist.
For something that does go through the deployers, you shouldn't use the MC "classloader"
element, you should use a META-INF/jboss-classloading.xml that the deployers know about.
Emanuel reported that packaging the -jboss-beans.xml in the jar and deploying the jar instead of a bare jboss-beans.xml solved the problem. I figured it should work packaged as a sar as well, so he's going to try that.. That should suffice until AS 6 when AIUI there should be no need for the binding service to deploy before deployers.
It should really just be a bindingservice.beans with a META-INF/jboss-beans.xml since we don't deploy any services, but I suppose it does not really matter.
Note that I have broken up the ServiceBindingManagedObjectsTestCase tests into:
org.jboss.test.profileservice.test.ServiceBindingManagedObjectsTestCase - basic managed object testing
org.jboss.test.profileservice.override.test.ServiceBindingManagedObjectsTestCase - creates and updates binding sets, standard bindings
org.jboss.test.profileservice.override.restart.test.ServiceBindingManagedObjectsTestCase - validates the the override changes are persisted across server restarts.