Java erasure with generic overloading (not overriding)

Question

I have FinanceRequests and CommisionTransactions in my domain. If I have a list of FinanceRequests each FinanceRequest could contain multiple CommisionTransactions that need

Answer 1

I think your best option is to simply name the method differently.

public void clawBackFinReqs(Collection financeRequestList) {

}

public void clawBackComTrans(Collection commissionTrnsList) {

}

In fact, it's not too bad, since you don't get anything extra out of having the same name on them.

Keep in mind, that the JVM will not decide which method to call at runtime. As opposed to virtual methods / method overriding resolution of overloaded methods are done at compile time. The Java Tutorials on method overloading even points out that "Overloaded methods should be used sparingly...".