What is it?
This example demonstrates the use of CDI 1.0 and JAX-RS in JBoss AS 7 or JBoss Enterprise Application Platform 6.
System requirements
All you need to build this project is Java 6.0 (Java SDK 1.6) or better, Maven 3.0 or better.
The application this project produces is designed to be run on JBoss Enterprise Application Platform 6 or JBoss AS 7.
Configure Maven
If you have not yet done so, you must Configure Maven before testing the quickstarts.
Start JBoss Enterprise Application Platform 6 or JBoss AS 7 with the Web Profile
- Open a command line and navigate to the root of the JBoss server directory.
-
The following shows the command line to start the server with the web profile:
For Linux: JBOSS_HOME/bin/standalone.sh For Windows: JBOSS_HOME\bin\standalone.bat
Build and Deploy the Quickstart
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.
- Make sure you have started the JBoss Server as described above.
- Open a command line and navigate to the root directory of this quickstart.
-
Type this command to build and deploy the archive:
mvn clean package jboss-as:deploy This will deploy
target/jboss-as-helloworld-rs.warto the running instance of the server.
Access the application
The application is deployed to http://localhost:8080/jboss-as-helloworld-rs.
The XML content can be viewed by accessing the following URL: http://localhost:8080/jboss-as-helloworld-rs/rest/xml
The JSON content can be viewed by accessing this URL: http://localhost:8080/jboss-as-helloworld-rs/rest/json
Undeploy the Archive
- Make sure you have started the JBoss Server as described above.
- Open a command line and navigate to the root directory of this quickstart.
-
When you are finished testing, type this command to undeploy the archive:
mvn jboss-as:undeploy
Run the Quickstart in JBoss Developer Studio or Eclipse
You can also start the server and deploy the quickstarts from Eclipse using JBoss tools. For more information, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts
Debug the Application
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
Build and Deploy the Quickstart - to OpenShift
Create an OpenShift Express Account and Domain
If you do not yet have an OpenShift account and domain, Sign in to OpenShift to create the account and domain. Get Started with OpenShift will show you how to install the OpenShift Express command line interface.
Create the OpenShift Application
Open a shell command prompt and change to a directory of your choice. Enter the following command, replacing APPLICATION_TYPE with jbosseap-6.0 for quickstarts running on JBoss Enterprise Application Platform 6, or jbossas-7 for quickstarts running on JBoss AS 7:
rhc app create -a helloworldrs -t APPLICATION_TYPE
NOTE: The domain name for this application will be helloworldrs-YOUR_DOMAIN_NAME.rhcloud.com. Here we use the quickstart domain. You will need to replace it with your own OpenShift domain name.
This command creates an OpenShift application named helloworldrs and will run the application inside the jbosseap-6.0 or jbossas-7 container. You should see some output similar to the following:
Creating application: helloworldrs
Now your new domain name is being propagated worldwide (this might take a minute)...
Warning: Permanently added 'helloworldrs-quickstart.rhcloud.com,107.22.36.32' (RSA) to the list of known hosts.
Confirming application 'helloworldrs' is available: Success!
helloworldrs published: http://helloworldrs-quickstart.rhcloud.com/
git url: ssh://b92047bdc05e46c980cc3501c3577c1e@helloworldrs-quickstart.rhcloud.com/~/git/helloworldrs.git/
Successfully created application: helloworldrs
The create command creates a git repository in the current directory with the same name as the application. Notice that the output also reports the URL at which the application can be accessed. Make sure it is available by typing the published url http://helloworldrs-quickstart.rhcloud.com/ into a browser or use command line tools such as curl or wget. Be sure to replace the quickstart in the URL with your domain name.
Migrate the Quickstart Source
Now that you have confirmed it is working you can migrate the quickstart source. You do not need the generated default application, so navigate to the new git repository directory and tell git to remove the source and pom files:
cd helloworldrs
git rm -r src pom.xml
Copy the source for the helloworld-rs quickstart into this new git repository:
cp -r <quickstarts>/helloworld-rs/src .
cp <quickstarts>/helloworld-rs/pom.xml .
Deploy the OpenShift Application
You can now deploy the changes to your OpenShift application using git as follows:
git add src pom.xml
git commit -m "helloworld-rs quickstart on OpenShift"
git push
The final push command triggers the OpenShift infrastructure to build and deploy the changes.
Note that the openshift profile in the pom.xml file is activated by OpenShift. This causes the WAR built by OpenShift to be copied to the deployments directory and deployed without a context path.
Test the OpenShift Application
When the push command returns you can test the application by getting the following URLs either via a browser or using tools such as curl or wget. Be sure to replace the quickstart in the URL with your domain name.
- http://helloworldrs-quickstart.rhcloud.com/rest/xml if you want xml or
- http://helloworldrs-quickstart.rhcloud.com/rest/json if you want json
You can use the OpenShift command line tools or the OpenShift web console to discover and control the application.
Destroy the OpenShift Application
If you plan to test the jax-rs-client quickstart on OpenShift, you may want to wait to destroy this application because it is also used by that quickstart for testing. When you are finished with the application you can destroy it as follows:
rhc app destroy -a helloworldrs
Note: There is a limit to the number of applications you can deploy concurrently to OpenShift. If the rhc app create command returns an error indicating you have reached that limit, you must destroy an existing application before you continue.
- To view the list of your OpenShift applications, type:
rhc domain show - To destroy an existing application, type the following, substituting the application name you want to destroy:
rhc app destroy -a APPLICATION_NAME_TO_DESTROY
Share the Knowledge
Find this guide useful?
Feedback
Find a bug in the guide? Something missing? You can fix it by forking the repository, making the correction and sending a pull request. If you're just plain stuck, feel free to ask a question in the user discussion forum.
Recent Changelog
- Feb 12, 2013: Add quickstart source repository of record to the readme files Sande Gilda
- Sep 11, 2012: Add target product (https://issues.jboss.org/browse/jdf-108) Sande Gilda
- Jul 30, 2012: Fix openshift instructions, issue #291, developer and doc links Sande Gilda
- Jul 19, 2012: Fix issue #301 and issue #302 : remove openshift warning, make template readme instructions clearer Sande Gilda
- May 18, 2012: Move metadata to quickstarts Pete Muir
- May 06, 2012: Add a nice index page for hellworld-rs :-) Pete Muir
- May 03, 2012: Clarify that the domain portion of the openshift url will be your own domain Sande Gilda
- May 03, 2012: Add caveat that only the as7 quickstarts currently run on openshift Sande Gilda
- May 03, 2012: Fix readme problems found in qe testing of eap 6 quickstarts Sande Gilda
- Apr 11, 2012: Remove odd trailing slashes Pete Muir
- Apr 10, 2012: Solve issue #194 :-) auto transform links from readme.md -> readme.html Pete Muir
- Apr 05, 2012: Missed adding the arquillian instructions, fixed indentations, modified jta-crash-rec and jts-distributed-crash-rec, add missing authors Sande Gilda
- Apr 01, 2012: More readme cleanup Sande Gilda
- Mar 26, 2012: Attempt to standardize readme.md files Sande Gilda
- Mar 23, 2012: Minor improvements to readme based on paul's readme Pete Muir