Ask yourself why sorting a collection of TimeCard objects should need to compare two Consultant objects.
Wouldn't it be more reasonable to expect it to compare two TimeCard objects?
And when it does that, what method of what class would it use?
Henry Wong wrote:
Can you elaborate a bit? What is wrong with having two overloaded constructor -- that aren't chained to each other?
Henry Wong wrote:
Not all constructors can be chained. If you have two completely different ways to construct an instance of the class, then they may have to be completely independent constructors.
Joe Harry wrote:
Did you use the same groupId and artifactId?