Abstract: A computer-implemented method and system useful in creating a device driver of a different architecture, based upon an existing driver of an original architecture. Information concerning an existing device driver is gathered. This information is stored for use by a transformation engine. The transformation engine maps information from the existing driver architecture to a new driver architecture. The transformation engine is used to obtain a description of the old driver in a format specific to the new driver architecture. A source code generation engine then converts the information obtained from the transformation engine into a new driver application layer. Given the base driver with the application layer already developed, a device provider or other driver creator can develop the device protocol layer for the driver.

Abstract: A collection of target Enterprise JavaBeans (EJBs) that are associated with the source EJB in a one-to-many association is obtained in response to traversing the one-to-many association of the source EJB. The collection of target EJBs is registered in a collection registry. The source EJB is passivated without passivating the collection of target EJBs, and the source EJB is later reactivated. The collection of target EJBs that are associated with the source EJB that is reactivated is fetched from the collection registry in response to traversing the one to many association of the source EJB that is reactivated. The one-to-many association between the source EJB and the collection of target EJBs may be managed by a link object that is generated by a link factory.

Abstract: A method and system for hibernating the state of executing applications on a removable module and resuming the applications at later time using the saved applications' state. After inserting the removable module into a computer system, the applications' state information stored on the removable module is loaded. The application state information may include an application identifier, a file identifier of a file being accessed by the application, and user preferences related to the application. One or more software applications are loaded from a nonvolatile storage device accessible by the computer system to a memory accessible by the computer system, and the loaded applications are executed. The state of each of the executed software applications is set based upon the corresponding application state information.