myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Nicolucci (JIRA)" <>
Subject [jira] [Commented] (MYFACES-4141) JSF 2.3 Spec Issue 1436 - MyFaces Implementation requires Server Push functionality
Date Thu, 09 Nov 2017 01:05:00 GMT


Paul Nicolucci commented on MYFACES-4141:

Interestingly enough, I was looking over the EG mailing list and it says they plan to implement
this in Mojarra in the next 2.3 release (2.3.1). So does not look like they implemented it
on their initial delivery either.

Link to thread:,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,5029044

Specific thread from Spec Lead Ed Burns:

So I think you're right, we can probably be fine with a 2.3.0 without this functionality as
the RI has not even tried to implement this aspect.

Perhaps the implemented would use the Servlet 4.0 PushBuilder API, the spec is pretty vague:

> JSF 2.3 Spec Issue 1436 - MyFaces Implementation requires Server Push functionality
> -----------------------------------------------------------------------------------
>                 Key: MYFACES-4141
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-372
>    Affects Versions: 2.3.0-beta
>            Reporter: Paul Nicolucci
> The following spec issue does not look to be implemented in the MyFaces 2.3.0-beta:
> The following text was added to the JSF 2.3 specification section 2.2.6 "Render Response":
> If running on a container that supports Servlet 4.0 or later, after any dynamic component
manipulations have been
> completed, any resources that have been added to the UIViewRoot, such as scripts, images,
or stylesheets, and any
> inline images, must be pushed to the client using the Servlet Server Push API. All of
the pushes must be started
> before any of the HTML of the response is rendered to the client.

This message was sent by Atlassian JIRA

View raw message