Thanks for considering it, Gavin.
However, I don't like it either because it doesn't fully solve the problem: in
the example above, the same class would be used as a Seam component in some
roles but not in others.
My suggestion: a "create" property in the @Role annotation (and in @Scope?).
Defaults to "true", but we could specify ("create=false").
This would allow null values in Seam components. (I'm JIRAing this suggestion).
Maybe this conflicts heavily with what a "Seam-managed component" is supposed
to be. Then the solution would be to create a new annotation specifying a role
and default scope (again, the same class could have different roles even if
it's not a Seam component in any of them). But wouldn't that just look too much
like the @Role annotation?
(All these forum messages with "feature XX doesn't work" and "feature YY"
requests may sound a bit harsh, so let me use this opportunity to express, for
what it's worth, how great a job I think you guys are doing with Seam).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952100#3952100
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952100
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
