Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Transitioning to Java
  • Toc
  • feedback
Transitioning to Java

Transitioning to Java

By : Ken Fogel
4.8 (6)
close
Transitioning to Java

Transitioning to Java

4.8 (6)
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)
close
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

Documentation and Logging

In this chapter, we will look at two aspects of software development that do not directly influence the operation of the code. The first is documentation, more commonly called comments. The second is logging, a tool used to record events during the run of a program for the purpose of monitoring what the program is doing. We will begin with documenting code inline. You likely noticed that none of the code shown so far in this book has any comments. This has been done on purpose, as each chapter describes what the code is doing. If you look at the book’s code in the GitHub repository, you will find comments in every file.

You have probably seen a message telling you to look at the log file when something goes wrong in a program. Where do these log files come from? We will examine how we can either display messages on the console or write to a file that certain events occurred or exceptions were thrown.

Here is the rundown for this chapter:

    ...
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete