On Jul 10, 2008, at 2:24 PM, Chris Hostetter wrote:
if you could submit a test case that
reproduces this using a trivial subclass (just return the orriginal
String
as the Comparable) that can help us verify the bug and the fix.
See my e-mail dated July 3, 2008.
Assuming i'm right, I don'treally have any good work arround
suggestion
for you beyond overriding newComparator() in your SortComparator
subclass
to explicitly test for null yourself.
And what do I do if it is null?
- Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]