JBossDeveloper

Ken,

Yes, for @Local beans, that certainly makes sense. But what about @Remote interfaces? They could be looked up and used via JNDI remotely, without necessitating a local caller inside WAR or EAR, couldn't they?

Ken,

I've searched a bit more and found:
CDI spec

There it says:

In an application deployed as an EJB jar, the container searches the EJB jar, if it is a bean archive, and every bean archive referenced by the EJB jar.

and further up:

Bean classes of enabled beans must be deployed in bean archives.

and

A directory in the JVM classpath is a bean archive if it has a file named beans.xml in the META-INF directory.

however

The container is not required to support application client jar bean archives.

If I do understand this correctly, an EJB deployed jar should be able to discover beans for injection which are located outside of the EJB if they are located in a directory, however the beans are not required to be discovered (by spec) if they are packaged inside a jar which is referenced by the EJB-jar.

Is this correct understanding or do I measread it?

As far as I can tell (I have tried this), cdi injection works with a EJB which is is deployed as a jar (which is not further packaged inside EAR or WAR) IFF the to be injected CDI bean is also located inside this same EJB-jar. However, if the to be injected CDI bean is located outside EJB-jar, bean discovery seems not to work (as stated earlier, I belive this has to do with some classpath issues).

What do you think?

P.S. Please note, this is not a killer issue for me anymore, as it works when deploying inside EAR, it just bothers me, that I don't seem to be able to understand the whole mechanism correctly. In short: I don't want to steal your precious time with this topic.