You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bug Report: Servlet container initializers do not see annotated classes from lib/warlibs jars (PrimeFaces 16 JSF1068) #8491
Servlet container initializers (e.g. Mojarra's FacesInitializer) do not receive annotated classes from jars in lib/warlibs, so with PrimeFaces 16 in warlibs, @FacesComponent classes are never registered.
Expected Outcome
Classes in warlib jars matching a ServletContainerInitializer's @HandlesTypes are passed to it, as for classes in WEB-INF/lib. PrimeFaces components render normally.
Current Outcome
Rendering a page using p:inputText fails:
JSF1068: Cannot instantiate component with component-type org.primefaces.component.InputText
jakarta.faces.FacesException: Expression Error: Named Object: org.primefaces.component.InputText not found.
Cause: warlibs are scanned once and their types cached in DeploymentUtils.getWarLibraryCache(), and cached jars are excluded from later scans (getWarLibraryURIs()). ServletContainerInitializerUtil.getInitializerList builds the @HandlesTypes input only from the deployment's Types, never from that cache. Only Weld (WeldUtils) reads it.
Reproducer
Put PrimeFaces 16 in lib/warlibs.
Deploy a Faces app that uses p:inputText with warlibs enabled.
changed the title [-]Servlet container initializers do not see annotated classes from lib/warlibs jars (e.g. PrimeFaces 16 JSF1068)[/-][+]Bug Report: Servlet container initializers do not see annotated classes from lib/warlibs jars (PrimeFaces 16 JSF1068)[/+]on Oct 9, 2026
Activity
[-]Servlet container initializers do not see annotated classes from lib/warlibs jars (e.g. PrimeFaces 16 JSF1068)[/-][+]Bug Report: Servlet container initializers do not see annotated classes from lib/warlibs jars (PrimeFaces 16 JSF1068)[/+]