Author: Peter Palaga, Brian Leathem, Ken Finnigan
Level: Beginner
Technologies: JSF2, Portlet Bridge
Summary: A simple portlet using JavaServer Faces 2.
Target Product: JBoss Portal
Source: https://github.com/jboss-developer/jboss-portal-quickstarts.git
This project demonstrates how to create a simple portlet using JavaServer Faces 2.1 and Portlet Bridge 3.3.1.Final.
An introduction and some background information to this quickstart can be found in the following chapters of Red Hat JBoss Portal Developer Guide:
All you need to build this example project is Java 6.0 (Java SDK 1.6) or newer and Maven 3.0 or newer.
The project is designed to be deployed on Red Hat JBoss Portal 6.1 running on JBoss EAP.
You have two options how you can configure Maven: A. Use hosted Maven repository or B. Download & setup zipped Maven repository.
This is the easier and thus recommended option. You need to configure the Maven user settings as follows:
Look for the settings.xml
file in the ${user.home}/.m2/
directory. For example:
For Linux or Mac: ~/.m2/settings.xml
For Windows: \Users\USER_NAME\.m2\settings.xml or \Documents and Settings\USER_NAME\.m2\settings.xml
If you have an existing settings.xml
file, modify it with the configuration information from the settings-hosted-repo.xml
file located in the root folder of Red Hat JBoss Portal quickstarts. This effectivelly results in
adding http://maven.repository.redhat.com/techpreview/all
as <repository>
and <pluginRepository>
to your settings.xml
.
If there is no settings.xml
file, copy the settings-hosted-repo.xml
file to the .m2
directory for your
operating system and rename it to settings.xml
.
Download the following zipped Maven repositories from Red Hat Customer Portal, Downloads > JBoss Enterprise Middleware:
Unpack each of these files to a separate directory.
Modify the settings-zipped-repos.xml
file located in the root directory of Red Hat JBoss Portal
quickstarts:
/path/to/repo/
within file:///path/to/repo/...
with the fully qualified path of the directory where you unpacked the given zipped Maven repository in the previous
step.<repository>
tag and one within
<pluginRepository>
tag.Be sure to use 3 forward slashes after file:
. Two slashes are there for the protocol and one for the fully qualified
path. For example:
file:///home/joedoe/Quickstarts/jpp-6.1-quickstarts
Configure the Maven user settings.
Look for the settings.xml
file in the ${user.home}/.m2/
directory. For example:
For Linux or Mac: ~/.m2/settings.xml
For Windows: \Users\USER_NAME\.m2\settings.xml or \Documents and Settings\USER_NAME\.m2\settings.xml
If you have an existing settings.xml
file, modify it with the configuration information from the example-settings.xml
file.
If there is no settings.xml
file, copy the modified example-settings.xml
file to the .m2
directory for your
operating system and rename it to settings.xml
.
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
Type this command to build and deploy the archive:
mvn clean package jboss-as:deploy
To deploy to other than default localhost:9999 JBoss instance, copy the following configuration
just after <artifactId>jboss-as-maven-plugin</artifactId>
in the pom.xml file and adjust it to suit your needs.
username
and password
elements can be omitted sometimes, depending on your JBoss security settings.
<configuration>
<hostname>127.0.0.1</hostname>
<port>9999</port>
<username>admin</username>
<password>secret</password>
</configuration>
This will deploy target/jsf2-hello-world-portlet.war
to the running instance of the portal.
To ensure that the example portlet has been deployed successfully, do the following:
When you are finished testing, type this command to undeploy the archive:
mvn jboss-as:undeploy
You can also deploy the quickstarts from Eclipse using JBoss Tools. For more information on how to set up Maven and JBoss Tools, refer to the JBoss Enterprise Application Platform 6 Development Guide or Get Started Developing Applications.
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
Please post feedback on this quickstart or Red Hat JBoss Portal on Online User Group.