Statements in a program are generally executed in a sequential manner, which is called sequential execution or sequential control flow. However, by putting the decision-making statement in the program, the normal flow of the program can be controlled. Statements that control the flow of the program are called control statements.

This program will help you enhance your mouse event concepts in Java. As the title indicates you will be playing with a brush after you go through the tutorial.

GUIs are generally designed with a model-view-controller architecture in which the view is decoupled from the model. The separation presents a challenge to automated testing because it's difficult to verify that a state change in the model is reflected appropriately in the view -- it spawns the infamous "Liar View." This installment of Diagnosing Java Code examines the Liar View bug pattern.

This article takes a new look at UPC symbols and bar codes, and describes how you can use Java to read information from a UPC bar code. The authors explain how to expedite and organize your enterprise operations that revolve around an IBM DB2 database. The sample application described in the article includes downloadable code.

Java 2D may be the most obvious solution for programming 2D graphs in Java programs, but it's not the only one. In this article, you will learn an elegant alternative in the form of Java Objects for Science (JSci), an open-source package that lets you create 2D bar graphs, pie charts, and line graphs in Swing. For most Java developers, any type of graphics development is intrinsically bound up with the Java 2D and 3D APIs and java.awt.Graphics. While the Java 2D and 3D APIs provide an excellent tool for creating graphics in Swing, they aren't the only ones at your disposal, and they certainly aren't the easiest ones to learn. And for those of you who don't have the time, need, or inclination to burn the midnight oil getting to know java.awt.Graphics intimately, I propose an open-source alternative: JSci.

Project JXTA is a community-run attempt to build a utility application substrate for peer-to-peer applications. The initial reference implementation of JXTA includes a command-line shell that allows experimentation with the core JXTA platform without programming. In this second installment in a three-part series, Sing Li takes us through a hands-on tour of the JXTA shell. You'll explore its command set and extend its capability by writing your own custom commands using the Java programming language. The JXTA command shell is the very first JXTA application that most JXTA developers will encounter. In fact, the JXTA development kit includes the shell as the default application. This is done for a very good reason: you can gain an appreciation of the components that make up the JXTA platform via the shell -- without writing a single line of code. The shell is a command-line tool that is similar to the familiar UNIX or DOS shell and makes extensive use of environment variables. In this installment of our series, you will become familiar with the essential commands of this versatile shell and learn how to enhance its capability by writing your own commands.

Google uses SOAP and WSDL standards to allow access from most programming languages. In addition to the SOAP access, Google has created a set of Java wrapper classes that encapsulates access to the Google Web APIs. This tutorial discusses the Java classes and the functionality of the Google web services

Loops allow you to run code multiple times

Paul Monday continues his three-part series on building resource management applications with a look at the Web-Based Enterprise Management (WBEM) initiative. WBEM serves to standardize the description and use of managed resources in enterprise networks. Follow along as Paul describes the components that comprise WBEM, and practice using the technology with a simple filesystem example. WBEM, which started as an industry initiative in 1996, standardizes the description and use of managed resources in enterprise networks. Individual companies provide their own implementations of WBEM, each of which must conform to the specifications put out by the DMTF. All WBEM-compliant technologies must accept the standardized schemas that are published by the DMTF and all associated CIMOMs must be accessible via the standard XML API.

Learn the basics of class and object oriented programming.