Hi! The (EJB centric) Spec of @Resource says that the resource will always be looked up via JNDI [1]. I guess mainly because the whole J2EE stuff is really JNDI centric.
Otoh in environments where no or only a read-only JNDI context is available, do we like to allow @Resouce also? I know this feature from Spring and I must say I love it. You can simply write a Bean and inject it via @Resource even without JNDI, So for Spring @Resource is more or less an alias for @Autowired (which is ~ our @Current) I'm not really sure how to interpret the section 5.12.1 of the spec. LieGrue, strub [1] http://java.sun.com/javaee/5/docs/api/javax/annotation/Resource.html
