Kal Kal Thanks kal : findjar is awesome — Kavitha. KC -- yes. I find that I go to it about times a month because of some obscure missing class especially in legacy applications. Sign up or log in Sign up using Google.
Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back An detailed example is provided in Appendix A. Content handlers may be installed on the device either before they are needed or when they are needed. The content handler API can be used to trigger the installation process to install the content handlers on the device.
For at least one downloadable application packaging type supported by the device, the CHAPI implementation MUST provide and register a content handler to perform the installation. The appropriate installation process for the device MUST be used to attempt to install the content handler. The installation MUST include all of the required security and user prompts as specified in the appropriate profile and download specification.
If the installation process fails for any reason, including the user's decision to cancel the installation, then the Invocation will fail with the Invocation. The status response must be delivered to the invoking application, if required in the request.
Content handlers are applications and are subject to the same security, integrity, installation, upgrade, and other requirements as any other application in the applicable Java runtime environment. Authentication of applications and application classes MUST conform to the requirements of the applicable Java runtime environment. Each Java runtime environment has its own application packaging and runtime requirements. Each content handler application MUST conform to these requirements.
Each Java runtime specifies how applications are uniquely identified, for example, by a classname of the application class. Installation and removal of content handlers utilizes the normal mechanisms of the Java runtime environment.
During installation, any content handlers MUST be registered using the attributes defined in the application packaging. Typically, they will be present in an application descriptor or JAR manifest. When a content handler application is removed, all of the static and dynamic registrations of the content handler application MUST be released. A goal of the Content Handler API is to promote a smooth or seamless user experience between the invoking application and content handler.
Typically, if the invoking application has a user interface, one of its screens will be displayed to the user that is, it will be in the foreground. If a user action causes an Invocation then the next screen the user sees should be the content handler for that invocation. If a foreground content handler finishes with an invocation that requires a response to the calling application that had the foreground immediately before the content handler was invoked, and there are no other requests buffered or being processed from the same calling application, then the foreground is returned to the calling application.
If there is a conflict between foreground transitions and external events or explicit user actions, then the external events or user actions should take precedence. Static Registration of Content Handlers Content handler registration can, and generally should, be handled during the installation of the application. The following attributes can be included in the JAR manifest of the application. Each Java runtime environment may define their own application packaging extensions.
If the attributes are present, they MUST be used by the installation process to register the content handlers. If the application is being upgraded from a previous version then static registrations that are not replaced by new registrations are removed. Each content handler is uniquely identified by an ID. Each static content handler registration contains the following information. Multiple registrations can be provided in an application. The first missing entry terminates the list.
Any additional entries are ignored. The locale string should be properly formatted as defined in class ContentHandler. If the number of action names does not match the number of actions, then the installation MUST fail.
Action names may contain embedded whitespace. Leading and trailing whitespace is deleted from each action. The content handler ID is set during installation and returned from the method ContentHandler.
If not provided, a unique value MUST be provided by the implementation. The contents of the MIDlet descriptor file, when it is present, are made available via the javax. The developer is responsible for creating and distributing the components of the JAR file as appropriate for the target user, device, network, locale, and jurisdiction.
For example, for a particular locale, the resource files would be tailored to contain the strings and images needed for that locale. The JAR manifest defines attributes that are used by the application management software to identify and install the MIDlet suite and as defaults for attributes not found in the application descriptor.
The attributes are defined for use in both the manifest and the optional application descriptor. The predefined attributes listed below allow the application management software to identify, retrieve, install, and invoke the MIDlet. The version number of the MIDlet suite. Version numbers are formatted so they can be used by the application management software for install and upgrade uses, as well as communication with the user.
The first missing entry terminates the list. Any additional entries are ignored. Leading and trailing spaces in name, icon and class are ignored. The minimum number of bytes of persistent data required by the MIDlet. The device may provide additional storage according to its own policy. The default is zero. The J2ME profiles required, using the same format and value as the System property microedition.
The device must implement all of the profiles listed. If any of the profiles are not implemented the installation MUST fail. Zero or more permissions that are critical to the function of the MIDlet suite. Zero or more permissions that are non-critical to the function of the MIDlet suite. Register a MIDlet to handle inbound connections. Refer to javax. PushRegistry for details.
Refer to the OTA Specification for details. Version numbers have the format Major. Micro] X. X] , where the. Micro portion MAY be omitted. If the. Micro portion is not omitted, then it defaults to zero. In addition, each portion of the version number is allowed a maximum of two decimal digits i. For example, 1. For each portion of the version number, leading zeros are not significant. For example, 08 is equivalent to 8. Also, 1. However, 1. A missing MIDlet-Version tag is assumed to be 0.
The manifest provides information about the contents of the JAR file. An attribute MUST not appear more than once within the manifest. If an attribute is duplicated the effect is unspecified. For example, a manifest for a hypothetical suite of card games would look like the following example:.
All Java classes needed by the MIDlet are be placed in the JAR file using the standard structure, based on mapping the fully qualified class names to directory and file names. For example, a class com.
0コメント