- GUI
- Windows API tutorial
- Introduction to Windows API
- Windows API main functions
- System functions in Windows API
- Strings in Windows API
- Date & time in Windows API
- A window in Windows API
- First steps in UI
- Windows API menus
- Windows API dialogs
- Windows API controls I
- Windows API controls II
- Windows API controls III
- Advanced controls in Windows API
- Custom controls in Windows API
- The GDI in Windows API
- PyQt4 tutorial
- PyQt5 tutorial
- Qt4 tutorial
- Introduction to Qt4 toolkit
- Qt4 utility classes
- Strings in Qt4
- Date and time in Qt4
- Working with files and directories in Qt4
- First programs in Qt4
- Menus and toolbars in Qt4
- Layout management in Qt4
- Events and signals in Qt4
- Qt4 Widgets
- Qt4 Widgets II
- Painting in Qt4
- Custom widget in Qt4
- The Breakout game in Qt4
- Qt5 tutorial
- Introduction to Qt5 toolkit
- Strings in Qt5
- Date and time in Qt5
- Containers in Qt5
- Working with files and directories in Qt5
- First programs in Qt5
- Menus and toolbars in Qt5
- Layout management in Qt5
- Events and signals in Qt5
- Qt5 Widgets
- Qt5 Widgets II
- Painting in Qt5
- Custom widget in Qt5
- Snake in Qt5
- The Breakout game in Qt5
- PySide tutorial
- Tkinter tutorial
- Tcl/Tk tutorial
- Qt Quick tutorial
- Java Swing tutorial
- JavaFX tutorial
- Java SWT tutorial
- wxWidgets tutorial
- Introduction to wxWidgets
- wxWidgets helper classes
- First programs in wxWidgets
- Menus and toolbars in wxWidgets
- Layout management in wxWidgets
- Events in wxWidgets
- Dialogs in wxWidgets
- wxWidgets widgets
- wxWidgets widgets II
- Drag and Drop in wxWidgets
- Device Contexts in wxWidgets
- Custom widgets in wxWidgets
- The Tetris game in wxWidgets
- wxPython tutorial
- Introduction to wxPython
- First Steps
- Menus and toolbars
- Layout management in wxPython
- Events in wxPython
- wxPython dialogs
- Widgets
- Advanced widgets in wxPython
- Drag and drop in wxPython
- Internationalisation
- Application skeletons in wxPython
- The GDI
- Mapping modes
- Creating custom widgets
- Tips and Tricks
- wxPython Gripts
- The Tetris game in wxPython
- C# Winforms Mono tutorial
- Java Gnome tutorial
- Introduction to Java Gnome
- First steps in Java Gnome
- Layout management in Java Gnome
- Layout management II in Java Gnome
- Menus in Java Gnome
- Toolbars in Java Gnome
- Events in Java Gnome
- Widgets in Java Gnome
- Widgets II in Java Gnome
- Advanced widgets in Java Gnome
- Dialogs in Java Gnome
- Pango in Java Gnome
- Drawing with Cairo in Java Gnome
- Drawing with Cairo II
- Nibbles in Java Gnome
- QtJambi tutorial
- GTK+ tutorial
- Ruby GTK tutorial
- GTK# tutorial
- Visual Basic GTK# tutorial
- PyGTK tutorial
- Introduction to PyGTK
- First steps in PyGTK
- Layout management in PyGTK
- Menus in PyGTK
- Toolbars in PyGTK
- Signals & events in PyGTK
- Widgets in PyGTK
- Widgets II in PyGTK
- Advanced widgets in PyGTK
- Dialogs in PyGTK
- Pango
- Pango II
- Drawing with Cairo in PyGTK
- Drawing with Cairo II
- Snake game in PyGTK
- Custom widget in PyGTK
- PHP GTK tutorial
- C# Qyoto tutorial
- Ruby Qt tutorial
- Visual Basic Qyoto tutorial
- Mono IronPython Winforms tutorial
- Introduction
- First steps in IronPython Mono Winforms
- Layout management
- Menus and toolbars
- Basic Controls in Mono Winforms
- Basic Controls II in Mono Winforms
- Advanced Controls in Mono Winforms
- Dialogs
- Drag & drop in Mono Winforms
- Painting
- Painting II in IronPython Mono Winforms
- Snake in IronPython Mono Winforms
- The Tetris game in IronPython Mono Winforms
- FreeBASIC GTK tutorial
- Jython Swing tutorial
- JRuby Swing tutorial
- Visual Basic Winforms tutorial
- JavaScript GTK tutorial
- Ruby HTTPClient tutorial
- Ruby Faraday tutorial
- Ruby Net::HTTP tutorial
- Java 2D games tutorial
- Java 2D tutorial
- Cairo graphics tutorial
- PyCairo tutorial
- HTML5 canvas tutorial
- Python tutorial
- Python language
- Interactive Python
- Python lexical structure
- Python data types
- Strings in Python
- Python lists
- Python dictionaries
- Python operators
- Keywords in Python
- Functions in Python
- Files in Python
- Object-oriented programming in Python
- Modules
- Packages in Python
- Exceptions in Python
- Iterators and Generators
- Introspection in Python
- Ruby tutorial
- PHP tutorial
- Visual Basic tutorial
- Visual Basic
- Visual Basic lexical structure
- Basics
- Visual Basic data types
- Strings in Visual Basic
- Operators
- Flow control
- Visual Basic arrays
- Procedures & functions in Visual Basic
- Organizing code in Visual Basic
- Object-oriented programming
- Object-oriented programming II in Visual Basic
- Collections in Visual Basic
- Input & output
- Tcl tutorial
- C# tutorial
- Java tutorial
- AWK tutorial
- Jetty tutorial
- Tomcat Derby tutorial
- Jtwig tutorial
- Android tutorial
- Introduction to Android development
- First Android application
- Android Button widgets
- Android Intents
- Layout management in Android
- Android Spinner widget
- SeekBar widget
- Android ProgressBar widget
- Android ListView widget
- Android Pickers
- Android menus
- Dialogs
- Drawing in Android
- Java EE 5 tutorials
- Introduction
- Installing Java
- Installing NetBeans 6
- Java Application Servers
- Resin CGIServlet
- JavaServer Pages, (JSPs)
- Implicit objects in JSPs
- Shopping cart
- JSP & MySQL Database
- Java Servlets
- Sending email in a Servlet
- Creating a captcha in a Servlet
- DataSource & DriverManager
- Java Beans
- Custom JSP tags
- Object relational mapping with iBATIS
- Jsoup tutorial
- MySQL tutorial
- MySQL quick tutorial
- MySQL storage engines
- MySQL data types
- Creating, altering and dropping tables in MySQL
- MySQL expressions
- Inserting, updating, and deleting data in MySQL
- The SELECT statement in MySQL
- MySQL subqueries
- MySQL constraints
- Exporting and importing data in MySQL
- Joining tables in MySQL
- MySQL functions
- Views in MySQL
- Transactions in MySQL
- MySQL stored routines
- MySQL Python tutorial
- MySQL Perl tutorial
- MySQL C API programming tutorial
- MySQL Visual Basic tutorial
- MySQL PHP tutorial
- MySQL Java tutorial
- MySQL Ruby tutorial
- MySQL C# tutorial
- SQLite tutorial
- SQLite C tutorial
- SQLite PHP tutorial
- SQLite Python tutorial
- SQLite Perl tutorial
- SQLite Ruby tutorial
- SQLite C# tutorial
- SQLite Visual Basic tutorial
- PostgreSQL C tutorial
- PostgreSQL Python tutorial
- PostgreSQL Ruby tutorial
- PostgreSQL PHP tutorial
- PostgreSQL Java tutorial
- Apache Derby tutorial
- SQLAlchemy tutorial
- MongoDB PHP tutorial
- MongoDB Java tutorial
- MongoDB JavaScript tutorial
- MongoDB Ruby tutorial
- Spring JdbcTemplate tutorial
- JDBI tutorial
Packages
In this part of the Java tutorial, we will talk about Java packages.
A package is a grouping of related types providing access protection and name space management. Packages in Java is a similar concept to namespaces in C#.
A package is declared with the package
keyword. This statement must be placed at the top of every source file. There can be only one such statement in each source file. The Java source files must be placed in directories that match the package name.
package com.zetcode;
All types defined in the file with the above package are part of the com.zetcode package. A class Being
has a fully qualified name com.zetcode.Being
. There are millions of Java programmers worldwide. To avoid potential name conflicts, there is a naming convention in Java. The package names reversed Internet domain names. The letters are written in lowercase. There can be only one zetcode.com
domain name so using a reversed name com.zetcode
for the packages will make them unique. A Java source file with a com.zetcode
package must be located in the com/zetcode
subdirectory.
The import
keyword is used at the beginning of a source file to specify types (classes, interfaces, enumerations, annotations) or entire Java packages to be referred to later without including their package names in the reference. Since Java SE 5.0, import statements can import static members of a class (methods and variables).
import java.awt.*;
Using the * wildcard character, we can import the whole package at a time. After this import, we can refer to all types of the java.awt package without their fully qualified names.
import java.awt.event.*;
The java.awt.event
subpackage is not imported with the java.awt.*
import. Subpackages must be imported independently.
package com.zetcode; import java.util.Random; public class Packages { public static void main(String[] args) { Random r = new Random(); int x = r.nextInt(); System.out.println(x); java.util.Calendar c = java.util.Calendar.getInstance(); System.out.println(c.getTime()); } }
The example uses two types. The Random
class and the Calendar
class. The first class is imported and the second is referred by its fully qualified name.
package com.zetcode;
We declare a package with the package
keyword. The Packages.java
file must be located in the com/zetcode
subdirectory.
import java.util.Random;
This code line enables us to use the Random
class without the package name.
Random r = new Random();
Here we use the Random
without using its full name.
java.util.Calendar c = java.util.Calendar.getInstance();
If we did not use the import
keyword on a type, we can refer to it only by its full name - java.util.Calendar
in our case. The import
keyword saves a lot of typing.
$ ls com/zetcode/ Packages.java
The Packages.java
source file is placed in the com/zetcode
subdirectory. The package name must reflect the directory structure.
$ javac com/zetcode/Packages.java
We compile the source file with the javac
tool. The tool is called from the parent directory of the com/zetcode
directory.
$ java com.zetcode.Packages 928256084 Sun Jul 21 15:01:14 CEST 2013
This is the output of the com.zetcode.Packages
program.
Package-private visibility
If we do not specify any access modifier (e.g. private
, protected
, or public
), we have a package-private visibility. In such a case, variables and methods are accessible within the same package. Classes in other packages cannot access classes and members declared with package-private access.
Default package
If no package is declared, all types defined in that file are part of a default unnamed package. It is recommended to always place your types in a package. Even for small programs.
public class DefaultPackage { public static void main(String[] args) { System.out.println("A class in a default package"); } }
The DefaultPackage
class is part of the default package.
$ ls DefaultPackage.java
If we do not specify a package, we do not place the source file in a specific subdirectory.
$ javac DefaultPackage.java $ java DefaultPackage A class in a default package
We compile the code and run the application. The source file and the bytecode is located in the current working directory.
Automatic imports
Java compiler automatically imports two packages. The java.lang
package and the current package.
Constants.java
package com.zetcode; public class Constants { public static final String version = "1.0"; }
The Constants
class is located in the same package as the AutomaticImports
which is referring to its version member.
AutomaticImports.java
package com.zetcode; public class AutomaticImports { public static void main(String[] args) { String os = System.getProperty("os.name"); System.out.println(os); System.out.println(Constants.version); } }
In this example, we refer to some classes that are automatically imported by Java compiler.
String os = System.getProperty("os.name");
The String
and System
classes are part of the java.lang
package.
System.out.println(Constants.version);
The Constants
class is located in the same package as the AutomaticImports
class. Therefore, we can access the class and its member without using the fully qualified name or utilizing the import
keyword.
$ ls com/zetcode/ AutomaticImports.java Constants.java
Both AutomaticImports.java
and Constants.java
files are located in the same subdirectory.
$ javac com/zetcode/AutomaticImports.java com/zetcode/Constants.java
Both files are compiled.
$ java com.zetcode.AutomaticImports Linux 1.0
This is a sample output of the com.zetcode.AutomaticImports
program.
Static imports
If we often use some static members, we can use import static
statement to refer to them later without a full class name. Static imports should be used with caution.
package com.zetcode; import static java.lang.Math.E; import static java.lang.Math.PI; import static java.lang.Math.abs; public class StaticImport { public static void main(String[] args) { System.out.println(E); System.out.println(PI); System.out.println(abs(-5)); } }
In this example, we refer to two constants and one static method.
import static java.lang.Math.E; import static java.lang.Math.PI; import static java.lang.Math.abs;
We use the import static
statement to enable referring to them without their full names.
System.out.println(E); System.out.println(PI); System.out.println(abs(-5));
We refer to these three members without their class name.
$ java com.zetcode.StaticImport 2.718281828459045 3.141592653589793 5
This is the output of the com.zetcode.StaticImport
program.
This chapter covered packages in Java.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论