A javax.management.openmbean.CompositeType defines a list of items, where each item has a name and a type.  The specification currently disallows a CompositeType with an empty list of items.  With the implementation of 5072004, which allows a CompositeData to contain additional items and still be compatible with a CompositeType, it is now meaningful to have an empty CompositeType.  This simply means that the corresponding CompositeData instances will have only additional items, and no fixed items.  In particular this can be used to handle "any"-type values in MXBeans.
Posted Date : 2006-03-29 15:40:35.0

N/A

It is unlikely that any existing code would be broken if we simply removed the clause "should contain at least one element" from the @param itemNames of the CompositeType constructor and changed the implementation accordingly.  (The implementation currently reads this "should" as a "must".)
Posted Date : 2006-03-29 15:40:36.0

This was fixed as part of the fix for 5072004.
Posted Date : 2006-11-14 16:21:44.0

The preceding comment is incorrect.  5072004 was implemented in Java SE 6 but the implementation of this RFE was only integrated in b30 of JDK 7.  Because this spec change was not in fact part of the 5072004 spec change, a new CCC request is needed to cover this change.
Posted Date : 2008-07-08 15:11:13.0