My point is that from the application developer point of view, the object does not exist. The fact that the class is wrong or the id is wrong is an implementation detail: you don't have an object from this class for this id, the fact that there is inheritance and so on shouldn't be seen from the session.get perspective IMHO.

So, I surprisingly vote for consistently returning null.