Can I apply Hibernate3, Annotations to provide an ORM solution for
CaveatEmptor case?

Another question is in terms of Hiberate Annotations, currently in EJB3,
it provides only Collection and Set property for an object, but in reality,
it is very popularan object has List or Map property, how to deal with
the issue?

Noddy

Sure, you can try to map it using EJB3/Hibernate annotations. But, this is alpha quality software and we are mostly interested in constructive feedback if you try. The discussion about this should happen in Hibernate3 forum, not here.

Dito, AFAIK this is a current topic of discussion in the EJB3 EG and I hope (and expect) it to be covered soon.

If not coevered by the spec, Map and List will be covered by an hibernate extension.
Note that it is not common to use a List with it's correct semantic and even more rare to have it on a plain entity relational model.