Cheers. Yes, I think setting the compliance level to 1.6 in eclipse has fixed it. The error has gone away on the Java6 I tried it on. Please let me know if I am mistaken.