-
Enhancement
-
Resolution: Fixed
-
P4
-
1.2.1
-
b34
-
x86
-
windows_xp
-
Verified
A DESCRIPTION OF THE REQUEST :
TabularDataSupport uses an internal HashMap for keeping CompositeData rows. As a result, row values are sorted by hash codes. However, in some case, it's critical that TabularDataSupport provides a view of rows in the actual insertion order.
I propose adding a new constructor accepting a helper object which can figure out how values should be presented.
JUSTIFICATION :
For example, when displaying interceptor details for a given managed endpoint we need to see them in the correct order. Displaying then in the random order will mislead the operator.
CUSTOMER SUBMITTED WORKAROUND :
One workaround is to pass a CompositeData order item with each row which would let a customized client to sort rows properly. However this would require us shipping client-side jars for all popular consoles which may not be possible
Anotehr one is to format a row in a String and pass an array of rows but this is much less elegant and may not be ideal either
TabularDataSupport uses an internal HashMap for keeping CompositeData rows. As a result, row values are sorted by hash codes. However, in some case, it's critical that TabularDataSupport provides a view of rows in the actual insertion order.
I propose adding a new constructor accepting a helper object which can figure out how values should be presented.
JUSTIFICATION :
For example, when displaying interceptor details for a given managed endpoint we need to see them in the correct order. Displaying then in the random order will mislead the operator.
CUSTOMER SUBMITTED WORKAROUND :
One workaround is to pass a CompositeData order item with each row which would let a customized client to sort rows properly. However this would require us shipping client-side jars for all popular consoles which may not be possible
Anotehr one is to format a row in a String and pass an array of rows but this is much less elegant and may not be ideal either
- relates to
-
JDK-8345049 Remove the jmx.tabular.data.hash.map compatibility property
-
- Resolved
-