deltaspike-beanbuilder quickstart demonstrates a CDI Portable Extension that uses DeltaSpike utilities to create new Beans in Red Hat JBoss Enterprise Application Platform.
This extension permits the injection of JPA entities by id, without the need to query it. To achieve this, the extension observes the
ProcessInjectionTarget event and get locates all the injection points that have requested injection by id. In
AfterBeanDiscovery event, the extension creates
Bean instances using the
The project contains a very simple JPA entity class, the extension class, the service registration file for that extension and an Arquillian test to verify the extension is working correctly.
It does not contain any user interface; the tests must be run to verify everything is working correctly.
The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform (JBoss EAP) 6.1 or later with the Red Hat JBoss Web Framework Kit (WFK) 2.7.
All you need to build this project is Java 6.0 (Java SDK 1.6) or later, Maven 3.0 or later.
If you have not yet done so, you must Configure Maven before testing the quickstarts.
The following shows the command line to start the server with the default profile:
For Linux: EAP_HOME/bin/standalone.sh For Windows: EAP_HOME\bin\standalone.bat
This quickstart provides Arquillian tests. By default, these tests are configured to be skipped as Arquillian tests require the use of a container.
NOTE: The following commands assume you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Run the Arquillian Tests for complete instructions and additional options.
Type the following command to run the test goal with the following profile activated:
mvn clean test -Parq-jbossas-remote
NOTE: If you use the Maven settings command line argument with this quickstart, you need to pass an additional argument to allow ShrinkWrap Resolver to function properly:
mvn clean test -Parq-jbossas-remote -s /path/to/custom/settings.xml -Dorg.apache.maven.user-settings=/path/to/custom/settings.xml
To be able to run the tests from JBoss Developer Studio, first set the active Maven profile in project properties to be either 'arq-jbossas-managed' for running on managed server or 'arq-jbossas-remote' for running on remote server.
To run the tests, right click on the project or individual classes and select Run As –> JUnit Test in the context menu.
Maven prints summary of performed tests into the console:
T E S T S ------------------------------------------------------- Running org.jboss.as.quickstart.deltaspike.beanbuilder.test.ByIdExtensionTest log4j:WARN No appenders could be found for logger (org.jboss.logging). log4j:WARN Please initialize the log4j system properly. Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.641 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
You can also start the server and deploy the quickstarts or run the Arquillian tests from Eclipse using JBoss tools. For more information, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts
If you want to debug the source code or look at the Javadocs of any library in the project, run either of the following commands to pull them into your local repository. The IDE should then detect them.
mvn dependency:sources mvn dependency:resolve -Dclassifier=javadoc