Preface

This book provides a specification of the Java trademark Servlet API for the Java Card 3 Platform, Connected Edition. This specification is a subset of the Java Servlet Specification, Version 2.4. For information on the differences between the two specifications, see Section 1.4, Compatibility With Java Servlet Specification Version 2.4. In this book, Java Card 3 Platform refers to both versions 3.0 and 3.0.1 to distinguish them from all earlier versions.

Before You Read This Specification

To fully use the information in this document, you must have thorough knowledge of the topics discussed in the Java Servlet Specification, Version 2.4.

Before reading this guide, you should be familiar with the Java programming language, the other Java Card technology specifications, and smart card technology. A good resource for becoming familiar with Java technology and Java Card technology is the Sun Microsystems, Inc. web site, located at

http://java.sun.com

You should also be familiar with the Java Card technology web site at

http://java.sun.com/products/javacard/

How This Document Is Organized

Chapter 1 describes the architecture of the Java Card 3 Platform, Connected Edition.

Chapter 2 briefly describes the two application models.

Chapter 3 describes the web application environment in more depth.

Chapter 4 describes the APDU-based application environment in more depth.

Chapter 5 describes card initialization and start-up.

Chapter 6 describes security and access control mechanisms.

Chapter 7 describes inter-application communication.

Chapter 8 describes card management.

Chapter 9 describes web applications.

Chapter 10 describes events.

Chapter 11 describes request mappings.

Chapter 12 describes security issues.

Chapter 13 describes how to use deployment descriptors.

Glossary provides definitions of selected terms used in the entire Connected Edition.

Using UNIX Commands

This document might not contain information about basic UNIX^® commands and procedures such as shutting down the system, booting the system, and configuring devices. Refer to the following for this information:

Software documentation that you received with your system

Solaris Operating System documentation, which is at:

http://docs.sun.com

Shell Prompts

Shell	Prompt
C shell	machine-name`%`
C shell superuser	machine-name`#`
Bourne shell and Korn shell	`$`
Bourne shell and Korn shell superuser	`#`

Typographic Conventions

Typeface`^[1]`	Meaning	Examples
`AaBbCc123`	The names of commands, files, and directories; on-screen computer output	Edit your`.login` file. Use `ls` `-a` to list all files. `% You have mail`.
`AaBbCc123`	What you type, when contrasted with on-screen computer output	`%` `su` `Password:`
AaBbCc123	Book titles, new words or terms, words to be emphasized. Replace command-line variables with real names or values.	Read Chapter 6 in the User’s Guide. These are called class options. You must be superuser to do this. To delete a file, type `rm` filename.

Typeface^[1]

Meaning

Examples

AaBbCc123

The names of commands, files, and directories; on-screen computer output

Edit your.login file.

Use ls -a to list all files.

% You have mail.

AaBbCc123

What you type, when contrasted with on-screen computer output

% su

Password:

AaBbCc123

Book titles, new words or terms, words to be emphasized. Replace command-line variables with real names or values.

Read Chapter 6 in the User’s Guide.

These are called class options.

You must be superuser to do this.

To delete a file, type rm filename.

Documentation, Support, and Training

Sun Function	URL
Documentation	`http://www.sun.com/documentation/`
Support	`http://www.sun.com/support/`
Training	`http://www.sun.com/training/`

Third-Party Web Sites

Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused by or in connection with the use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

The following specifications provide information relevant to the development and implementation of the Java Servlet API and standard servlet engines. Online versions of the following RFCs are at http://wwww.ietf.org/rfc/.

RFC 1630 Uniform Resource Identifiers (URI)

RFC 1738 Uniform Resource Locators (URL)

RFC 3986 Uniform Resource Identifiers (URI): Generic Syntax

RFC 1945 Hypertext Transfer Protocol (HTTP/1.0)

RFC 2045 MIME Part One: Format of Internet Message Bodies

RFC 2046 MIME Part Two: Media Types

RFC 2047 MIME Part Three: Message Header Extensions for non-ASCII text

RFC 2048 MIME Part Four: Registration Procedures

RFC 2049 MIME Part Five: Conformance Criteria and Examples

RFC 2109 HTTP State Management Mechanism

RFC 2145 Use and Interpretation of HTTP Version Numbers

RFC 2616 Hypertext Transfer Protocol (HTTP/1.1)

RFC 2617 HTTP Authentication: Basic and Digest Authentication

RFC 2818 HTTP Over TLS

The World Wide Web Consortium (http://www.w3.org/) is a definitive source of HTTP related information affecting this specification and its implementations.

The eXtensible Markup Language (XML) is used for the specification of the deployment descriptors described in Chapter 13 of this specification. More information about XML can be found at the following web sites:

http://java.sun.com/xml

http://www.xml.org/

Sun Welcomes Your Comments

Sun Microsystems is interested in improving its documentation and welcomes your comments and suggestions. You can submit your comments to jc-bandol-spec-feedback@sun.com.

Please include the title of your document with your feedback:

Java Servlet Specification, Java Card Platform, Version 3.0.1, Connected Edition.

^{1 (TableFootnote) The settings on your browser might differ from these settings.}