DbEntityManagermethods, they are examined and parsed and these results are stored internally in
DbEntityManager. This kind of registration is called types registration since only class information is registered. This means that more then one entity types may be mapped to single database table. In other words, this is one way mapping:
DbEntityManagerbefore the usage. Entity registration supersede the type registration: types and tables now becomes mapped in both ways:
DbOomQuerywill throw exception if that happens.
AutomagicDbOomConfigurator. It scans the class path and jar files (or part of it, as specified by user) and finds all classes annotated with
@DbTable. No class is loaded in class loader unless it contains correct bytecode.
AutomagicDbOomConfiguratoroffers both way of registration.
DbOomQueryexamples, each method accepts explicit list of (entity) classes to which the result set will be mapped. Now it is possible to omit the list and let
DbOomQueryresolve classes by itself: