Hi,

can you please explain why this issue was set as Rejected, Steve Ebersole?

It seems like quite a valid one: why couldn't it be possible that Hibernate doesn't go to database every time a non-existing object is repeatedly searched (session.get(id))? In other words, why not "cache null values" at the 1st level cache? I realize this would perhaps incur some additional overhead, but what do the Hibernate authors think?