Book Image

Transitioning to Java

By : Ken Fogel
Book Image

Transitioning to Java

By: Ken Fogel

Overview of this book

This comprehensive guide will help non-Java developers already using different languages transition from their current language to all things Java. The chapters are designed in a way that re-enforces a developer’s existing knowledge of object-oriented methodologies as they apply to Java. This book has been divided into four sections, with each section touching upon different aspects that’ll enable your effective transition. The first section helps you get to grips with the Java development environment and the Maven build tool for modern Java applications. In the second section, you’ll learn about Java language fundamentals, along with exploring object-oriented programming (OOP) methodologies and functional programming and discovering how to implement software design patterns in Java. The third section shows you how to code in Java on different platforms and helps you get familiar with the challenges faced on these platforms. In the fourth section, you’ll find out how you can manage and package your Java code. By the end of this Java programming book, you’ll have learned the core concepts of Java that’ll help you successfully transition from a different language to Java.
Table of Contents (23 chapters)
1
Part 1:The Java Development Environment
5
Part 2:Language Fundamentals
15
Part 3:GUI and Web Coding in Java
19
Part 4:Packaging Java Code

The two-step compile and execute process – javac and java/javaw

The most common approach to running a Java program involves two steps. First, you must compile the code with javac and then execute the code in the Java Virtual Machine (JVM) with Java or on Windows with javaw.

The first step of preparing Java source code for execution is to compile it into bytecode. This is the machine language of the JVM. Every Java source file that is part of an application must be compiled into bytecode.

The second step is to execute the bytecode in a JVM. Unlike C or C++, there is no link step. The link step combines all compiled code into a single executable file. In Java, all the bytecode files must be on the classpath, which is the path to all bytecode files, and not necessarily combined into a single file. This may seem confusing as there is a tool called jlink, but its purpose is to combine the Java runtime with your code so that the end user does not need the Java version that...