Abstract: A system and method for providing composite applications for software-based systems that uses a built-in application model having at least one general purpose object type, and providing dynamic late-binding of object implementations through an object typing system decoupled from pre-run time program code, using persistently stored objects. The application model may require that program objects in a conformant application be instances of a predefined active object type, or optionally instances of a predefined reactive object type. The application model enables integration of applications into composite applications, and further integration of composite applications into subsequently defined systems. The run-time object typing system for persistently stored objects is independent of the class typing system that is defined at compile-time or link-time, and enables convenient and practical modifications during development, deployment and maintenance of composite applications.

Abstract: A system and method for binding software objects to the program code that implements them in accordance with run-time object typing that is independent of the program code typing system. Persistently-stored, run-time object instances (“persistent objects”) are maintained by a software-based system across transactions, user sessions, and application executions, and are identified by unique, typed names. Dynamic binding is provided through software constructs that are associated with corresponding persistent objects, and referred to as “Associators”. Associators provide links between object types and the program code that implements them.

Abstract: A user-driven, service-oriented application model, in which conformant applications implement and process instances of two program object types. Components in conformant applications consist of objects having built-in behaviors that are common across different applications. Each application object is either an instance of a predefined active object type, or an instance of a predefined reactive object type. Active objects are associated with individual users of their application, are allowed to activate services, and encapsulate all their inputs and outputs within a bounded space. Reactive objects are instantiated or processed by services, and, in one embodiment, each one is owned by an individual active object at any given point in time. During operation of the disclosed system, services activated by active objects route reactive objects to active objects. An active object assumes ownership of a received reactive object upon receipt.

Abstract: The present invention relates to an improved process for producing lead oxide in a pure state from a spent paste resulting from exhausted acid batteries. The spent paste is first calcined and desulfurized, then leached by a concentrated solution comprising an alkali hydroxide at a temperature above 100.degree. C. The separated solution is contacted with a ketone resulting in a suspension from which the .alpha.-lead oxide constituent is recovered. The solutions of alkali and ketone are recycled in the process. The preferred alkali constituents are selected from sodium hydroxide or potassium hydroxide, preferably containing also a small amount of sulfate of the respective alkali metal of the hydroxide used.

Abstract: A process for the recovery of lead from spent battery paste and lead containing materials. The process includes the steps of calcination of a spent paste treated with an alkali carbonate or hydroxide or any mixture thereof, and elemental sulphur at a temperature of up to 600.degree. C., followed by washing with water. The calcined and washed paste is dissolved in an alkali molten electrolyte, and lead is electrowinned from the alkali molten electrolyte. The spent electrolyte is reused in the process.

Abstract: The present invention relates to a process for the recovery of metallic lead from exhausted lead-acid batteries. According to the invention, the metallic scrap obtained thereof is treated by a smelting operation which is carried out under a layer of a molten flux. The flux comprises alkali hydroxide and optionally also carbonate(s) and sulfate(s) of said alkali. The temperature which is maintained during the smelting is between 350.degree. C. to 600.degree. C. and most preferably in the range of between 450.degree. C. to 550.degree. C. The preferred weight ratio between the metallic scrap and the flux is between 15 to 45. Generally, the alkali flux is selected from sodium hydroxide and potassium hydroxide and mixtures thereof. The process is characterized by a very extent of lead recovery compared with the known processes and absence of exhausted gases.