Gavin, I have a suggestion for Web Beans regarding the convention used by the @Named annotation. The nice part about this annotation is that it doesn't require the use of a string value to create a name that maps to the class name. In ~80% of cases, that is what people would do anyway. However, for framework builders, I can see them wanting to create fully-qualified names like in Seam to avoid naming conflicts. Would it be reasonable to propose adding an attribute to the @Named annotation that indicates the Java package should be prepended to the calculated name? @Named(qualified = true) That would avoid people slipping into the non-type safe pattern of: @Named("org.jboss.seam.core.expressions") -Dan -- Dan Allen Software consultant | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention.