The Javelin is the only one I know of.
However: Java and most Basics both suffer the same problem on mcus. They are compiled to an interim 'byte code' which is then interpreted. So they both have some program memory (either on board or in a seperate EEPROM) that is reserved for the runtime interpreter (ie JRE). Nothing wrong with that - but it does add cost to the board.
So you would never use Java for a slave device (such as a motor controller or sensor) as the cost of the extra ROM for each device would be substantial. But for the main controller (ie you only have one of them) then its not too much of a problem.
The benefit with this 'byte code' is that your own application compiles down to a small size - ie you get more bangs for your buck.
But if you are an ardent Java developer then also be aware that these chips only support a very small subset of the vast Java API.
The only other consideration I would give (as someone who uses Java as my main job!) is that a runtime interpreter is never quite as fast/efficient as a natively compiled program such as C.
Given that the mcu implementations of Java are somewhat simplistic then I would recommend that you just stick with C. After all C is like Java without all the object orientated stuff. If you still want object orientation then you can use C++. As a Java developer you will learn it quickly and learn to hate all those stupid things that are different from Java!!
Just be grateful that Microsoft were kicked off the Java committee !!