While further investigating the recent changes in OWB due to JSR 330 I
stumbled upon the mismatch of @Named in OWB and in JSR 330. In 330 it is
defined as a qualifying annotation as far as I know (based on my knowledge
about Guice and
http://atinject.googlecode.com/svn/trunk/src/javax/inject/Named.java), but
OWB use it as a simple annotation.
>From my point of view this is a conceptual mismatch: One spec uses the
annotation just for binding specific beans to a literal name, the other one
uses it for differentiate between multiple beans. Even this should be no
immediate issue for JSR 299's typesafe resolution mechanism, if a single
bean is further qualified with specific @Named name, I do not feel well, if
people are going to use this annotation as a qualifying one like
@Named("stage_test") on multiple bans. The EL namespace gets polluted with
unresolvable names and developers become potentially confused by the
conceptually ambiguously usage of the annotation.
Your opinion?
br, Sven
