Igor Akkuratov,

I have several concerns about your patch.

1. I don't understand why setting
IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false + igniteInstanceName is not a
solution to your issue ?
Just put it in the documentation and this should do fine.

2. Removing the classloader id can break the template working in the
container environment, where the instances with the same name are
instantiated using different classloaders.
How is this scenario supposed to work with a single template ?

3. Your patch introduces breaking change. This can be done only in two
steps: release N deprecated the behavior, release N + 1 changes the
behavior, according to the new rules.
But first let's decide if we really need to do any change at all.




<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Без
вирусов. www.avast.ru
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#m_-5956278403710209994_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

пт, 16 апр. 2021 г. в 14:16, Igor Akkuratov <akkura...@mail.com>:

> Is there anybody alive?
>


-- 

Best regards,
Alexei Scherbakov

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Без
вирусов. www.avast.ru
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Reply via email to