> Here is the crux of my point. IMHO, the javadoc/specs should capture all > requirements. The RI is not to be used as the final definition > of the spec. > Am I wrong? >
The TCK is the final arbiter of the spec. In this case, there is an ambiguity in the spec - the RI does one thing which we think is weird. Provided what we implement conforms to the spec and passes the TCK then we do not need to duplicate the behaviour of the RI. Now all we need is a TCK :-) -- Jeremy
