[cdi-dev] Accessiblity of beans

On 22 Oct 2012, at 14:33, Mark Struberg wrote: I'm still not really understanding how scoping particularly affects this. I think this issue is true for any normal scoped bean. For the purposes of my answer, I'm assuming by "see" mean inject. This is absolutely correct. If we take a look 1.0 of the spec, 5.1.4 (Inter-module injection), we can see it clearly says "A bean is available for injection in a certain module if ... the bean class is required to be accessible to classes in the module, according to the class accessibility requirements of the module architecture." The accessibility requirements of Java EE are quite clear, there should *not* be visibility FROM a WAR TO an EAR shared library, and so therefore a bean defined in a WAR is NOT available for injection in an EAR shared library. This is not true. The resolution rules for observers are defined in chapter 10, and do not make any reference to 5.1.4, which are anyway about injection, as the section title indicates. Note that this is intended, as it allows events to propagate throughout the application. Without more details of the packaging of these beans I can't make a comment here. But it's certainly the case that injecting a user in one module will not result in the same thing as injecting a user in another module. This is true under any proposed scheme that we've discussed. What is important here is not that you get a different instance, but that the rules about what instance you get are: * consistent * easy to understand * easy to apply Agreed, there needs to be some increased specification here. You need to provide a little more detail of the problem you see here, as from this, I can't quite gather what you mean ;-) I think this is being a little pejorative towards those who see this as the *best* way to do things. In general, we are going to make better progress on this issue if we try to make rational well reasoned arguments. Definitely. Weld should never use the TCCL to determine bean accessibility.