Abstract: A method and wireless mobile device runs different types of applications and groups a set of common application interfaces (APIs) that are associated with an application type to produce an application container (902). The wireless mobile device and method translates calls between at least one of the linked or grouped common APIs of the application container and a shared API that is shared for example among applications of different types (904). If desired the method and device also groups a set of common application interfaces associated with another application type to produce another application container. The applications of different types use APIs from the multiple application containers. In one embodiment, the translating of calls is accomplished by employing a class loading structure using, for example, a class loader that looks at certain path locations to obtain resources.

Abstract: A mobile device having a framework (901) comprising a logical device management tree (903), a device management engine (905), and a plurality of application specific logical device management sub-trees (907, 909) logically connected to the logical device management tree.

Abstract: A method and wireless mobile device runs different types of applications and groups a set of common application interfaces (APIs) that are associated with an application type to produce an application container (902). The wireless mobile device and method translates calls between at least one of the linked or grouped common APIs of the application container and a shared API that is shared for example among applications of different types (904). If desired the method and device also groups a set of common application interfaces associated with another application type to produce another application container. The applications of different types use APIs from the multiple application containers. In one embodiment, the translating of calls is accomplished by employing a class loading structure using, for example, a class loader that looks at certain path locations to obtain resources.

Abstract: A mobile device having a framework (901) comprising a logical device management tree (903), a device management engine (905), and a plurality of application specific logical device management sub-trees (907, 909) logically connected to the logical device management tree.

Abstract: A processor (304) of a wireless communication device (102, 216) scans (806) a patch for any difference commands indicating that data submitted in this command has been differenced by a file-level difference based on a file extension. Memory (306) contains data representing a device management tree (DMT). The processor (304) updates data of the device management tree to provide dynamic update of the DMT to facilitate software updates based on the patch.

Abstract: Methods and apparatus for providing customized security and logging protocols in a servlet environment are described. A servlet engine that includes a security module that assures that only those requests that are properly authenticated and authorized are serviced by a servlet. A logging module provides customized records of both security module and servlet transactions.

Abstract: Methods and computer systems for providing access to a protected resource are described. In an enterprise computer system, an authentication server provides a client requesting access to the protected resource a credential. In order to access the protected resource, the requesting client presents a protected resource access request in combination with the credential to a server coupled to the protected resource. The server, in turn, requests the authentication server to validate the credential. After the authentication server has validated the credential, the server grants the requesting client access to the protected resource.

Abstract: The Web Services Development Kit (WSDK) comprises a set of build-time tools and run-time components designed to support the development of web services and the interface to those services. WSDK provides a framework for the development of web services that isolates developers from the implementation details of the markup and transport layers, by separating the logical aspects of the service development from the physical aspects. A “call” generated by a client contains a batch of operations to be executed in the context of a single request/reply message exchange. A markup library translates logical structure to a specific markup language. Additional markup languages are supported by adding additional modules to the markup library.