Issue 29 in stajistics: Determine and enforce valid StatsKey names, attribute names, and values
staji...@googlecode.com
Owner: troy.kin...@gmail.com
Labels: Type-Defect Priority-Medium Milestone-Release0.3 Component-Core
Usability
New issue 29 by troy.kin...@gmail.com: Determine and enforce valid StatsKey
names, attribute names, and values
http://code.google.com/p/stajistics/issues/detail?id=29
Due to the fact that StatsKey names, attribute names, and values are
inserted into JMX ObjectNames as part of statistics management, there will
be restrictions on the characters/sequences that can appear in these fields.
Determine exactly what these restrictions are, and ensure invalid fields
are either rejected or escaped. Ensure javadoc and external documentation
exists to explain both rejections and escapes. Where escapes are necessary,
ensure the documentation explain clearly how a JMX ObjectName must be
constructed to address a particular StatsKey.
Create unit tests to validate enforced rejections and escapes.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
staji...@googlecode.com
Status: WontFix
Comment #1 on issue 29 by troy.kin...@gmail.com: Determine and enforce
valid StatsKey names, attribute names, and values
http://code.google.com/p/stajistics/issues/detail?id=29
With proper ObjectName quoting, StatsKeys should not have any invalid
characters, or rather "any" character could be escaped.
Closing.