MXBean serialization of Maps needs to be fixed for complex keys #105
MXBeans convert complex beans in OpenType. So Maps (as in our case) are converted to TabularType data with two elements: key and value with the appropriate types. If these are used directly for serialization for simple maps (i.e. with string keys), plain JSON serialization of the generated TabularData is quite ugly, so Jolokia does its best to convert it back to a simple map with the key being a JSON key.
For complex keys which are not simply translatable into strings, Jolokia should fallback to the regular TabularData serialization for everything without a simple String representation (which is more or less exactly the same as you suggest above).
See #102 for a concrete use case.
The text was updated successfully, but these errors were encountered: