Embedded JBoss FAQ

Q: Embedded JBoss boots up so fast, why should I ever use JBoss AS?

A: Embedded JBoss does not support hot deployment or any Java EE packaging type that isn't a JAR (EARs and WARs for example).  Embedded JBoss does not support a servlet engine nor does not provide any management features.

Q: Embedded JBoss boots up fine and fast in Tomcat, why should I ever use JBoss AS?

There are a few significant AS features not tested in Embedded.  Specifically clustering and manage features.  An AS deployment also gives you greater fine-grain deployment and classloader flexibility.

Q: Can Embedded JBoss be used in non testing environments?

A: Yes, all components deployed in Embedded JBoss are the same components deployed in JBoss Application server.  JBoss TS, JBoss Messaging, JCA, JNDI, EJB, etc... all are the same codebase.

Q: I added a .jar file to the embedded deploy/ directory but I am getting class not found errors.  What is the problem?

Embedded JBoss does not create any classloaders or manipulate the classpath.  It uses the system classpath and/or the context classloader.  So, you must add that particular .jar file to your classpath.