Java SE

This category will hold articles for Java SE and Eclipse.

I think Java can be a lot of fun, since it already delivers a lot out of the box.

People who develop Java APIs usually give it a lot of thinking and work.


Java EE in comparison to Java SE can be described as a huge collection of Frameworks and API developed around Java SE.

Java EE is not a stand-alone programming language, but based on Java SE.

Understanding Ant

First things first. You need to understand Ant build files and how Ant is working in general. If you do not also using any automation offered by tools like eclipse will not get you very far. Therefore I suggest to read through the tutorial linked below or to consult other resources before you start working with Ant. You might have some fast advantages using Ant without understanding it but you will miss the big picture and sooner or later run into problems.

So far I have always received connection details for oracle databases providing me with the SID, which gives you the name of a database.

Using an SID in the SQL Developer configuration is working fine, but using the same configuration using the SID name in a JDBC oracle connection String as a service name will not work.

At first attempt I many times came across the following sql exception (below a link to a short explanation on

ORA-12514 TNS:listener does not currently know of service requested in connect descriptor

Every time this happened I had to either adjust an oracle specific file called tnsames.ora, which contains configuration details for services registered with an oracle database or change the connection String to use the actual service name instead of the SID.

When coding a rich client application in Java SE sooner or later you will have to think about how to lay out your application.

In most cases you will come to the conclusion to lay it out as everyone else does.

  1. MenuBar for all functions.
  2. ToolBar for more commonly used functions.
  3. Controls, which are layed out in a more custom way fitting your needs.

In order to have something ready to start with when I want to lay out the controls of an application I suggest below approach.

Use a BorderPane as root node. In the Top area of a BorderPane you can place a VBox. In this VBox you can place your MenuBar as well as a ToolBar or only a MenuBar.

In the Center area of a BorderPane you can place another layout like a GridPane for high flexibility or a SplitPane to have to separated areas in a BorderPanes Center area.

Enough talk, here is the source as well as an Oracle article that helped me.

MenuBar, ToolBar and Controls in GridPane

import javafx.application.Application;
import javafx.event.ActionEvent;
import javafx.event.EventHandler;
import javafx.geometry.Insets;
import javafx.geometry.Pos;
import javafx.scene.Scene;
import javafx.scene.control.Button;
import javafx.scene.control.Menu;
import javafx.scene.control.MenuBar;
import javafx.scene.control.MenuItem;
import javafx.scene.control.ToolBar;
import javafx.scene.layout.BorderPane;
import javafx.scene.layout.GridPane;
import javafx.scene.layout.VBox;
import javafx.stage.Stage;

public class Main extends Application {
public void start(Stage primaryStage) {
try {
/* Create a new MenuBar. */
MenuBar menu = new MenuBar();
/* Create new sub menus. */
Menu menuFile = new Menu("File");
Menu menuHelp = new Menu("Help");
MenuItem about = new MenuItem("About");
about.setOnAction(new EventHandler<ActionEvent>() {
public void handle(ActionEvent event) {
* Implement dialog to be prompted when users asks for
* details.

/* Adding all sub menus at ones to a MenuBar. */
menu.getMenus().addAll(menuFile, menuHelp);

/* Create a button. */
Button btn = new Button();
btn.setText("Say Hello World.");
btn.setOnAction(new EventHandler<ActionEvent>() {
public void handle(ActionEvent event) {
System.out.println("Hello World!");

/* Create a new ToolBar. */
ToolBar tools = new ToolBar(btn);

/* Create a new VBox and add the menu as well as the tools. */
VBox menus = new VBox();
menus.getChildren().addAll(menu, tools);

/* Create a flexible layout. */
GridPane contentPane = new GridPane();
/* Setting the alignment of controls WITHIN a pane. */
contentPane.setPadding(new Insets(25, 25, 25, 25));

/* Create a root node as BorderPane. */
BorderPane root = new BorderPane();

/* Adding the menus as well as the content pane to the root node. */

* Setting the root node of a scene as well as the applications CSS
* file. CSS file has to be in same src directory as this class. The
* path is always relative.
Scene scene = new Scene(root, 800, 600);

/* Adding a scene to the stage. */

/* Lift the curtain :0). */;
} catch (Exception e) {

public static void main(String[] args) {



This category provides articles regarding JavaFX as well as e(fx)clipse as this seems to be a good start to deal with JavaFX.

JavaFX has been around for some time now and Oracle is currently triying to enforce it as new standard for Java Rich Client Applications.

Regarding to a developer I know it has had some improvements over the years and it looks like it is going to be a try out worthy successor of AWT (Java), Swing (Java) and SWT (IBM).

However Oracle is trying to push this somewhat new technology into the market for some time now, it has not yet been accepted by the Java community.

Root cause for this seem to be the following reasons.

  • Companies are not asking for Rich Client Applications, but there is a trend for developing Web Applications. Therefore motivation to use anything like AWT, Swing, SWT or JavaFX is low except for private purposes. However JavaFX supports Mobile Applications, which is a big market. Since integration with mobiles is asked by companies as well for web applications and older technologies not supporting it, I can understand Oracle not wanting to provide support for it anymore.
  • Programmers are lazy. If you give them something completely new to learn, it takes quite an effort to get to a stage where you are as fast as using already known technologies. The standard platform for Java development, eclipse is still not providing the same comfortable "what you see is waht you get editors" for JavaFX as it is providing for the older technologies. Until eclipse is not deprecating support for Swing and older technologies like SWT and AWT they will be used by programmers.

I did some research one the internet regarding JavaFX so far but I will try to write more articles in the future about it as I intend to write little tools for myself in Java. For this I of course do not want the hustle of maintaining a JEE server all the time. Therefore JavaFX is intersting for me but I am far from beeing an expert, so try it yourself.

Groups articles regarding eclipse SWT.

A category to collect articles around Apache POI.

Java Architecture for XML Binding (JAXB) provides a fast and convenient way to bind XML schemas and Java representations, making it easy for Java developers to incorporate XML data and processing functions in Java applications. As part of this process, JAXB provides methods for unmarshalling (reading) XML instance documents into Java content trees, and then marshalling (writing) Java content trees back into XML instance documents. JAXB also provides a way to generate XML schema from Java objects.