Sun Java Solaris Communities My SDN Account

Article

Java Card Platform, v3.0, Connected Edition : XML Schemas for Java Card Deployment Descriptors

 
This Version: April 13, 2010  

Latest Version: http://java.sun.com/xml/ns/javacard/

Contents
 
 
1. Introduction
2. Using Java Card Technology Schemas
3. Java Card 3 Technology Schema Resources
 
1. Introduction

This document lists the document formats that are used by the Java Card Platform, Connected Edition, Version 3.0.2, deployment descriptors described by Java Card 3.0.1 specifications. Each descriptor within the specification requires its deployment descriptor be validated with respect to an XML schema that is listed by this document.

This document describes how to use the Java Card technology schemas that are described as a set of modules and provides a list of XML schemas for each deployment descriptor.

2. Using Java Card Technology Schemas

All Java Card technology deployment descriptor schemas share the namespace, http://java.sun.com/xml/ns/javacard/ except for the Java Card Web Application Deployment Descriptor Schema, which uses the Java Platform, Enterprise Edition (formerly J2EE) namespace, http://java.sun.com/xml/ns/j2ee/ and is a subset of the J2EE Servlet Deployment Descriptor Schema.

Each schema document contains a version attribute that contains the version of the specification. For example, the XML schema document for the Java Card Applet Application Deployment Descriptor and the Java Card Platform-specific Application Descriptor contain the version attribute value "3.0", pertaining to the specific version of the Java Card specifications as well as the schema document itself. The Java Card Web Application Deployment Descriptor Schema contains the version attribute value "2.4" to indicate that it is a subset of the J2EE Servlet Deployment Descriptor Schema, version 2.4.

Each Java Card technology XML schema document's file name contains the specific version of the related specification. This is introduced for convenience to locate specific versions of the schema documents. The version attribute in the schema instance provides sufficient information for deployment descriptor processors to validate the Java Card Applet Application Deployment Descriptor instance and the Java Card Platform-specific Application Descriptor instance in the http://java.sun.com/xml/ns/javacard/ namespace. However, to validate against the Java Card 3 Platform, subset of the J2EE Servlet Deployment Descriptor Schema, the schema location (http://java.sun.com/xml/ns/javacard/) and file name (jcweb-app_3_0.xsd) must be specified.

A specific version of the Java Card specifications contains a set of deployment descriptor schemas that constitute the Java Card technology schema. The common definitions are contained in the j2ee_<version>.xsd and xml.xsd documents that may be included by several Java Card technology deployment descriptor schemas.

3. Java Card 3 Technology Schema Resources

This table contains the XML schema components for Java Card 3 technology.

Date Published
File Name
Description
Status
Dec. 21, 2009
Java Card Web Application Deployment Descriptor Schema
Final Release
Mar. 26, 2008
Java Card Applet Application Deployment Descriptor Schema
Final Release
Mar. 26, 2008
Java Card Platform-specific Application Descriptor Schema
Final Release
Nov. 24, 2003
Java EE v1.4 definitions file that contains common schema components
Final Release
The Java EE schemas use some common definitions provided and published by W3C
 

Oracle is reviewing the Sun product roadmap and will provide guidance to customers in accordance with Oracle's standard product communication policies. Any resulting features and timing of release of such features as determined by Oracle's review of roadmaps, are at the sole discretion of Oracle. All product roadmap information, whether communicated by Sun Microsystems or by Oracle, does not represent a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. It is intended for information purposes only, and may not be incorporated into any contract.