Uses of Class
jakarta.interceptor.InterceptorBinding

Packages that use InterceptorBinding

Package	Description
jakarta.enterprise.context.control
jakarta.security.enterprise.authentication.mechanism.http	The HTTP authentication mechanism API package.
jakarta.transaction	Provides the API that defines the contract between the transaction manager and the various parties involved in a distributed transaction namely : resource manager, application, and application server.

Uses of InterceptorBinding in jakarta.enterprise.context.control

Classes in jakarta.enterprise.context.control with annotations of type InterceptorBinding

Modifier and Type	Class and Description
interface	ActivateRequestContext The container provides a built in interceptor that may be used to annotate classes and methods to indicate that a request context should be activated when this method is invoked.

Uses of InterceptorBinding in jakarta.security.enterprise.authentication.mechanism.http

Classes in jakarta.security.enterprise.authentication.mechanism.http with annotations of type InterceptorBinding

Modifier and Type	Class and Description
interface	AutoApplySession The AutoApplySession annotation provides an application the ability to declaratively designate that an authentication mechanism uses the jakarta.servlet.http.registerSession and auto applies this for every request.
interface	LoginToContinue The LoginToContinue annotation provides an application the ability to declaratively add login to continue functionality to an authentication mechanism.
interface	RememberMe The RememberMe annotation provides an application the ability to declaratively designate that an authentication mechanism effectively "remembers" the authentication and auto applies this with every request.

Uses of InterceptorBinding in jakarta.transaction

Classes in jakarta.transaction with annotations of type InterceptorBinding

Modifier and Type	Class and Description
interface	Transactional The jakarta.transaction.Transactional annotation provides the application the ability to declaratively control transaction boundaries on CDI managed beans, as well as classes defined as managed beans by the Jakarta EE specification, at both the class and method level where method level annotations override those at the class level.