KER-280: Cannot getConfigurationXML of Portal Container via jconsole after doing some actions in eXo Platform Problem analysis * For object parameter, the kernel uses reflection to provide all the fields. The kernel assumes that object parameters are only simple Bean Objects with simple fields. However, in case of PLF we have some object parameters whose fields are actually services provided by the ExoContainer. As consequence, the kernel tries to convert it into an object parameter recursively which finally causes a StackOverFlowError.
Fix description * Before converting a field into an object parameter, we first check if the field is not a service provided by the ExoContainer in case we are serializing a configuration to limit the risk.