[
http://jira.jboss.com/jira/browse/JBSEAM-1670?page=comments#action_12369035 ]
Dan Allen commented on JBSEAM-1670:
-----------------------------------
Oh, and thanks to the syntax of annotation attribute values, this should not affect
existing applications because a single value does not require the brackets. It is fully
backward compatible. Ah, in thinking about that, we may need to add logic that handles the
case when the UNSPECIFIED scope is used. Like I said, the patch is a good start, but needs
to be reviewed.
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, 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:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira