>>>
>> Well, this CL is not available for Prelude since deploying of MBeans
>> is not yet supported for Prelude. It will be available for v3 final,
>> though.
> Will the mbean class loader be in the same position in the hierarchy,
> with the public API class loader as its parent?
It will need to be done slightly differently.
> Will the life cycle module class loader exist at all in V3?
The way we do life cycle modules has changed significantly. In v3,
everything is a module with services inside it. So, I am not sure
how we are going to do V2's life cycle modules in v3.
-Kedar