Type: New Feature
Affects Version/s: None
Fix Version/s: 1.4
The schemas I deal with make heavy use of xsd:key on what are intended as sequences of uniquely identifiable entries; a.k.a, maps. Take for example:
The ejb-name element contains the name of an enterprise
bean. The name must be unique within the ejb-jar file.
The attached patch allows someone to flag a field of the java class as being a key and allows that object to be added to a map using that key value. Such as:
I've taken some time and split the patches in two as it may be easier to deal with the addition in logical parts.