[
https://issues.apache.org/jira/browse/MYFACES-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966641#action_12966641
]
Leonardo Uribe commented on MYFACES-2949:
-----------------------------------------
I checked this one and myfaces is using JSF 2.0 resource api for this one. Note
it is valid to do the following:
<:h:outputScript library="org.apache.myfaces" name="oamSubmit.js"
target="head"/>
to prevent render this resource inline and collect them on head.
In this part myfaces is doing exactly what it is necessary to do for jsf.js
when it has not been rendered before.
It is still unknown it this behavior could cause problems on portlets case (at
the time I wrote this there is no any known JSF 2.0 portlet compatible
implementation yet).
> I think that MyFaces should use JSF 2 resource handling instead of directly
> write script resources to the output stream
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-2949
> URL: https://issues.apache.org/jira/browse/MYFACES-2949
> Project: MyFaces Core
> Issue Type: Bug
> Components: General, JSR-314
> Affects Versions: 2.0.2
> Environment: ALL
> Reporter: Hampus Wingren
>
> I think that MyFaces should use JSF 2 resource handling instead of directly
> write script resources to the output stream. Why not use the
> UIViewRoot.addComponentResource. The problem I´m having is that I´ve got a
> simple portal implementation that queries the resources added to the viewroot
> and then puts them in the portal <head> section.
> This could potentially be a problem in a portlet environment where several
> portlets will write out this script import directly to the response stream
> instead of collecting one of them under head.
> Regards,
> Hampus
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
