You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Paulo Cristovão de Araújo Silva Filho (Jira)" <ji...@apache.org> on 2021/09/14 15:46:00 UTC
[jira] [Updated] (TOMEE-3791) Ajax JSF not provided in 8.0.8 builds
[ https://issues.apache.org/jira/browse/TOMEE-3791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paulo Cristovão de Araújo Silva Filho updated TOMEE-3791:
---------------------------------------------------------
Description:
Both plume and plus versions 8.0.8 of tomee were built without the jsf.js inside the respective jsf libs (jakarta.faces and myfaces). Plus (myfaces) shows up the folloing log:
{code:java}
org.apache.myfaces.renderkit.html.HtmlScriptRenderer.encodeEnd Resource referenced by resourceName jsf.js and libraryName javax.faces not found in call to ResourceHandler.createResource. It will be silenty ignored
{code}
Plume version silently ignores the problem.
Exchanging the packaged jar with the maven provided ones fixes the issue.
I guess the issue didn't show up in early phases because most of the tests on JSF does not use ajax enabled and that the issue is due some broken filtering (maybe you filtered out *.js or didin't filter them in).
Attached is a slightly modified version of the tomee-webapp with 6 profiles: the default webprofile, plus and plume, the three of them broken when you try to access book.jsf, and 3 others (webprofile-fixed, plus-fixed and plume-fixed), in which I've made the jar substitution. Using mvn -P<profilename> clean package tomee:run will allow checking accessing [http://localhost:8080/book.jsf]
was:
Both plume and plus versions 8.0.8 of tomee were built without the jsf.js inside the respective jsf libs (jakarta.faces and myfaces). Plus (myfaces) shows up the folloing log:
{code:java}
org.apache.myfaces.renderkit.html.HtmlScriptRenderer.encodeEnd Resource referenced by resourceName jsf.js and libraryName javax.faces not found in call to ResourceHandler.createResource. It will be silenty ignored
{code}
Plume version silently ignores the problem.
Exchanging the packaged jar with the maven provided ones fixes the issue.
I guess the issue didn't show up in early fases because most of the tests on JSF does not use ajax enabled and that the issue is due some broken filtering (maybe you filtered out *.js or didin't filter them in).
Attached is a slightly modified version of the tomee-webapp with 6 profiles: the default webprofile, plus and plume, the three of them broken when you try to access book.jsf, and 3 others (webprofile-fixed, plus-fixed and plume-fixed), in which I've made the jar substitution. Using mvn -P<profilename> clean package tomee:run will allow checking accessing [http://localhost:8080/book.jsf]
> Ajax JSF not provided in 8.0.8 builds
> -------------------------------------
>
> Key: TOMEE-3791
> URL: https://issues.apache.org/jira/browse/TOMEE-3791
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Build
> Affects Versions: 8.0.8
> Reporter: Paulo Cristovão de Araújo Silva Filho
> Priority: Blocker
> Attachments: books-jsf.tar.gz
>
>
> Both plume and plus versions 8.0.8 of tomee were built without the jsf.js inside the respective jsf libs (jakarta.faces and myfaces). Plus (myfaces) shows up the folloing log:
> {code:java}
> org.apache.myfaces.renderkit.html.HtmlScriptRenderer.encodeEnd Resource referenced by resourceName jsf.js and libraryName javax.faces not found in call to ResourceHandler.createResource. It will be silenty ignored
> {code}
> Plume version silently ignores the problem.
> Exchanging the packaged jar with the maven provided ones fixes the issue.
> I guess the issue didn't show up in early phases because most of the tests on JSF does not use ajax enabled and that the issue is due some broken filtering (maybe you filtered out *.js or didin't filter them in).
> Attached is a slightly modified version of the tomee-webapp with 6 profiles: the default webprofile, plus and plume, the three of them broken when you try to access book.jsf, and 3 others (webprofile-fixed, plus-fixed and plume-fixed), in which I've made the jar substitution. Using mvn -P<profilename> clean package tomee:run will allow checking accessing [http://localhost:8080/book.jsf]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)