[haploid]

No, I meant duck-typed. A lot of languages popular with the HN ooh-new-shiney-language-of-the-month crowd use duck typing.

http://en.wikipedia.org/wiki/Duck_typing

Also, Java is not pure OOP in any real sense of the word. It still has primitives, and plenty of other reasons.

All I was saying that if you're accustomed to statically-typed languages with pointer/reference passing semantics and limited FP usage, the manner in which you think is likely to mesh better with Java. And in that sense, you'd probably be more productive out of the gate with it than with Ruby.

Or maybe not - learning about servlet containers and how Wicket overlays it, and Wicket's own component-oriented stateful approach could be fairly steep.

This is not an easy question to answer, and is almost entirely dependent on your experience and disposition.