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

[Pete Muir (JIRA)]

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

Pete Muir commented on CDI-164:
-------------------------------

Working through this:

* I've moved the bean manager exclusion to chapter 8
* Extensions aren't built-in beans, so this doesn't apply
* I'm not sure we want to offer decorating of other container provided beans, that wasn't discussed. Though we could expand it call them built in beans? Not sure, that should be a new issue. Validator stuff has moved out anyway.
* I've added built-in beans to list of stuff that must have passivation capable decorators
                
> 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