The quickstarts demonstrate JBoss AS 7, Java EE 6 and a few additional technologies. They provide small, specific, working examples that can be used as a reference for your own project
jboss-as-maven-plugin to deploy the webapp. Unfortunately, this plugin does not allow me to start and stop the server and it seems redundant to require a local install if the Arquillian tests already download an AS instance (yes, I could run the test against the local instance as well, but think for example continuous integration where I want to manage/control the WHOLE ENVIRONMENT).
cargo plugin another go. A lot has happened there and it supports not only JBoss 7.x, but it also offers a so called artifact installer which allows to download the app server as a managed maven dependency.
cargo:install in the initialize phase to install the app server into the target directory. This way I can install a custom module (via the gmaven plugin) before the tests get executed and/or before I start the application
able to deploy my application directly from the workspace
bad news is that JBoss AS 7 does not currently support other persistence providers like Eclipselink, OpenJPA or DataNucleus
GlassFish and Resin, you can simply drop the JARs of your preferred provider and its dependencies in a designated folder of your server installation and edit your persistence.xml to override the default provider of the server
JBoss AS 7 appears to require an adapter per persistence provider, which to me looks like an unfortunate and unnecessary design decision
potential to take over the lead from GlassFish
documentation continues to be sketchy and far below the standard of JBoss AS 5
surprisingly lean and fast
top-level performance
classloader leaks
productivity issues of the Eclipse integration
lack of support for JPA providers other than Hibernate
Each of these is currently a blocker for using JBoss AS 7 in production
Redeployment
after a couple of redeployments, there was an OutOfMemoryError
new classloader leak
JBoss AS 7: Catching up with Java EE 6
Performance measurements
JBoss AS 7.0.2
GlassFish 3.1.1
Empty server startup time 1.9 s
3.2 s
Empty server heap memory 10.5 MB
26.5 MB
Empty server PermGen memory 36.3 MB
28.4 MB
MyApp deployment time 5.8 s
JBoss AS 7 is now at a competitive level with Resin and Glassfish and actually outperforms Glassfish in almost all of these tests
displayed using JSF views, business logic is encapsulated in CDI beans, information is persisted using JPA, and transactions can be controlled manually or using EJB
deploy the example by right clicking on the jboss-as-login project, and choosing Run As -> Run On Server
src/main/webapp directory
beans.xml and face-config.xml tell JBoss AS to enable CDI and JSF for the application
don't need a web.xml
src/main/resources
persistence.xml, which sets up JPA, and import.sql which Hibernate, the JPA provider in JBoss AS, will use to load the initial users into the application when the application starts