Uses of Package
com.licensespring

Packages that use com.licensespring

Package	Description
com.licensespring	Package com.licensespring contains the main public classes of interest when implementing the client SDKs (license-client, floating-client).
com.licensespring.api	com.licensespring.api package contains Core APIs, API builders, Error decoders, Interceptors and used in all SDKs e.g.
com.licensespring.dto	com.licensespring.dto contains all data transfer objects used in API requests and API responses.
com.licensespring.identity	Package com.licensespring.identity.identity contains various identity providers that are used depending on the context in which the application is launched.

Classes in com.licensespring used by com.licensespring

Class and Description
BaseConfiguration Base configuration class - immutable - can be built using the inner Builder class.
BaseConfiguration.ConfigurationBuilder Builder for BaseConfiguration.
IdentityProvider IdentityProvider interface should be used when implementing own -custom hardware key generation algorithm The default implementation provided uses information from the motherboard, the cpu and disk to generate a unique hardware id - representing a single device.
LicenseData License data is the main license model returned by LS servers.
LicenseData.LicenseDataBuilder

Classes in com.licensespring used by com.licensespring.api

Class and Description
BaseConfiguration Base configuration class - immutable - can be built using the inner Builder class.
LicenseData License data is the main license model returned by LS servers.

Classes in com.licensespring used by com.licensespring.dto

Class and Description
LicenseData License data is the main license model returned by LS servers.

Classes in com.licensespring used by com.licensespring.identity

Class and Description
BaseConfiguration Base configuration class - immutable - can be built using the inner Builder class.
IdentityProvider IdentityProvider interface should be used when implementing own -custom hardware key generation algorithm The default implementation provided uses information from the motherboard, the cpu and disk to generate a unique hardware id - representing a single device.