It's time to pull the covers back and dive into the internals of Weld example applications. Let's start with the
simpler of the two examples, weld-numberguess.
In the numberguess application you get 10 attempts to guess a number between 1 and 100. After each attempt, you're told whether your guess was too high or too low.
The numberguess example is comprised of a number of beans, configuration files and Facelets (JSF) views, packaged as a war module. Let's start by examining the configuration files.
All the configuration files for this example are located in WEB-INF/, which can be found in
the src/main/webapp directory of the example. First, we have the JSF 2.2 version of
faces-config.xml. A standardized version of Facelets is the default view handler in JSF
2.2, so there's really nothing that we have to configure. Thus, the configuration consists of only the root
element.
<faces-config version="2.2"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd">
<name>numberguess</name>
</faces-config>
There's also an empty beans.xml file, which tells the container to look for beans in this
archive and to activate the CDI services.
Finally, some of the supported servers also need a web.xml which is located in
src/main/webapp-[server]/WEB-INF.
Note
This demo uses JSF 2 as the view framework, but you can use Weld with any servlet-based web framework, such as JSF 1.2 or Wicket.
Let's take a look at the main JSF view, src/main/webapp/home.xhtml.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:f="http://java.sun.com/jsf/core">
ml_plain">
<ui:composition template="/template.xhtml">
<ui:define name="content">
<h1>Guess a number...</h1>
<h:form id="numberGuess">
ml_plain"> <div style="color: red">
<h:messages id="messages" globalOnly="false"/>
<h:outputText id="Higher" value="Higher!" rendered="#{game.guessLower}"/>
<h:outputText id="Lower" value="Lower!" rendered="#{game.guessHigher}"/>
</div>
ml_plain"> <div>
I'm thinking of a number between <span id="numberGuess:smallest">#{game.smallest}</span> and <span id="numberGuess:biggest">#{game.biggest}</span>. You have #{game.remainingGuesses} guesses remaining.
</div>
<div>
ml_plain"> Your guess:
ml_plain"> <h:inputText id="inputGuess" value="#{game.guess}"
ml_plain"> required="true" size="3" disabled="#{game.guessCorrect}" validator="#{game.validateNumberRange}"/>
<h:commandButton id="guessButton" value="Guess" action="#{game.check}" disabled="#{game.guessCorrect}"/>
</div>
<div>
<h:commandButton id="restartButton" value="Reset" action="#{game.reset}" immediate="true"/>
</div>
</h:form>
</ui:define>
</ui:composition>
</html>
| Facelets is the built-in templating language for JSF. Here we are wrapping our page in a template which defines the layout. |
| There are a number of messages which can be sent to the user, "Higher!", "Lower!" and "Correct!" |
| As the user guesses, the range of numbers they can guess gets smaller - this sentence changes to make sure they know the number range of a valid guess. |
| This input field is bound to a bean property using a value expression. |
| A validator binding is used to make sure the user doesn't accidentally input a number outside of the range in which they can guess - if the validator wasn't here, the user might use up a guess on an out of bounds number. |
| And, of course, there must be a way for the user to send their guess to the server. Here we bind to an action method on the bean. |
The example consists of 4 classes, the first two of which are qualifiers. First, there is the
@Random qualifier, used for injecting a random number:
@Qualifier
@Target( { TYPE, METHOD, PARAMETER, FIELD })
@Retention(RUNTIME)
public @interface Random {}
There is also the @MaxNumber qualifier, used for
injecting the maximum number that can be injected:
@Qualifier
@Target( { TYPE, METHOD, PARAMETER, FIELD })
@Retention(RUNTIME)
public @interface MaxNumber {}
The application-scoped Generator class is responsible for creating the random number, via a
producer method. It also exposes the maximum possible number via a producer method:
@ApplicationScoped
public class Generator implements Serializable {
private java.util.Random random = new java.util.Random(System.currentTimeMillis());
private static final int MAX_NUMBER = 100;
java.util.Random getRandom() {
return random;
}
@Produces
@Random
int next() {
//a number between 1 and 100
return getRandom().nextInt(MAX_NUMBER - 1) + 1;
}
@Produces
@MaxNumber
int getMaxNumber() {
return MAX_NUMBER;
}
}
The Generator is application scoped, so we don't get a different random each time.
Note
The package declaration and imports have been excluded from these listings. The complete listing is available in the example source code.
The final bean in the application is the session-scoped Game class. This is the primary
entry point of the application. It's responsible for setting up or resetting the game, capturing and validating
the user's guess and providing feedback to the user with a FacesMessage. We've used the
post-construct lifecycle method to initialize the game by retrieving a random number from the @Random
Instance<Integer> bean.
You'll notice that we've also added the @Named annotation to this class. This annotation is
only required when you want to make the bean accessible to a JSF view via EL (i.e., #{game}).
import javax.enterprise.inject.Instance;
@Named
@SessionScoped
public class Game implements Serializable {
private static final int DEFAULT_REMAINING_GUESSES = 10;
private int number;
private int guess;
private int smallest;
private int biggest;
private int remainingGuesses;
@Inject
@MaxNumber
private int maxNumber;
@Inject
@Random
private Instance<Integer> randomNumber;
public Game() {
}
public int getNumber() {
return number;
}
public int getGuess() {
return guess;
}
public void setGuess(int guess) {
this.guess = guess;
}
public int getSmallest() {
return smallest;
}
public int getBiggest() {
return biggest;
}
public int getRemainingGuesses() {
return remainingGuesses;
}
public void check() {
if (guess > number) {
biggest = guess - 1;
} else if (guess < number) {
smallest = guess + 1;
} else if (guess == number) {
FacesContext.getCurrentInstance().addMessage(null, new FacesMessage("Correct!"));
}
remainingGuesses--;
}
@PostConstruct
public void reset() {
this.smallest = 0;
this.guess = 0;
this.remainingGuesses = DEFAULT_REMAINING_GUESSES;
this.biggest = maxNumber;
this.number = randomNumber.get();
}
public void validateNumberRange(FacesContext context, UIComponent toValidate, Object value) {
if (remainingGuesses <= 0) {
FacesMessage message = new FacesMessage("No guesses left!");
context.addMessage(toValidate.getClientId(context), message);
((UIInput) toValidate).setValid(false);
return;
}
int input = (Integer) value;
if (input < smallest || input > biggest) {
((UIInput) toValidate).setValid(false);
FacesMessage message = new FacesMessage("Invalid guess");
context.addMessage(toValidate.getClientId(context), message);
}
}
public boolean isGuessHigher() {
return guess != 0 && guess > number;
}
public boolean isGuessLower() {
return guess != 0 && guess < number;
}
public boolean isGuessCorrect() {
return guess == number;
}
}
A couple of modifications must be made to the numberguess artifact in order to deploy it to Tomcat or Jetty.
First, Weld must be deployed as a Web Application library under WEB-INF/lib since the
servlet container does not provide the CDI services. For your convenience we provide a single jar suitable
for running Weld in any servlet container (including Jetty), weld-servlet.jar.
Note
You must also include the jars for JSF, EL, and the common annotations
(jsr250-api.jar), all of which are provided by the Java EE platform (a Java EE
application server).
Second, we need to explicitly specify the servlet listener in web.xml, again because the
container isn't doing this stuff for you. The servlet listener boots Weld and controls it's interaction with
requests.
<listener>
<listener-class>org.jboss.weld.environment.servlet.Listener</listener-class>
</listener>
When Weld boots, it places the javax.enterprise.inject.spi.BeanManager, the portable SPI
for obtaining bean instances, in the ServletContext under a variable name equal to the fully-qualified
interface name. You generally don't need to access this interface, but Weld makes use of it.
This example shows how to use the Weld SE extension in a
Java SE based Swing application with no EJB or servlet
dependencies.
This example can be found in the
examples/se/numberguess
folder of the Weld distribution.
To use the Weld SE numberguess example in Eclipse, you can either import it as a Maven project if you have the m2eclipse plugin installed, or generate an Eclipse project and import it.
With m2eclipse installed, you can open any Maven project directly. From within Eclipse, select File -> Import... -> Existing Maven Projects. Then, browse to the location of the Weld SE numberguess example. You should see that Eclipse recognizes the Maven project.
Without m2eclipse plugin, you first have to generate an Eclipse project. Switch into the Weld SE numberguess example folder, then execute the Maven Eclipse plugin, as follows:
mvn eclipse:configure-workspace -Declipse.workspace=/path/to/your/eclipse/workspace
and then
mvn eclipse:eclipse
Then from within Eclipse, select File -> Import... -> Existing Projects into Workspace and browse to the location of the Weld SE numberguess example.
In both cases, you should now see a project in your workspace called weld-se-numberguess.
It's time to get the example running!
Disable m2eclipse's Workspace Resolution, to make sure that Eclipse
can find StartMain. Right click on the project, and choose
Properties -> Maven, and uncheck
Resolve dependencies from Workspace projects:
Right click on the project, and choose Run As -> Java Application:
Locate the StartMain class:
The application should now launch!
Ensure that Maven 3 is installed and in your PATH
Ensure that the
JAVA_HOMEenvironment variable is pointing to your JDK installationOpen a command line or terminal window in the
examples/se/numberguessdirectoryExecute the following command
mvn -Drun
Let's have a look at the significant code and configuration files that make up this example.
There is an empty beans.xml file in the root
package (src/main/resources/META-INF/beans.xml), which
marks this application as a CDI application.
Note
The beans.xml file is no longer required for CDI enablement as of CDI 1.1.
CDI is automatically enabled for archives which don't contain beans.xml
but contain one or more bean classes with a bean defining annotation,
as described in section Section 15.6.2, “Implicit bean archive”.
The game's main logic is located in Game.java.
Here is the code for that class, highlighting the ways in which this
differs from the web application version:
public static final int MAX_NUM_GUESSES = 10;
private Integer number;
private int guess = 0;
private int smallest = 0;
@Inject
@MaxNumber
private int maxNumber;
private int biggest;
private int remainingGuesses = MAX_NUM_GUESSES;
private boolean validNumberRange = true;
@Inject
Generator rndGenerator;
public Game() {
}
public int getNumber() {
return number;
}
public int getGuess() {
return guess;
}
public void setGuess(int guess) {
this.guess = guess;
}
public int getSmallest() {
return smallest;
}
public int getBiggest() {
return biggest;
}
public int getRemainingGuesses() {
return remainingGuesses;
}
return validNumberRange;
}
public boolean isGameWon() {
return guess == number;
}
public boolean isGameLost() {
return guess != number && remainingGuesses <= 0;
}
boolean result = false;
if (checkNewNumberRangeIsValid()) {
if (guess > number) {
biggest = guess - 1;
}
if (guess < number) {
smallest = guess + 1;
}
if (guess == number) {
result = true;
}
remainingGuesses--;
}
return result;
}
private boolean checkNewNumberRangeIsValid() {
return validNumberRange = ((guess >= smallest) && (guess <= biggest));
}
@PostConstruct
this.smallest = 0;
this.guess = 0;
this.remainingGuesses = 10;
this.biggest = maxNumber;
this.number = rndGenerator.next();
System.out.println("psst! the number is " + this.number);
}
}
| The bean is application scoped rather than session scoped, since an instance of a Swing application typically represents a single 'session'. |
| Notice that the bean is not named, since it doesn't need to be accessed via EL. |
|
In Java SE there is no JSF
This allows the Swing UI to query the state of the game,
which it does indirectly via a class called
|
|
Since there is no dedicated validation phase, validation of
user input is performed during the |
|
The |
The MessageGenerator class depends on the
current instance of Game and queries its
state in order to determine the appropriate messages to provide
as the prompt for the user's next guess and the response to the
previous guess. The code for MessageGenerator
is as follows:
public class MessageGenerator {
private Game game;
StringBuilder challengeMsg = new StringBuilder("I'm thinking of a number between ");
challengeMsg.append(game.getSmallest());
challengeMsg.append(" and ");
challengeMsg.append(game.getBiggest());
challengeMsg.append(". Can you guess what it is?");
return challengeMsg.toString();
}
if (game.isGameWon()) {
return "You guessed it! The number was " + game.getNumber();
} else if (game.isGameLost()) {
return "You are fail! The number was " + game.getNumber();
} else if (!game.isValidNumberRange()) {
return "Invalid number range!";
} else if (game.getRemainingGuesses() == Game.MAX_NUM_GUESSES) {
return "What is your first guess?";
} else {
String direction = null;
if (game.getGuess() < game.getNumber()) {
direction = "Higher";
} else {
direction = "Lower";
}
return direction + "! You have " + game.getRemainingGuesses() + " guesses left.";
}
}
}
|
The instance of |
|
The |
| ... and again to determine whether to congratulate, console or encourage the user to continue. |
Finally we come to the NumberGuessFrame class
which provides the Swing front end to our guessing game.
import javax.enterprise.event.Observes;
public class NumberGuessFrame extends javax.swing.JFrame {
@Inject
@Inject
java.awt.EventQueue.invokeLater(new Runnable() {
public void run() {
initComponents();
setVisible(true);
}
});
}
borderPanel = new javax.swing.JPanel();
gamePanel = new javax.swing.JPanel();
inputsPanel = new javax.swing.JPanel();
buttonPanel = new javax.swing.JPanel();
guessButton = new javax.swing.JButton();
...
mainLabel.setText(msgGenerator.getChallengeMessage());
mainMsgPanel.add(mainLabel);
messageLabel.setText(msgGenerator.getResultMessage());
mainMsgPanel.add(messageLabel);
...
}
int guess = -1;
try {
guess = Integer.parseInt(guessText.getText());
} catch (NumberFormatException nfe) {
// noop
}
game.setGuess(guess);
game.check();
refreshUI();
if (game.isGameWon() || game.isGameLost()) {
switchButtons();
}
}
game.reset();
refreshUI();
switchButtons();
}
private void switchButtons() {
CardLayout buttonLyt = (CardLayout) buttonPanel.getLayout();
buttonLyt.next(buttonPanel);
}
private void refreshUI() {
mainLabel.setText(msgGenerator.getChallengeMessage());
messageLabel.setText(msgGenerator.getResultMessage());
guessText.setText("");
guessesLeftBar.setValue(game.getRemainingGuesses());
guessText.requestFocus();
}
// swing components
private javax.swing.JPanel borderPanel;
...
private javax.swing.JButton replayBtn;
}
| The injected instance of the game (logic and state). |
| The injected message generator for UI messages. |
|
This application is started in the prescribed Weld SE way,
by observing the |
|
This method initializes all of the Swing components. Note
the use of the |
|
|
|
|
The translator example will take any sentences you enter, and translate them to Latin. (Well, not really, but the stub is there for you to implement, at least. Good luck!)
The translator example is built as an EAR and contains EJBs. As a result, it's structure is more complex than the numberguess example.
Note
Java EE 7, which bundles EJB 3.2, allows you to package EJBs in a WAR, which will make this structure much simpler! Still, there are other advantages of using an EAR.
First, let's take a look at the EAR aggregator project, which is located in the example's ear directory. Maven
automatically generates the application.xml for us from this plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<configuration>
<modules>
<webModule>
<groupId>org.jboss.weld.examples.jsf.translator</groupId>
<artifactId>weld-jsf-translator-war</artifactId>
<contextRoot>/weld-translator</contextRoot>
</webModule>
</modules>
</configuration>
</plugin>
This configuration overrides the web context path, resulting in this application URL: http://localhost:8080/weld-translator.
Note
If you weren't using Maven to generate these files, you would need
META-INF/application.xml:
<application version="7"
xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="
http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/application_7.xsd">
<display-name>weld-jsf-translator-ear</display-name>
<description>The Weld JSF translator example (ear)</description>
<module>
<web>
<web-uri>weld-translator.war</web-uri>
<context-root>/weld-translator</context-root>
</web>
</module>
<module>
<ejb>weld-translator.jar</ejb>
</module>
</application>
Next, let's look at the WAR, which is located in the example's war directory. Just as in the
numberguess example, we have a faces-config.xml for JSF 2.2 and a web.xml
(to activate JSF) under WEB-INF, both sourced from src/main/webapp/WEB-INF.
More interesting is the JSF view used to translate text. Just as in the numberguess example we have a template, which surrounds the form (omitted here for brevity):
<h:form id="TranslatorMain">
<table>
<tr align="center" style="font-weight: bold">
<td>
Your text
</td>
<td>
Translation
</td>
</tr>
<tr>
<td>
<h:inputTextarea id="text" value="#{translator.text}" required="true" rows="5" cols="80"/>
</td>
<td>
<h:outputText value="#{translator.translatedText}"/>
</td>
</tr>
</table>
<div>
<h:commandButton id="button" value="Translate" action="#{translator.translate}"/>
</div>
</h:form>
The user can enter some text in the left-hand text area, and hit the translate button to see the result to the right.
Finally, let's look at the EJB module, which is located in the example's ejb directory. In
src/main/resources/META-INF there is just an empty beans.xml, used to
mark the archive as containing beans.
Note
The beans.xml file is no longer required for CDI enablement as of CDI 1.1.
CDI is automatically enabled for archives which don't contain beans.xml
but contain one or more bean classes with a bean defining annotation,
as described in section Section 15.6.2, “Implicit bean archive”.
We've saved the most interesting bit for last, the code! The project has two simple beans,
SentenceParser and TextTranslator and two session beans,
TranslatorControllerBean and SentenceTranslator. You should be getting
quite familiar with what a bean looks like by now, so we'll just highlight the most interesting bits here.
Both SentenceParser and TextTranslator are dependent beans, and
TextTranslator uses constructor injection:
public class TextTranslator implements Serializable {
private SentenceParser sentenceParser;
@EJB private Translator translator;
@Inject public TextTranslator(SentenceParser sentenceParser) {
this.sentenceParser = sentenceParser;
}
public String translate(String text) {
StringBuilder sb = new StringBuilder();
for (String sentence: sentenceParser.parse(text)) {
sb.append(translator.translate(sentence)).append(". ");
}
return sb.toString().trim();
}
}
TextTranslator uses the simple bean (really just a plain Java class!)
SentenceParser to parse the sentence and then calls on the stateless bean with the local
business interface Translator to perform the translation. That's where the magic happens.
Of course, we couldn't develop a full translator, but it's convincing enough to anyone who doesn't understand
Latin!
@Stateless
public class SentenceTranslator implements Translator {
public String translate(String sentence) {
return "Lorem ipsum dolor sit amet";
}
}
Finally, there is UI orientated controller. This is a request scoped, named, stateful session bean, which injects the translator. It collects the text from the user and dispatches it to the translator. The bean also has getters and setters for all the fields on the page.
@Stateful
@RequestScoped
@Named("translator")
public class TranslatorControllerBean implements TranslatorController {
@Inject private TextTranslator translator;
private String inputText;
private String translatedText;
public void translate() {
translatedText = translator.translate(inputText);
}
public String getText() {
return inputText;
}
public void setText(String text) {
this.inputText = text;
}
public String getTranslatedText() {
return translatedText;
}
@Remove public void remove() {}
}
That concludes our short tour of the Weld starter examples. For more information on Weld, please visit http://weld.cdi-spec.org/.