Uses of Class
com.neurosys.security.auth.domain.basic.AbstractUser

Packages that use AbstractUser

Package	Description
com.neurosys.ecom.users.domain
com.neurosys.modules.etl
com.neurosys.security.auth.domain.basic
com.neurosys.user.domain

Uses of AbstractUser in com.neurosys.ecom.users.domain

Subclasses of AbstractUser in com.neurosys.ecom.users.domain

Modifier and Type	Class and Description
class	GenericEcomUser
class	GuestUser Guest Users Only
class	RegisteredUser<T extends RegisteredUser> Registered Users Only

Uses of AbstractUser in com.neurosys.modules.etl

Classes in com.neurosys.modules.etl with type parameters of type AbstractUser

Modifier and Type	Class and Description
class	UserToJson<U extends AbstractUser> Marshal User to JSON TODO: Add unit test case

Uses of AbstractUser in com.neurosys.security.auth.domain.basic

Subclasses of AbstractUser in com.neurosys.security.auth.domain.basic

Modifier and Type	Class and Description
class	BasicUser<T extends BasicUser> Simply Extend and use JPA annotations over extended class like:

Uses of AbstractUser in com.neurosys.user.domain

Subclasses of AbstractUser in com.neurosys.user.domain

Modifier and Type

Class and Description

class

AdminUser To distinguish an Admin User. An AdminUser is not an Entity, because any user can be translated into an AdminUser by proxying a real User instance. This is done to ensure A User logged in as a user (while testing say) can transcend into an Admin user in an Admin session, it also prevents any chance of User beans getting access to admin in multiple Login scenarios, where Users may also have logins and authorizations.