[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1670) allow multiple scopes for @In annotation
Dan Allen (JIRA)
jira-events at lists.jboss.org
Sun Jul 15 18:22:03 EDT 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-1670?page=all ]
Dan Allen updated JBSEAM-1670:
------------------------------
Attachment: JBSEAM-1670-v1.txt
I believe I got the logic right for Component#getValueToInject() , but I was a tad confused about the semantics of the enforceRequired variable.
> allow multiple scopes for @In annotation
> ----------------------------------------
>
> Key: JBSEAM-1670
> URL: http://jira.jboss.com/jira/browse/JBSEAM-1670
> Project: JBoss Seam
> Issue Type: Patch
> Components: Core
> Affects Versions: 2.0.0.BETA1
> Reporter: Dan Allen
> Priority: Minor
> Fix For: 2.0.0.CR1, 2.0.0.GA, 2.0.1.GA
>
> Attachments: JBSEAM-1670-v1.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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list