Component Manager Update Stage 1: Restore standard context ClassLoader environment within Sakai components

On the basis that these have been untouched in some years and the asignee is no longer involved in Sakai, am marking them closed

[Bulk Comment] This issue has a Fix Version set, however, it is an Unresolved issue. The Fix Version is being re-set to Unknown. Please use the Target Version field to indicate in for version of Sakai you plan to address this issue. Thank you.

OK... implementation fixed as of 38541 to implement "Bean demotion" as part of what you observe are your desired semantics <alias> is now the only remaining deficit

Changing a test assertion in order to get the test to pass is generally a clue that you've broken the desired behavior.... Obviously, we still have some work ahead of us if we're to coordinate the goals of my branch and the goals of your branch.

As of rev 38537 this branch now includes the functions of Ray's branch, with working integration tests.
One test required to be modified - testComponent.mapOverride now resolve to the local version of the util:map rather than the shared one - this is in agreement with standard Spring semantics on hierarchical contexts. The changed lines in the integration test now read:

// ** AMB Changed test - semantics are not as originally designed. Local references
//must remain local
Assert.assertTrue(testComponent.getMapOverride1().size() == 2);
Assert.assertTrue(testComponent.getMapOverride1().get("key1").equals("default1"));

The <alias> test has been commented out pending investigation of what the intended Spring behaviour is meant to be.