deltaspike-projectstage quickstart demonstrates how to use DeltaSpike project stages, for example, conditional
@Exclude, in Red Hat JBoss Enterprise Application Platform. Project stages provide a way to customize the implementation based on the type of deployment environment. For example, you may want to generate sample data for system testing, but not for production. You can create a bean that generates sample data and activate it only for project stage SystemTest
Besides custom project stages it's possible to use the following pre-defined project stages:
@Exclude, it is possible to annotate beans which should be ignored by CDI, even if they are in a CDI enabled archive.
This project has a interface called
MyBean that has 4 different implementations:
@Exclude(exceptIfProjectStage=Development.class)to exclude the implementation if the project stage is anything other than Development..
@Exclude(ifProjectStage=Development.class)to exclude the implementation for project stage Development.
@Excludeto exclude the implementation for all project stages.
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
NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Build and Deploy the Quickstarts for complete instructions and additional options.
Type this command to build and deploy the archive:
mvn clean package jboss-as:deploy
target/jboss-deltaspike-projectstage.warto the running instance of the server.
Access the running application in a browser at the following URL: http://localhost:8080/jboss-deltaspike-projectstage
You be presented with a simple page that shows the current project stage: Staging. You will se also the List of available CDI instances for MyBean table with two available implementations.
Edit the file
src/main/resources/META-INF/apache-deltaspike.properties and change the
org.apache.deltaspike.ProjectStage property to
Development. Deploy the application again
mvn clean package jboss-as:deploy
Access the application again at the same URL: http://localhost:8080/jboss-deltaspike-projectstage
Look at List of available CDI instances for MyBean table and realize that the available implementations has changed.
When you are finished testing, type this command to undeploy the archive:
This quickstart provides Arquillian functional tests. They are located under the directory "functional-tests". Functional tests verify that your application behaves correctly from the user's point of view - simulating clicking around the page as a normal user would do.
To run these tests, you must build the main project as described above.
Build the quickstart WAR using the following command:
mvn clean package
If you have a running instance of the JBoss EAP server, as described above, run the remote tests by typing the following command:
mvn clean verify -Parq-jbossas-remote
NOTE: For this to work, Arquillian needs to know the location of the JBoss EAP server. This can be declared through the
JBOSS_HOME environment variable or the
jbossHome property in
arquillian.xml. See Run the Arquillian Tests for complete instructions and additional options.
mvn clean verify -Parq-jbossas-managed
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