There is a bug in JBoss AS 6 M3 which causes the BeanManager to be bound under the wrong JNDI name when deploying CDI + EJB in a War.
This is fixed in JBoss AS trunk (upcoming M4).
Your best bet for now is either to not use EJBs with CDI, or build JBoss AS from trunk.
Actually, there is a much simpler way. Just download the nightly snapshots. A snapshot only gets generated if the tests pass, so you won't get a dud.
I also made a tinyurl for this:
That's the app server build, but you also need the Maven client artifacts for the same build. They are not published to the JBoss nexus repo I think?
Dan, do you have a Repo for them?
Hahaha. I knew you were going to say that
<dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-depchain</artifactId> <version>6.0.0-SNAPSHOT</version> <type>pom</type> </dependency> <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-client</artifactId> <version>6.0.0-SNAPSHOT</version> <type>pom</type> </dependency> <dependency> <groupId>org.jboss.jbossas</groupId> <artifactId>jboss-as-distribution</artifactId> <version>6.0.0-SNAPSHOT</version> <type>zip</type> </dependency>
Those are available in http://repository.jboss.org/nexus/content/groups/public/
I'm not sure how you get Maven to link against a specific snapshot release. I tried the full version, but different dependencies have different snapshot version numbers for the same date.
Sure you don't have a local build?
They are all empty..?
What the heck? Either I was dreaming when I ran that test, or they have since disappeared. Odd. At first I thought maybe they are only available in the developer nexus group, but they are blank there too. Hmmmm.
I can tell you one thing for sure, I haven't built JBoss AS
Okay, so maybe you have to build JBoss AS
The AS Hudson run does not use profile "dist-zip", so these are not even generated to be uploaded to Nexus.
For local installs of AS, build with "./build.sh -Pdist-zip" to get it into your local repo.
Thanks, all! I'm building JBoss AS right now. If nothing else, I'll probably wait until m4, which, a quick search tells me, will be out next week sometime.