Most type systems (including Haskell's) can be subverted. Java does catch many common errors, typically of the form "I refaxtored, now this function takes 4 args instead of 3" or "this function returns an X now".

The latter sort are, in my experience, the most common form of type error and catching g them is awesome.

"Expressive" tends towards "complex". I would argue that Java's type system is pretty simple which is a good thing - a pragmatic choice. You sound like you're making "perfect" the enemy of "good"

Lisp is optionally statically-typed. I am not aware of any type error Java can catch at compile time which Lisp cannot catch at compile time.

Now, whether or not a particular implementation does catch it is an entirely different affair.