[
https://issues.apache.org/jira/browse/ARTEMIS-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16306269#comment-16306269
]
ASF GitHub Bot commented on ARTEMIS-1575:
-----------------------------------------
Github user michaelandrepearce commented on a diff in the pull request:
https://github.com/apache/activemq-artemis/pull/1743#discussion_r159060268
--- Diff:
artemis-server/src/main/resources/schema/artemis-configuration.xsd ---
@@ -934,6 +934,26 @@
a broker plugin
</xsd:documentation>
</xsd:annotation>
+ <xsd:sequence>
--- End diff --
Is it worth instead of re-defineing what a property type is, re-naming and
re-using the transformerProperty complex type which this is identical to?
also could the same file
/artemis-tools/src/test/resources/artemis-configuration.xsd be updated also.
> configuring custom brokerPlugins within the broker.xml
> ------------------------------------------------------
>
> Key: ARTEMIS-1575
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1575
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 2.4.0
> Reporter: Pat Fox
> Priority: Minor
>
> It would be nice to allow users to users configure their custom plugins
> within the broker.xml, using key value properties like below:
> {code}
> <broker-plugins>
> <broker-plugin class-name="some.custom.Plugin">
> <plugin-property key="key1" value="value1" />
> <plugin-property key="key2" value="value2" />
> <plugin-property key="key3" value="value3" />
> </broker-plugin>
> </broker-plugins>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
