[
https://issues.apache.org/jira/browse/MYFACES-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12893991#action_12893991
]
Werner Punz commented on MYFACES-2848:
--------------------------------------
The question only is, would it break the spec, otherwise I would favor this
approach...
Ganesh in the meanwhile you can use following workaround, simply push a
<h:outputScript for jsf.js into the header this should prevent the inclusion of
the code in the body.
The problem is mainly caused by the auto inclusion into the body in this area,
but I guess as jakob said, jsf.js should not be rendered at all if it is an
ajax case.
> AJAX responses contain <script type="text/javascript"
> src="/MyFaces_Test/javax.faces.resource/jsf.js.faces?ln=javax.faces">
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-2848
> URL: https://issues.apache.org/jira/browse/MYFACES-2848
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.1
> Environment: AJAX Java
> Reporter: Ganesh Jung
> Attachments: Test.war
>
>
> The fact that an AJAX request was triggered clearly shows, that jsf.js is
> already available to the browser. Including it again in the response triggers
> another HTTP GET for jsf.js with time and traffic penalty.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.