myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leonardo Uribe (JIRA)" <>
Subject [jira] [Commented] (MYFACES-3785) RendererWrapper logic (@ListenerFor and @ResourceDependency)
Date Fri, 27 Sep 2013 11:30:03 GMT


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:
>             Project: MyFaces Core
>          Issue Type: Task
>          Components: JSR-344
>            Reporter: Leonardo Uribe
>            Assignee: Leonardo Uribe
> This issue was included in the spec as:
> 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:

View raw message