I Have the same problem and it seems that nobody at JBoss cares since Embedded mode is not a priority.

JBoss Embedded is really a great concept, What JBoss miss is that someone who hesitates to use or not JBoss AS will certainly look for to any kind of Embedded Support.

OpenEJB has Embedded SupportGlassFish V3 has Embedded Support

Bill did the job to mockup the JNDI stuff but there still a lot of issues that are not solved. Providing the build of Embedded binaries from the AS source codebase is a minimum. That doesn't work and the current version (beta 3) is obsolete. So, what we do ?

"johanmicoud" wrote:JBoss Embedded is really a great concept, What JBoss miss is that someone who hesitates to use or not JBoss AS will certainly look for to any kind of Embedded Support.

OpenEJB has Embedded SupportGlassFish V3 has Embedded Support

Bill did the job to mockup the JNDI stuff but there still a lot of issues that are not solved. Providing the build of Embedded binaries from the AS source codebase is a minimum. That doesn't work and the current version (beta 3) is obsolete. So, what we do ?

+1

I have read that Jboss 5 is bunch of preconfigured services around OSGi and in this model for me is very strong point/virtue to running these services in whatever environment (junit, jse, server, jboss, tomcat, weblogic). Time of standalone Jee servers is gone, and Jboss way with preconfigured services on OSGi is fine but that services have to be able running in many context ;) Great success Spring is that Spring is running in many environments ().

It would probably be more correct to update the import statement in the classes that use that class, but it also works adding this reference to embedded/build.xml:

<path refid="org.jboss.aspects.classpath" />

Compilation goes well with those fixes, though the build breaks later on trying to assemble library jars. References to ejb3 jar files are not correct, and I have no idea how to fix them. I gave up at this point.