[cdi-dev] [JBoss JIRA] (CDI-164) Decorating built in beans

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Thu Nov 1 04:47:18 EDT 2012


    [ https://issues.jboss.org/browse/CDI-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730706#comment-12730706 ] 

Jozef Hartinger commented on CDI-164:
-------------------------------------

I though the intention was to enable decoration of all container-provided beans and specifying the requirement for those labeled with "built-in" was only an oversight. However, it seems it was actually intentional. Here's a summary of what is currently required to support decoration if we go strictly with the "built-in label":

* Event
* Instance
* Conversation
* HttpServletRequest / HttpSession / ServletContext
* InjectionPoint
* Principal
* UserTransaction

The container-provided beans that are not required to support decoration:

* extensions (injected instances)
* Bean, Interceptor, Decorator (@Default, @Intercepted or @Decorated)
* Validator
* ValidatorFactory

Built-in beans not supporting decoration: 
* BeanManager
                
> Decorating built in beans
> -------------------------
>
>                 Key: CDI-164
>                 URL: https://issues.jboss.org/browse/CDI-164
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Decorators
>    Affects Versions: 1.0
>            Reporter: Jozef Hartinger
>            Assignee: Pete Muir
>             Fix For: 1.1.PFD
>
>
> In CDI 1.0, decorators may only be applied to managed and session beans. Decorating built-in beans would make CDI extensions more powerful. 
> One of the possible usecases is represented by decorating the Event bean https://gist.github.com/1223042
> This would allow extensions to implement for example:
> * event queuing (Forge)
> * bidirectional mapping to another event technology without introducing infinite loops (Seam JMS)

--
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


More information about the cdi-dev mailing list