Package javax.microedition.ipdr.configuration

This package contains the set of interfaces for defining the configuration.

See:
Description

Interface Summary

CollectorConfig	This interface provides the configuration of the collector.
CollectorPriorityConfig	This interface provides the configured priority of a collector.
ConnectionConfig	This interface provides the configuration of the Connection.
ExporterConfig	This interface provides the configuration of the exporter.
FieldConfig	This interface provides a configuration of a field in a template.
SessionConfig	This interface provides a configuration of a Session.
TemplateConfig	This interface provides a configuration of a Templat ETA defines that at least one implementation must be implemented by the ETA implementer.

Class Summary

ExporterConfigFactory

The ExporterConfigFactory is an ExporterConfig Factory This factory instantiates implementation of ExporterConfig that takes all its parameters from JAD/manifest

Exception Summary

ConfigException

Exception thrown whenever there is an error in the configuration data.

Package javax.microedition.ipdr.configuration Description

This package contains the set of interfaces for defining the configuration. The root of this set of interfaces is used by the implementation in order to set the proper configuration.

The main goal of the set of Java configuration interfaces is to enable the API implementation to be easily configured (in a standard way). In order to constitute a standard configuration methodology, the set of Java configuration interfaces MUST be supported by the implementation.

§ The main entry point for ETA (ExporterManager) gets the configuration interface, ExporterConfig, as input and uses it to configure itself.

Attributes in the Mobile Information Device Profile (MIDP) are considered to be the natural ways to expose configuration for Java ME applications (attributes can be specified in both the descriptor (JAD) and the manifest). For this reason, this JSR defines a set of attributes to be an alternative standard way to define the configuration for an ETA implementation. However, if the attributes mechanism is used for configuration (The ExporterConfig implementation take its attributes from Manifest/JAD file), they MUST be as presented in the table below.

Note: A configuration implementation might collect subset of the configuration from the Manifest/JAD (in this case it must stand the rules and the names that defined in this spec with regards to the Manifest/JAD attributes) and all others parameters might be collected from other locations (such as been written hard coded)

Where a default value is given, in some cases the default defined by JSR 190 specification and in other cases the default value is defined by the implementer. A mandatory parameter must always be part of the set of attributes (JAD file or manifest) and have a value (if it chosen to be taken from the Manifest/JAD file).