[
https://issues.apache.org/jira/browse/MYFACES-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13694182#comment-13694182
]
Leonardo Uribe commented on MYFACES-3740:
-----------------------------------------
The problem with this issue is that to resolve "this" identifier it is
necessary to setup the context. For example, if a css resource is being served,
the resulting EL expressions that are evaluated must take the context into
account. If the file is a simple template, "this" should refer to the current
facelet template, but that's tricky because if the EL expression is evaluated
outside facelets control, the reference is lost.
> ResourceResolver "this" identifier applies for contracts too in JSF 2.2
> -----------------------------------------------------------------------
>
> Key: MYFACES-3740
> URL: https://issues.apache.org/jira/browse/MYFACES-3740
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-344
> Reporter: Leonardo Uribe
>
> Doing some reviews in the code, I found these lines in JSF 2.2 section
> 5.6.2.5 :
> getValue()
> "... If property contains a single colon character ‘:’, treat the content
> before the ‘:’ as the libraryName and the content after the ‘:’ as the
> resourceName and pass both to ResourceHandler.createResource(
> resourceName, libraryName). If the value of libraryName is the literal string
> “this” (without the quotes), discover the library name of the current
> resource (or the contract name of the current resource, the two
> are mutually exclusive) and replace “this” with that library name (or
> contract name) before calling
> ResourceHandler.createResource(). In the case of resource library contracts,
> libraryName will actually be the contract name. If property contains more
> than one colon character ‘:’, throw a localized
> ELException, including property ..."
> In JSF 2.0, "this" was used when el expression where inside composite
> components, but in this case "this" refers to the contract itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
