You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Leonardo Uribe (JIRA)" <de...@myfaces.apache.org> on 2013/09/27 13:30:03 UTC
[jira] [Commented] (MYFACES-3785) RendererWrapper logic
(@ListenerFor and @ResourceDependency)
[ https://issues.apache.org/jira/browse/MYFACES-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13779835#comment-13779835 ]
Leonardo Uribe commented on MYFACES-3785:
-----------------------------------------
This issue has two points:
1. Scan for annotation following RendererWrapper wrappers.
2. Deal with @ListenerFor
Solving the first one is enough to make @ResourceDependency to work. The tricky point is @ListenerFor, because in this case we need to subscribe the Renderer as listener and in that sense we need to change some internals in UIComponent class to take it into account.
I have done some junit tests in ApplicationImplAnnotationTest too.
> RendererWrapper logic (@ListenerFor and @ResourceDependency)
> ------------------------------------------------------------
>
> Key: MYFACES-3785
> URL: https://issues.apache.org/jira/browse/MYFACES-3785
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-344
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
>
> This issue was included in the spec as:
> https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-1109
> But it is more difficult than just implement one wrapper class. The reason is @ListenerFor and @ResourceDependency annotations could be used in the base class and in the wrapper.
> In this part we need to update MyFaces implementation to check for RendererWrapper in the places where we need to scan for annotations.
> I can remember some problems with renderer wrappers in extval and other libraries, and the inclusion of RendererWrapper aims to solve all these troubles, saying "all wrappers now must implement RendererWrapper class, and you can walkthrough the hierarchy of objects using getWrapped() method".
--
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