From Wikipedia, the free encyclopedia

A Java package is a mechanism for organizing Java classes into namespaces. Java packages can be stored in compressed files called JAR files, allowing classes to download faster as a group rather than one at a time. Programmers also typically use packages to organize classes belonging to the same category or providing similar functionality.

Java source files can include a package statement at the top of the file to designate the package for the classes the source file defines.

• A package provides a unique namespace for the types it contains.
• Classes in the same package can access each other's protected members.
• A package can contain the following kinds of types.
  • Classes
  • Interfaces
  • Enumerated types
  • Annotations

Contents 1 Using packages 2 Package access protection 3 Creation of JAR files 4 Package naming conventions 5 Core packages in J2SE 6.0 6 See also 7 External links

In Java source files, the package that the file belongs to is specified with the package keyword.

package java.awt.event;

To use a package inside a Java source file, it is convenient to import the classes from the package with an import statement. The statement

import java.awt.event.*;

imports all classes from the java.awt.event package, while

import java.awt.event.ActionEvent;

imports only the ActionEvent class from the package. After either of these import statements, the ActionEvent class can be referenced using its simple class name:

ActionEvent myEvent = new ActionEvent();

Classes can also be used directly without an import statement by using the fully-qualified name of the class. For example,

java.awt.event.ActionEvent myEvent = new java.awt.event.ActionEvent();

doesn't require a preceding import statement.

Classes within a package can access classes and members declared with default access and class members declared with the protected access modifier. Default access is enforced when neither the public, protected nor private access modifier is specified in the declaration. By contrast, classes in other packages cannot access classes and members declared with default access. Class members declared as protected can only be accessed from within classes in other packages that are subclasses of the declaring class.

JAR Files are created with the jar command-line utility. The command

jar cf myPackage.jar *.class

compresses all *.class files into the JAR file myPackage.jar. The ' c ' option on the command line tells the jar command to "create new archive." The ' f ' option should be placed just before the file name of the JAR file being created.

Packages are usually defined using a hierarchical naming pattern, with levels in the hierarchy separated by periods (.) (pronounced "dot"). Although packages lower in the naming hierarchy are often referred to a "subpackages" of the corresponding packages higher in the hierarchy, there is no semantic relationship between packages. The Java Language Specification establishes package naming conventions in order to avoid the possibility of two published packages having the same name. The naming conventions describe how to create unique package names, so that packages that are widely distributed will have unique namespaces. This allows packages to be easily and automatically installed and catalogued.

In general, a package name begins with the top level domain name of the organization and then the organization's domain and then any subdomains listed in reverse order. The organization can then choose a specific name for their package. Package names should be all lowercase characters whenever possible.

For example, if an organization in Canada called MySoft creates a package to deal with fractions, naming the package ca.mysoft.fractions distinguishes the fractions package from another similar package created by another company. If a US company named MySoft also creates a fractions package, but names it com.mysoft.fractions, then the classes in these two packages are defined in a unique and separate namespace.

Complete conventions for disambiguating package names and rules for naming packages when the Internet domain name cannot be directly used as a package name are described in section 7.7 of the Java Language Specification.

Main article: Java Platform, Standard Edition

java.lang	— basic language functionality and fundamental types
java.util	— collection data structure classes
java.io	— file operations
java.math	— multiprecision arithmetics
java.nio	— the New I/O framework for Java
java.net	— networking operations, sockets, DNS lookups, ...
java.security	— key generation, encryption and decryption
java.sql	— Java Database Connectivity (JDBC) to access databases
java.awt	— basic hierarchy of packages for native GUI components
javax.swing	— hierarchy of packages for platform-independent rich GUI components

• JAR (file format)
• Classpath (Java)
• Apache Harmony

• Java SE 6 API Javadocs
• Java Language Specification, 3rd edition: Unique Package Names
• Java Package Naming Conventions