Ales Justin wrote:
Better question is how you're getting past this mechanism in the first place,
by being able to have an ObjectName named bean which is not canonical.
I'm not sure I understood that question. Is there a constraint in MC, that MC bean names which might be of the form ObjectName, should be canonical? More specifically, can't I have a MC bean named:
blah.blah:p=q,a=b
and just be treated as a plain string name, instead of ObjectName?