[
https://issues.apache.org/jira/browse/ARTEMIS-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Domenico Francesco Bruscino updated ARTEMIS-4818:
-------------------------------------------------
Description: The broker support loading multiple broker plugins from the
broker properties only if they expose a getter/setter for the property name.
Could you support loading multiple broker plugins without a getter/setter for
the property name? (was: The broker support loading multiple broker plugins
from the broker properties only if they have a different class and expose a
getter/setter for the property name. Could you improve the broker property
syntax to define the class instance name in the key optionally? In this way,
users could add multiple instances of the same broker plugin even if it has no
getter/setter for the property name, i.e.
{code}
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-0.class".init=LOG_ALL_EVENTS=false
brokerPlugins."org.apache.activemq.artemis.core.server.plugin.impl.LoggingActiveMQServerPlugin#my-instance-1.class".init=LOG_ALL_EVENTS=true
{code}
)
> Improve support for multiple broker plugins from broker properties
> ------------------------------------------------------------------
>
> Key: ARTEMIS-4818
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4818
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Domenico Francesco Bruscino
> Assignee: Domenico Francesco Bruscino
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The broker support loading multiple broker plugins from the broker properties
> only if they expose a getter/setter for the property name. Could you support
> loading multiple broker plugins without a getter/setter for the property name?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
