myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Nicolucci (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Commented] (MYFACES-4141) JSF 2.3 Spec Issue 1436 - MyFaces Implementation requires Server Push functionality
Date Tue, 12 Sep 2017 17:04:02 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-4141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163289#comment-16163289
] 

Paul Nicolucci commented on MYFACES-4141:
-----------------------------------------

Unfortunately I have not had a change to get back to this due to other commitments. If someone
else can pick it up that would be awesome.

> JSF 2.3 Spec Issue 1436 - MyFaces Implementation requires Server Push functionality
> -----------------------------------------------------------------------------------
>
>                 Key: MYFACES-4141
>                 URL: https://issues.apache.org/jira/browse/MYFACES-4141
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-372
>    Affects Versions: 2.3.0-beta
>            Reporter: Paul Nicolucci
>             Fix For: 2.3.0
>
>
> The following spec issue does not look to be implemented in the MyFaces 2.3.0-beta: https://github.com/javaee/javaserverfaces-spec/issues/1436
> 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
(v6.4.14#64029)

Mime
View raw message