Java Reference
In-Depth Information
of a DoJa application. It inherits its suffix ( .jam ) from the original Java
ME days when it was tied in with the Java Application Manager (JAM)
which evolved into the Application Management Service (AMS). The ADF
is completely standardized and integrated into the execution framework
and contains a large number of parameters most of which are optional.
These primarily address security issues and can be thought of as taking
the place of the API permissions in protection domains in MIDP.
DoJa is designed to be secure. If any of the parameters contain invalid
values, the default behavior of the launch sequence is to prevent the
application from running altogether. Most of these parameters can be left
at their default values, but there are a few core parameters worth outlining
here, as described in Table 7.3. For a comprehensive overview, consult
the DoJa Developers Guide. 7
The ADF provides a secure contract for DoJa applications. As can be
seen above, some of the more interesting things that can be done include
configuring an i-Appli to start periodically, in response to an incoming
SMS or when the device goes into stand-by mode. The ADF drives and
defines all of these behaviors in an easy-to-understand and consistent
Table 7.3 ADF Parameters
The URL for the application binary; communication by the
application is only possible to the host and port defined
in this field
JAR size in bytes, set during compilation
Size of the Scratchpad in bytes; the maximum value here
is device-dependent
Start-up parameters (i.e. command-line input)
Specifies if network communication is used; the only valid
value is http
Specifies if SMS is used; the value is either blank or the
string 'Yes'
If MSISDN is set here, application launch via SMS is
Used when applications need to be launched automati-
cally at regular intervals; the format is Ih where h is the
interval in hours.
Search WWH ::

Custom Search