JMX: Quote object name values if not identifiers
https://www.oracle.com/technetwork/java/javase/tech/best-practices-jsp-136021.html The set of characters in a value is also limited. If special characters may occur, it is recommended that the value be quoted, using ObjectName.quote. If the value for a given key is sometimes quoted, then it should always be quoted. By default, if a value is a string (rather than a number, say), then it should be quoted unless you are sure that it will never contain special characters. Practically, some special characters are allowed, but we will standardize on allowed characters in java identifiers. In 5.0.x, this is enabled using `spring.integration.properties`.
This commit is contained in:
committed by
Artem Bilan
parent
7403e36c1e
commit
c111e1be6a
@@ -301,6 +301,10 @@ NOTE: The default naming strategy is a http://docs.spring.io/spring/docs/current
|
||||
The exporter propagates the `default-domain` to that object to allow it to generate a fallback object name if parsing of the bean key fails.
|
||||
If your custom naming strategy is a `MetadataNamingStrategy` (or subclass), the exporter will *not* propagate the `default-domain`; you will need to configure it on your strategy bean.
|
||||
|
||||
Starting with version 5.0.9; any bean names (represented by the `name` key in the object name) can be quoted if they contain any characters that are not allowed in a Java identifier (or period `.`).
|
||||
This requires setting `spring.integration.jmx.quote.names=true` in a `META-INF/spring.integration.properties` file on the class path.
|
||||
In 5.1 it will not be configurable.
|
||||
|
||||
[[jmx-42-improvements]]
|
||||
===== JMX Improvements
|
||||
|
||||
|
||||
Reference in New Issue
Block a user