[jboss-jira] [JBoss JIRA] (WFLY-11151) Wildfly 14 mixes up HTML response in JSF applications

[Tamás Ábele (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tamás Ábele updated WFLY-11151:
-------------------------------
    Description: 
Introduced in wildfly 14 we receive a new JSF implementation (developed years ago), which is based on mojarra 2.3.5. In certain circumstances this JSF runtime hides the real problem, and makes from an invalid HTML a valid one, and spoils it somewhere else you would never guess, or produces an invalid partial response. Anything can happen, and the real problem will be really hard to find. This behavior led to a more severe error than the original one in two reported cases at github.

I opened an issue ([eclipse-ee4j/mojarra#4488|https://github.com/eclipse-ee4j/mojarra/issues/4488]) about this, but the mojarra development team closed this issue without solving it, despite the fact how vulnerable JSF become to component rendering problems. Now a lot of teams starting to move towards wildfly 14. They are likely to face similar magical errors like us. In the other case ([jboss/mojarra#21|https://github.com/jboss/mojarra/issues/21]) the developer team switched back to JSF 2.2. I’m also worried to change to wildfly 14, because of the future magical errors it will cause in our systems.


  was:
Introduced in wildfly 14 we receive a new JSF implementation (developed years ago), which is based on mojarra 2.3.5. In certain circumstances this JSF runtime hides the real problem, and makes from an invalid HTML a valid one, and spoils it somewhere else you would never guess, or produces an invalid partial response. Anything can happen. This way the JSF runtime makes it really hard to find the real problem. This behavior led to a more severe error than the original one in two reported cases at github.

I opened an issue ([eclipse-ee4j/mojarra#4488|https://github.com/eclipse-ee4j/mojarra/issues/4488]) about this, but the mojarra development team closed this issue without solving it, despite the fact how vulnerable JSF become to component rendering problems. Now a lot of teams starting to move towards wildfly 14. They are likely to face similar magical errors like us. In the other case ([jboss/mojarra#21|https://github.com/jboss/mojarra/issues/21]) the developer team switched back to JSF 2.2. I’m also worried to change to wildfly 14, because of the future magical errors it will cause in our systems.




> Wildfly 14 mixes up HTML response in JSF applications
> -----------------------------------------------------
>
>                 Key: WFLY-11151
>                 URL: https://issues.jboss.org/browse/WFLY-11151
>             Project: WildFly
>          Issue Type: Bug
>          Components: JSF
>    Affects Versions: 14.0.0.Final
>            Reporter: Tamás Ábele
>            Assignee: Jason Greene
>            Priority: Major
>
> Introduced in wildfly 14 we receive a new JSF implementation (developed years ago), which is based on mojarra 2.3.5. In certain circumstances this JSF runtime hides the real problem, and makes from an invalid HTML a valid one, and spoils it somewhere else you would never guess, or produces an invalid partial response. Anything can happen, and the real problem will be really hard to find. This behavior led to a more severe error than the original one in two reported cases at github.
> I opened an issue ([eclipse-ee4j/mojarra#4488|https://github.com/eclipse-ee4j/mojarra/issues/4488]) about this, but the mojarra development team closed this issue without solving it, despite the fact how vulnerable JSF become to component rendering problems. Now a lot of teams starting to move towards wildfly 14. They are likely to face similar magical errors like us. In the other case ([jboss/mojarra#21|https://github.com/jboss/mojarra/issues/21]) the developer team switched back to JSF 2.2. I’m also worried to change to wildfly 14, because of the future magical errors it will cause in our systems.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)