[seam-issues] [JBoss JIRA] Closed: (JBSEAM-1670) allow multiple scopes for @In annotation

[Pete Muir (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBSEAM-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBSEAM-1670.
-----------------------------

    Resolution: Out of Date


No more enhancements to DI model in Seam 2.

> allow multiple scopes for @In annotation
> ----------------------------------------
>
>                 Key: JBSEAM-1670
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1670
>             Project: Seam
>          Issue Type: Patch
>          Components: Core
>    Affects Versions: 2.0.0.BETA1
>            Reporter: Dan Allen
>            Priority: Minor
>             Fix For: The future
>
>         Attachments: JBSEAM-1670-v1.txt, JBSEAM-1670-v2.txt
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Right now, your only option for the scope on the @In annotation is an explicit scope or a hierarchical search of all the scopes. I can imagine that there are times when you want to look in a handful of scopes, but not all of them. For instance, anything within a conversation, but not above. Additionally, by making this a multi-value attribute, the developer can override the order in which the scopes are searched. They are searched in the order specified.
> ScopeType[] scope() default {};	
> This would also eliminate the need for the UNSPECIFIED scope since no scopes would assume a hierarchical search. The logic that would have to change is Component#getValueToInject()

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira