International Business Machines Corporation

Other

Kevin Joe Williams

Timo J Salo

Lawrence Scott Rich

Timothy Marc Francis

Yang Lei

Arthur Thomas Jolin

Brent Hames Daniel

Systems and methods for managing energy within an inhabitable environment are provided. An energy storage system includes storing and managing energy. The storage of energy may be based on user preferences. The management of energy includes directing energy within the inhabitable environment according to user preferences and mapping data. Mapping data includes matching an electrical outlet to a location and/or device within the inhabitable environment. Instructions are provided by the computing device to the electrical components based on the mapping to control the electrical components and electrical devices.

Distributed energy source system

A many-to-many relationship management system. In an object persistence management system, a many-to-many relationship manager can include one or more related objects; a junction table storing relationships between the related objects; and, one or more corresponding links. Each link can correspond to one of the objects. Furthermore, each link can persist state information for the corresponding object in an associated object table. Finally, each link can manage the junction table responsive to changing relationships with others of the related objects. Importantly, as the present invention distributes the management of the junction table, a counter-operation management protocol can be provided which can resolve conflicts which arise in the management of the junction table in response to changing relationships among their associated objects.

Decentralized many-to-many relationship management in an object persistence management system

Methods, apparatus and computer instructions for a container managed persistent support architecture that meets the Enterprise Java Bean (EJB) Specification are disclosed. The support architecture provides application programmers a model for balancing generated components with runtime code to better optimize flexibility and efficiency of applications. Six generated components: concrete bean, bean adaptor binding, injector, extractor, data cache entry and function set, are used in combination with runtime code to perform typical operations of CMP entity beans.

Method and apparatus for a container managed persistent entity bean support architecture

The present invention provides methods, apparatus and computer instructions for a container managed persistent support architecture that meets the Enterprise Java Bean (EJB) Specification. The support architecture provides application programmers a model for balancing generated components with runtime code to better optimize flexibility and efficiency of applications. Six generated components: concrete bean, bean adaptor binding, injector, extractor, data cache entry and function set, are used in combination with runtime code to perform typical operations of CMP entity beans.

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.

Methods, systems and computer program products for maintaining association integrity of enterprise JavaBeans (EJB) during EJB passivation and reactivation

The present invention comprises a Dynamic Query Interface (DQI). The DQI provides an apparatus and method for dynamically discovering the shape of data returned by a DBMS in response to a query statement. The DQI comprises a Query Schema, a Select Macro, and a Macro Expansion Module (MEM). Unlike conventional query statements, a Select Macro only requires a select-clause. The MEM builds a conventional query statement from a Select Macro using information contained in the Query Schema. The Macro Token expansion approach implemented in the MEM obviates the need for full language parsing and is thus much more suited to runtime execution than prior art solutions. Furthermore, because the MEM examines a Select Macro at runtime, the MEM has the added advantage over prior art solutions of being able to discover dynamically the shape of the requested data at runtime.

Macro-based dynamic discovery of data shape

A technique for managing life cycles of objects which are created by mapping layer software in response to retrieving data from a relational database. Object-level cursors are defined, where an object cursor is mapped to a database cursor for a particular cursored query. When the application traverses from one root object to another, the object-level cursor is advanced and memory used to store the objects corresponding to the previous subset of cursored rows is released, freeing memory space for a next set of objects corresponding to a next subset of cursored rows. The database cursor is also advanced to align with a row corresponding to the current root object to be processed by the application. Using this technique, result sets may be arbitrarily large without impacting system performance or efficiency.

Managing object life cycles using object-level cursor

Systems, methods and computer program products automatically order database transaction by an object-oriented transaction system. The objects in the completed transaction are clustered into groups of objects to be inserted into the relational database, objects to be deleted from the relational database and objects to be updated in the relational database. The objects to be inserted into the relational database are ordered according to an insert precedence of the objects into the relational database to thereby define an insert order. The objects to be deleted from the relational database are ordered according to a delete precedence of the objects from the relational database are ordered according to a delete precedence of the objects from the relational database to thereby define a delete order. The objects to be inserted into the relational database are inserted into the relational database in the insert order. Then, the objects to be updated in the relational database are updated in an arbitrary order. Finally, the objects to be deleted from the relational database are deleted from the relational database in the delete order.

SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCTS FOR ORDERING OBJECTS CORRESPONDING TO DATABASE OPERATIONS THAT ARE PERFORMED ON A RELATIONAL DATABASE UPON COMPLETION OF A TRANSACTION BY AN OBJECT-ORIENTED TRANSACTION SYSTEM

Growing community of inventors

Colorado Springs, CO, United States of America

Kevin Joe Williams