Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

Facelet metadata is not cached properly when contracts are used. #4392

Open
larslorenzen opened this issue Jan 7, 2019 · 1 comment
Open

Facelet metadata is not cached properly when contracts are used. #4392

larslorenzen opened this issue Jan 7, 2019 · 1 comment

Comments

@larslorenzen
Copy link

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
@erickdeoliveiraleal
Copy link

mojarra issue tracker moved to: https://github.com/eclipse-ee4j/mojarra

dmatej pushed a commit to payara/patched-src-mojarra that referenced this issue Feb 12, 2020
@TomasHofman @arjantijms
Escaping CDATA end tags
5726196 
Fixes javaee#4392

Signed-off-by: Tomas Hofman <thofman@redhat.com>
aubi pushed a commit to payara/patched-src-mojarra that referenced this issue Nov 17, 2022
@TomasHofman
Escaping CDATA end tags
0bf29e5 
Fixes javaee#4392

Signed-off-by: Tomas Hofman <thofman@redhat.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@larslorenzen @erickdeoliveiraleal