All Classes and Interfaces
Class
Description
Deployment processor that builds bean archives and attaches them to the deployment
Determines the set of bean defining annotations as defined by the CDI specification and attaches them under
WeldAttachments.BEAN_DEFINING_ANNOTATIONS.Implementation of
BeanDeploymentArchive.A collection of Bean Deployment archives that share similar bean visibility.
Service that provides access to the BeanManger for a (sub)deployment
Deployment processor that finds beans.xml files and attaches the information to the deployment
Marker for deployments that have CDI annotations present
CdiAnnotationProcessor class.
Class that stores the
DotNames of CDI annotations.Processor that registers a CDI portable extension for EAR deployments, which adds support for EE facilities, to CDI app context lifecycle event handlers.
Maintains information about an explicit bean archive
Information about explicit CDI bean archives
Deployment processor that builds bean archives from external deployments.
Utilities for working with Jandex indices.
Utility class for working with Jakarta Contexts and Dependency Injection InjectionTargets
Interceptor that creates the CDI interceptors and attaches them to the component
Singleton Provider that uses the TCCL to figure out the current application.
Fork of
BeansXmlParser to support standard WildFly deployment descriptor expression resolution.ProxyServices implementation that delegates to the module class loader if the bean class loader cannot be determinedAdds binder service dependencies for any
Resource lookups within java:jboss namespace that are processed by Weld.Processes deployment descriptor env-entry configurations looking for cases where an injection target
is specified and the env-entry-type is one of the 'Simple Environment Entry' Java types listed in Section 5.4
of the Jakarta EE 9.1 Platform specification.
Service that manages the weld
SingletonProviderVarious utilities for working with WildFly APIs
Deployment processor that integrates weld into the web tier
AttachmentKeys for weld attachmentsDeploymentUnitProcessor that binds the bean manager to JNDIProvides the initial bootstrap of the Weld container.
The implementation of WeldCapability.
Deployment unit processor that add the
WeldManagedReferenceFactory instantiator
to components that are part of a bean archive.Interceptor that attaches all the nessesary information for weld injection to the interceptor context
Merges the per-deployment configuration defined in
jboss-all.xml with the global configuration and attaches the result under
WeldConfiguration.ATTACHMENT_KEY.Initiates component construction.
Sets up the session, request and conversation contexts for a weld deployment
Deployment processor which adds a module dependencies for modules needed for weld deployments.
Abstract implementation of
CDI11Deployment.A processor which takes care of after boot cleanup for Weld.
Marker for top level deployments that contain a beans.xml file
Deployment processor that installs the weld services and all other required services
Implementation of Weld's
EEModuleDescriptorWeld's ExecutorServices implementation.
Domain extension used to initialize the weld subsystem.
Deployment processor that finds implicit bean archives (as defined by the CDI spec).
Interceptor that attaches all the nessesary information for weld injection to the interceptor context
Class that performs Jakarta Contexts and Dependency Injection and calls initializer methods after resource injection
has been run
Class that performs Jakarta Contexts and Dependency Injection injection and calls initializer methods on interceptor classes after resource injection
has been run
Immutable representation of Weld configuration in
jboss-all.xml.The Web Beans Jakarta Server Pages initialization listener
Managed reference factory that can be used to create and inject components.
A
ResourceLoader that can load classes from a ModuleDeployment processor that loads Jakarta Contexts and Dependency Injection portable extensions.
Service provider for
CDI.This service calls
Bootstrap.endInitialization(), i.e. places the container into a state where it can service
requests.Service that actually finishes starting the weld container, after it has been bootstrapped by
WeldBootstrapService