New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MXBean serialization of Maps needs to be fixed for complex keys #105

Closed
rhuss opened this Issue May 3, 2013 · 1 comment

Comments

Projects
None yet
1 participant
@rhuss
Owner

rhuss commented May 3, 2013

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.

rhuss added a commit that referenced this issue May 5, 2013

rhuss added a commit that referenced this issue May 10, 2013

@rhuss

This comment has been minimized.

Owner

rhuss commented May 29, 2013

Fixed in 1.1.2

@rhuss rhuss closed this May 29, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment