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 }}
This repository was archived by the owner on Mar 20, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 20, 2021. It is now read-only.
Facelet metadata is not cached properly when contracts are used. #4392
Hi, We see a lot of contention on class.forName when using JSF with 2 resource library contracts.
It seems that the problem results from the composite component metadata not being cached correctly.
DefaultFaceletFactory.needsToBeRefreshed always returns false because the facelets are cached in cachePerContract.
This method is called from FaceletViewHandlingStrategy.getComponentMetadata.
Hi, We see a lot of contention on class.forName when using JSF with 2 resource library contracts.
It seems that the problem results from the composite component metadata not being cached correctly.
DefaultFaceletFactory.needsToBeRefreshed always returns false because the facelets are cached in cachePerContract.
This method is called from FaceletViewHandlingStrategy.getComponentMetadata.
Environment:
Payara 4.1.2.181
Mojarra 2.2.14