Oh, and one other thing. By making this a multi-value attribute, the user can
override the order in which the scopes are searched. They are searched in the
order specified!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4064370#4064370
Reply to the post :
I want it too.
Thanks!
Ellen
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4064372#4064372
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4064372
___
jboss-user mailing list
I now have a patch if anyone is interested.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4064377#4064377
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4064377
___
jboss-user
sorry, i meant Thanks!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4064379#4064379
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4064379
___
jboss-user mailing list
The semantics of how it searches a given scope would remain the same as it is
today. Meaning, if you put scope = ScopeType.CONVERSATION, then it will just do
Component.getInstance(value, ScopeType.CONVERSATION). This patch just let's
you work multiple scopes, but the lookup is still the same.