Uses of Package
org.apache.openmeetings.db.entity.user
Packages that use org.apache.openmeetings.db.entity.user
Package
Description
-
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.bind.adapterClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.dao.file
-
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.dao.userClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.dto.userClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.entity.basicClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.entity.calendarClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.entity.room
-
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.entity.serverClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.entity.userClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.managerClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.mapper
-
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.utilClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment -
Classes in org.apache.openmeetings.db.entity.user used by org.apache.openmeetings.db.util.wsClassDescriptionEntity to store user data, password field is
FetchType.LAZY
, so that is why there is an extra udpate statement at this moment