US6085198A - Integrated three-tier application framework with automated class and table generation - Google Patents
Integrated three-tier application framework with automated class and table generation Download PDFInfo
- Publication number
- US6085198A US6085198A US09/092,610 US9261098A US6085198A US 6085198 A US6085198 A US 6085198A US 9261098 A US9261098 A US 9261098A US 6085198 A US6085198 A US 6085198A
- Authority
- US
- United States
- Prior art keywords
- data
- class
- tier
- client
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/31—Programming languages or programming paradigms
- G06F8/315—Object-oriented languages
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/211—Schema design and management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/289—Object oriented databases
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99942—Manipulating data structure, e.g. compression, compaction, compilation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99951—File or database maintenance
- Y10S707/99952—Coherency, e.g. same view to multiple users
- Y10S707/99953—Recoverability
Definitions
- This invention relates to the field of computer software, and, more specifically, to multi-tier software applications.
- an application architecture that is becoming more widely used, particularly in the Internet environment, is the three-tier application architecture, or three-tier architecture.
- a client communicates requests to a server for data, software and services, for example, and the server responds to the requests which may entail communication with a database management system for the storage and retrieval of persistent data.
- the three tier architecture includes a database tier that includes a database server, an application tier that includes an application server and application logic (i.e., software application programs, functions, etc.), and a client tier.
- the application server responds to application requests (e.g., a request for a software applet, etc.) received from the client.
- the application server forwards data requests to the database server.
- An enterprise's application e.g., a scheduling, accounting or personnel application
- FIG. 2 provides an overview of a three-tier architecture.
- Client tier 202 typically consists of a computer system that provides a graphic user interface (GUI) generated by a client 206, such as a browser or other user interface application.
- GUI graphic user interface
- Client 206 generates a display from, for example, a specification of GUI elements (e.g., a file containing input, form, and text elements defined using the Hypertext Markup Language (HTML)) and/or from an applet (i.e., a program such as a program written using the JavaTM programming language that runs when it is loaded by the browser).
- GUI graphic user interface
- HTML Hypertext Markup Language
- Database tier 218 contains the data that is accessed by the application logic in application tier 216.
- Database server 212 manages the data, its structure and the operations that can be performed on the data and/or its structure.
- Application server 210 can include applications such as a corporation's scheduling, accounting, personnel and payroll applications, for example.
- Application server 210 manages requests for the applications that are stored therein.
- Application server 210 can also manage the storage and dissemination of production versions of enterprise application logic (i.e., the versions that are currently being used by the corporate users).
- Database server 212 manages the database(s) that manage data for applications. Database server 212 responds to requests to access the scheduling, accounting, personnel and payroll applications' data, for example.
- Connection 204 is used to transmit enterprise data between client tier 202 and application tier 216, and may also be used to transfer the enterprise application logic to client tier 202.
- the client tier can communicate with the application tier via, for example, a Remote Method Invocator (RMI) application programming interface (API) available from Sun MicrosystemsTM.
- RMI Remote Method Invocator
- API application programming interface
- the RMI API provides the ability to invoke methods, or software modules, that reside on another computer system. Parameters are packaged and unpackaged for transmittal to and from the client tier.
- Connection 214 between application server 210 and database server 212 represents the transmission of requests for data and the responses to such requests from applications that reside in application server 210.
- Elements of the client tier, application tier and database tier may execute within a single computer. However, in a typical system, elements of the client tier, application tier and database tier may execute within separate computers interconnected over a network such as a LAN (local area network) or WAN (wide area network).
- a network such as a LAN (local area network) or WAN (wide area network).
- Schema information in the form of metadata structures is used to generate data classes for the client tier and the application tier.
- Corresponding client tier and application tier data classes implement a common interface that supports generalized access by other system components.
- factory classes are automatically generated for the client tier and application tier which permit instantiation of the generated data classes.
- database configuration is automated by the generation of database table creation commands from the schema information.
- a framework of management components are provided for both the client and application tiers to handle inter-tier communication, transparent caching of data objects in a public store, handling of changes to data via change objects, handling of updates in response to data changes, and resolution of query objects into database queries.
- Common methods are generated within each data class which recognize the use of a public store and the application of a change object scheme. Further, methods and attributes are inherited from framework superclasses that confer the concept of identity on a data class, as well as the ability to discover the attributes of the data class.
- FIG. 1 is a block diagram of one embodiment of a computer system capable of providing a suitable execution environment for an embodiment of the invention.
- FIG. 2 is a general block diagram of a three-tier system.
- FIG. 3 is a block diagram of a three-tier application framework in accordance with an embodiment of the invention.
- FIG. 4 is a flow diagram of a process for generating classes and database tables in accordance with an embodiment of the invention.
- FIGS. 5A and 5B are block diagrams illustrating metadata structures in accordance with an embodiment of the invention.
- FIG. 6A is a flow diagram of a process for generating data classes from schema metadata in accordance with an embodiment of the invention.
- FIG. 6B is a flow diagram of a process for generating a class definition from a MetaClass instance in accordance with an embodiment of the invention.
- FIG. 7A is a flow diagram of a process for generating database "create table” commands from schema metadata in accordance with an embodiment of the invention.
- FIG. 7B is a flow diagram of a process for generating an attribute database declaration from schema metadata in accordance with an embodiment of the invention.
- FIG. 8 is a block diagram illustrating the use of data objects, change objects and query objects, in accordance with one embodiment of the invention.
- FIG. 9 is a block diagram of design time and run time environments in accordance with an embodiment of the invention.
- the invention is an integrated three-tier application framework with automated class and database table generation.
- numerous specific details are set forth to provide a more thorough description of embodiments of the invention. It will be apparent, however, to one skilled in the art, that the invention may be practiced without these specific details. In other instances, well known features have not been described in detail so as not to obscure the invention.
- An embodiment of the invention comprises a three-tier application framework having system management components that handle the representation of data in the form of data objects on the client tier and server tier.
- the data objects implement a common interface whether the data objects are resident on the client tier or the application tier.
- Application-specific logic on the client tier and application tier may access the data objects in the same manner, with storage and retrieval of persistent information in the database occurring transparently to the application specific logic.
- An object cache is provided on the client tier and the application tier to return pointers to data objects in response to object IDs.
- Application queries are performed via query objects.
- a query object is resolved against the object cache if the query object contains only object IDs. Otherwise, the query object is converted into a database query.
- the results of a database query are packaged into one or more data objects and returned.
- Changes to data are handled via change objects that encapsulate the changes being made.
- Change objects are produced automatically by data objects, and propagated transparently from the originating tier to the database tier in a transaction-based scheme by change management components in the client and application tiers. As the change objects propagate through the client and application tiers, the change objects may be applied to the corresponding data objects in the object caches. Updates of changes made are propagated to interested components via update management components on the client and application tiers. Change objects and query objects are transmitted between the client and application tiers by communication management components using serialization and reflection techniques.
- a code generator converts the schema information into metadata structures and generates data class definitions for the client tier and application tier that can interface with the framework management components. Class factories are also generated that provide factory methods for creating new instances of the data classes.
- the schema information in the metadata structures is used by the code generator to generate a schema class that can configure the database, at runtime, by generating "create table" commands to support the persistent attributes of the data classes.
- An embodiment of the invention can be implemented as computer software in the form of computer readable code executed on a general purpose computer such as computer 100 illustrated in FIG. 1, or in the form of bytecode class files executable within a Java runtime environment running on such a computer.
- a keyboard 110 and mouse 111 are coupled to a bi-directional system bus 118. The keyboard and mouse are for introducing user input to the computer system and communicating that user input to processor 113. Other suitable input devices may be used in addition to, or in place of, the mouse 111 and keyboard 110.
- I/O (input/output) unit 119 coupled to bidirectional system bus 118 represents such I/O elements as a printer, A/V (audio/video) I/O, etc.
- Computer 100 includes a video memory 114, main memory 115 and mass storage 112, all coupled to bidirectional system bus 118 along with keyboard 110, mouse 111 and processor 113.
- the mass storage 112 may include both fixed and removable media, such as magnetic, optical or magnetic optical storage systems or any other available mass storage technology.
- Bus 118 may contain, for example, thirty-two address lines for addressing video memory 114 or main memory 115.
- the system bus 118 also includes, for example, a 32-bit data bus for transferring data between and among the components, such as processor 113, main memory 115, video memory 114 and mass storage 112. Alternatively, multiplex data/address lines may be used instead of separate data and address lines.
- the processor 113 is a microprocessor manufactured by Motorola, such as the 680X0 processor or a microprocessor manufactured by Intel, such as the 80X86, or Pentium processor, or a SPARCTM microprocessor from Sun Microsystems, Inc.
- Main memory 115 is comprised of dynamic random access memory (DRAM).
- Video memory 114 is a dual-ported video random access memory. One port of the video memory 114 is coupled to video amplifier 116.
- the video amplifier 116 is used to drive the cathode ray tube (CRT) raster monitor 117.
- Video amplifier 116 is well known in the art and may be implemented by any suitable apparatus. This circuitry converts pixel data stored in video memory 114 to a raster signal suitable for use by monitor 117.
- Monitor 117 is a type of monitor suitable for displaying graphic images.
- Computer 100 may also include a communication interface 120 coupled to bus 118.
- Communication interface 120 provides a two-way data communication coupling via a network link 121 to a local network 122.
- ISDN integrated services digital network
- communication interface 120 provides a data communication connection to the corresponding type of telephone line, which comprises part of network link 121.
- LAN local area network
- communication interface 120 provides a data communication connection via network link 121 to a compatible LAN.
- Wireless links are also possible.
- communication interface 120 sends and receives electrical, electromagnetic or optical signals which carry digital data streams representing various types of information.
- Network link 121 typically provides data communication through one or more networks to other data devices.
- network link 121 may provide a connection through local network 122 to local server computer 123 or to data equipment operated by an Internet Service Provider (ISP) 124.
- ISP 124 in turn provides data communication services through the world wide packet data communication network now commonly referred to as the "Internet" 125.
- Internet 125 uses electrical, electromagnetic or optical signals which carry digital data streams.
- the signals through the various networks and the signals on network link 121 and through communication interface 120, which carry the digital data to and from computer 100, are exemplary forms of carrier waves transporting the information.
- Computer 100 can send messages and receive data, including program code, through the network(s), network link 121, and communication interface 120.
- remote server computer 126 might transmit a requested code for an application program through Internet 125, ISP 124, local network 122 and communication interface 120.
- one such downloaded application is the apparatus for the integrated three-tier application framework described herein.
- the received code may be executed by processor 113 as it is received, and/or stored in mass storage 112, or other non-volatile storage for later execution. In this manner, computer 100 may obtain application code in the form of a carrier wave.
- Application code may be embodied in any form of computer program product.
- a computer program product comprises a medium configured to store or transport computer readable code, or in which computer readable code may be embedded.
- Some examples of computer program products are CD-ROM disks, ROM cards, floppy disks, magnetic tapes, computer hard drives, servers on a network, and carrier waves.
- An embodiment of the invention includes software apparatus comprising a collection of components configured to support an integrated three-tier architecture.
- the components may be implemented as one or more instances of object classes in accordance with known object-oriented programming practices, or the components may be implemented under one or more component model definitions.
- component model definitions are currently available, such as COM, CORBA, and the Java component scheme referred to as JavaBeansTM.
- Each component model provides for encapsulation of related functions and data structures into individual components, similar to what occurs under a standard object-oriented programming (OOP) approach.
- OOP object-oriented programming
- the particular mechanisms by which the components are managed and interact are defined according to the respective component model.
- Bridges e.g., ActiveX
- Interaction is typically performed through a set of methods implemented by the component. These sets of methods are referred to as "interfaces" in some component models.
- the public methods by which OOP object classes interact are often presented in the form of application programming interface (API) definitions.
- API application programming interface
- Object-oriented programming is a method of creating computer programs by combining certain fundamental building blocks, and creating relationships among and between the building blocks.
- the building blocks in object-oriented programming systems are called "objects.”
- An object is a programming unit that groups together a data structure (one or more instance variables) and the operations (methods) that can use or affect that data.
- an object consists of data and one or more operations or procedures that can be performed on that data.
- the joining of data and operations into a unitary building block is called "encapsulation.”
- An object can be instructed to perform one of its methods when it receives a "message."
- a message is a command or instruction sent to the object to execute a certain method.
- a message consists of a method selection (e.g., method name) and a plurality of arguments.
- a message tells the receiving object what operations to perform.
- object-oriented programming is the way in which methods are invoked. When a message is sent to an object, it is not necessary for the message to instruct the object how to perform a certain method. It is only necessary to request that the object execute the method. This greatly simplifies program development.
- Object-oriented programming languages are predominantly based on a "class” scheme.
- the class-based object-oriented programming scheme is generally described in Lieberman, "Using Prototypical Objects to Implement Shared Behavior in Object-Oriented Systems," OOPSLA 86 Proceedings, September 1986, pp. 214-223.
- a class defines a type of object that typically includes both variables and methods for the class.
- An object class is used to create a particular instance of an object.
- An instance of an object class includes the variables and methods defined for the class. Multiple instances of the same class can be created from an object class. Each instance that is created from the object class is said to be of the same type or class.
- an employee object class can include "name” and "salary” instance variables and a "set -- salary” method. Instances of the employee object class can be created, or instantiated for each employee in an organization. Each object instance is said to be of type “employee.” Each employee object instance includes "name” and “salary” instance variables and the "set -- salary” method. The values associated with the "name” and “salary” variables in each employee object instance contain the name and salary of an employee in the organization. A message can be sent to an employee's employee object instance to invoke the "set -- salary” method to modify the employee's salary (i.e., the value associated with the "salary" variable in the employee's employee object).
- a hierarchy of classes can be defined such that an object class definition has one or more subclasses.
- a subclass inherits its parent's (and grandparent's etc.) definition.
- the parent class is also referred to as a "superclass.”
- Each subclass in the hierarchy may add to or modify the behavior specified by its parent class.
- Some object-oriented programming languages support multiple inheritance where a subclass may inherit a class definition from more than one parent class.
- Other programming languages, such as the Java programming language support only single inheritance, where a subclass is limited to inheriting the class definition of only one parent class.
- the Java programming language also provides a mechanism known as an "interface" which comprises a set of constant and abstract method declarations.
- An object class can implement the abstract methods defined in an interface.
- An object is a generic term that is used in the object-oriented programming environment to refer to a module that contains related code and variables.
- a software application can be written using an object-oriented programming language whereby the program's functionality is implemented using objects.
- the encapsulation provided by objects in an object-oriented programming environment may be extended to the notion of components under a component model definition.
- Java programming language is an object-oriented programming language with each program comprising one or more object classes.
- Java classes are compiled into machine independent bytecode class files.
- Each class contains code and data in a platform-independent format called the class file format.
- the computer system acting as the execution vehicle supports the Java runtime environment.
- the runtime environment contains a program called a virtual machine, which is responsible for executing the code in Java classes.
- Applications may be designed as standalone Java applications, or as Java "applets" which are identified by an applet tag in an HTML document, and loaded by a browser application.
- the class files associated with an application or applet may be stored on the local computing system, or on a server accessible over a network. Each class is loaded into the Java runtime environment, as needed, by the "class loader.”
- Java classes are loaded on demand from the network (stored on a server), or from a local file system, when first referenced during an application or applet's execution.
- the runtime environment locates and loads each class file, parses the class file format, allocates memory for the class's various components, and links the class with other already loaded classes. This process makes the code in the class readily executable by the virtual machine.
- Java classes may also be incorporated into Java components referred to as "JavaBeans".
- JavaBeans are designed in accordance with the JavaBean API Specification to allow for component-based application building.
- Bridges e.g., ActiveX bridges
- JavaBeans may be used with JavaBeans to allow JavaBeans to be used in other component model environments, such as OLE/COM and CORBA.
- JavaBean framework supports for features such as “introspection,” “customization,” “events,” “properties” and “persistence” is provided within the JavaBean framework to facilitate application building and component use.
- Introspection permits builder tools to analyze how a particular bean works.
- Customization permits an application builder to customize the appearance and behavior of a bean.
- Events provide a simple communication metaphor that can be used to connect a bean with other application components or beans.
- “Properties” are used for bean customization and programmatic use.
- Persistence allows for a bean to have its customized state saved and reloaded later.
- Embodiments of the software apparatus may be implemented using standard OOP object classes or using components under a known component model definition.
- references to components may refer to one or more instances of OOP object classes, or one or more components under a known component model.
- FIG. 3 is a block diagram of an implementation of a three-tier application framework in accordance with an embodiment of the invention.
- the three-tier application framework comprises one or more clients, such as clients 300A and 300B, in the client tier, application server 307 in the application tier and database server 311 in the database tier.
- clients 300A and 300B are coupled to application server 307 to exchange method calls and data.
- application server 307 is coupled to database server 311 to exchange database calls and data. It is also possible in some embodiments for additional servers to be coupled to application server 307 for the exchange of enterprise data.
- Application server 307 maintains a set of objects containing data for the clients it serves. Clients 300A and 300B each maintain a subset of objects containing data for their respective user needs.
- Application server 307 is responsible for transforming data from the format of database server 311 into the form of data objects, and, similarly, from the form of data objects into the format of database server 311. Additionally, queries are transformed from a general query object format into the particular query format expected by database server 311, such as SQL.
- Clients 300A and 300B comprise client-side application logic and graphic user interface (GUI) component 301A, client-side change management component 302A, client-side object cache component 303A, client-side update management component 304A, client-side communication management component 305A and client-side query management component 312A.
- Application server 307 comprises server-side communication management component 305B, server-side application logic 301B, server-side change management component 302B, server-side object cache component 303B, server-side update management component 304B, server-side query management component 312B, data store component 308 and database connectivity component 309 (e.g., a Java data base connectivity or JDBCTM component).
- GUI graphic user interface
- Client-side application logic and GUI component 301A provides the software mechanism by which the user is able to view the data and other output associated with a particular application, to generate input in the form of additions, deletions and modifications of data, and to otherwise exert control over the data and format of what is displayed.
- Client-side application logic and GUI component 301A interfaces with client-side change management component 302A, client-side object cache component 303A, client-side update management component 304A and client-side query management component 312A.
- Client-side change management component 302A provides the software mechanism by which changes to data are handled within the respective client. This entails determining which objects within the client are affected by a change and carrying out the change on those objects. Also, the change is propagated to the application server for handling. In one embodiment, changes are abstracted into change objects.
- the change object for example, may contain the state of a given data object before a change is applied, as well as the state of the given data object after the change is applied. Custom change objects for specific data classes may be subclassed from general framework change object superclasses.
- Client-side communication management component 305A is used to transmit a change object to application server 307, or to receive a change object from application server 307.
- Client-side object cache component 303A maintains a set of objects for the respective client, as well as a hash table of the unique ID of each object thus maintained and an associated pointer to that object.
- client-side object cache component 303A is first queried to determine whether the data object containing the desired data is already resident at the client. If the data object is resident, as indicated by the presence of its object ID in the hash table, client-side object cache component 303A returns to the requesting logic a pointer to the data object. If the object is not resident at the client, client-side cache component 303A sends a request for the given object to application server 307.
- a pointer to the object is returned to the requesting application logic, and the object is registered in the hash table for future requests.
- client-side cache component 303A may perform what is referred to as "pruning the cache.” This means that certain data objects are removed from client-side cache component 303A by removing their entries in the hash table. Data objects whose entries have been removed from the hash table may then be garbage collected by the system.
- Reference counting may be used to determine which objects are currently in demand, or more advanced interest registries may be used for such a purpose.
- a reference count value associated with a given cache object is incremented whenever another referencing object obtains a reference to the cache object.
- the reference count value is decremented whenever a referencing object indicates the reference to the cache object is no longer needed. When the reference count is at zero, no other objects maintain a reference to the cache object, and it may be safely removed from the object cache and garbage collected.
- interest objects may be used to indicate that one or more objects are "interested” in actions involving a particular data object in the cache (i.e., a cache object). These interest objects can thus be used to determine which cache objects are subject to registered interest and which are not. Those cache objects for which no interest objects are registered may be safely removed from the object cache.
- Client-side query management component 312A provides a mechanism for formulating application queries, and, either resolving those queries against client-side object cache 303A, or forwarding those queries to application server 307 for handling.
- Object requests or queries from application logic are typically encapsulated within one or more query objects. If a query object contains only object IDs, the query object may be resolved against the object cache. If a query object contains query information other than object IDs, the query object is transmitted to application server 307 to be resolved into an appropriate database query for the database server. Responses to the database query are encapsulated into one or more data objects and returned to the requester.
- the hash tables of the respective object cache components are updated to include the new data objects.
- Custom query objects with application specific semantics may be subclassed from general framework query object superclasses. Further, query object subclasses may extend interest-based object superclasses that implement active updating through registration of interest objects that identify the query requester with the data objects resulting from the query.
- Client-side update management 304A provides the software mechanism by which updates are applied to data objects and other associated objects within the respective client.
- client-side update management component 304A implements an active updating scheme. This means that not only is a data object affected by changes in the form of an addition, deletion or modification of associated data, those objects in client-side application logic and GUI component 301A that are dependent on the associated data are also updated. This is opposed to a passive update scheme wherein objects in client-side application logic and GUI component 301A would not be aware of changes to data until and unless a further reference is made to the respective data object, at which time the data object would determine whether an update is necessary.
- One method for implementing the active updating scheme is to apply interest objects as discussed briefly above.
- Query objects result in the registration of an interest object for the requester. Any changes to data objects passed as a result of the query will be propagated to the interested component indicated in the registered interest object. Further description of the interest scheme is provided in copending U.S. patent application Ser. No. 09/092,356, entitled “Method and Apparatus of Performing Active Update Notification,” filed on Jun. 5, 1998, assigned to the same assignee, and incorporated herein by reference.
- Client-side communication management component 305A provides the software mechanism by which objects and method calls are transmitted between the client (300A or 300B) and application server 307.
- objects that may be transmitted between the client and application tiers are configured with metadata describing the elements of the object, such as the attribute names and types, methods, etc.
- Objects configured with metadata can be serialized, that is, broken down into a set of data bytes containing the metadata descriptions and object state which may later be reconstituted (i.e., "deserialized") by the same or a different application to generate a copy of the original object.
- Serialization provides a useful mechanism for object persistence and transmission.
- a serialized object may be stored in memory for any length of time and regenerated with the same state the object had at the time it was serialized.
- object transmission a serialized object may be transmitted between remote clients and servers as data streams or packets in accordance with known communication protocols, such as the protocol implemented by the Remote Method Invocator (RMI) API.
- RMI Remote Method Invocator
- serialized objects may be written to a shared portion of memory by one application and read out of the shared memory by another application.
- Client-side and server-side communication management components 305A and 305B implement methods to perform serialization and deserialization functions.
- Data transport such as the transmission and reception of serialized objects, may be implemented using any known communication protocol as described above.
- Server-side communication management component 305B performs the same general functions for application server 307 as its counterpart component 305A does for client 300A or 300B, such as serialization, deserialization, and data transport.
- Method calls and objects received by the server-side communication management component from client-side communication management component 305A are directed to server-side components 301B, 302B, 303B, 304B and 312B as specified by the call either explicitly or implicitly.
- Method calls or objects destined for the client tier are directed to the client-side communication management component 305A of the specified client, 300A or 300B.
- Server-side application logic 301B provides any application-specific functions for application server 307, such as data analysis and processing algorithms, etc. Further, automated data functions, such as time-based operations, and multi-client oriented operations may be implemented by server-side application logic 301B. These functions may also include the implementation of a permissions model for determining access permissions and change permissions for different clients or users.
- the division of application-specific functionality between client-side application logic and GUI component 301A and server-side application logic 301B may be determined by the relative efficiency of shared functions on a server versus local functions on a client. Also, the use of a thin client or thick client topology may determine how functions are divided between clients 300A and 300B and application server 307.
- Server-side change management component 302B provides for the application of changes, for example, in the form of change objects, to data objects in application server 307.
- Change objects may be received from either of clients 300A or 300B (or from other servers).
- the changes embedded within change objects are used by datastore management component 308 to send appropriate calls to database server 311 to manipulate the persistent data stored therein.
- a call may be made to one or more permissions objects in the application logic component 301B, to determine whether the encapsulated change is allowed. The change may then be undone at the client if the change is not permissible, or the change may be carried out on the application server and propagated to the database if the change is permissible.
- changes are handled within a transactional scheme.
- Change objects allow several benefits in a transactional scheme. For example, change objects may be stored on a stack after the associated changes have been performed. The stack of change objects may then be used to perform transaction rollbacks, that is, the change objects may be used to "undo" or reverse the changes previously performed. "Redo" functions are also easily implemented.
- change objects may be collected on a client while the client is offline from an application server. When the client is once again connected to the application server, the change objects may be applied to the application server.
- Server-side object cache component 303B is similar to the client-side object cache component 303A.
- the request is resolved against the cache, if possible, by specifying the object ID in the hash table. If a data object is already registered with the object cache component 303B, a pointer to that object is returned. If the object is not registered with object cache component 303B, datastore management component 308 is utilized to obtain the desired object or objects from the persistent store of database server 311. The newly obtained data object is registered with object cache component 303B, and the pointer to the data object is returned to the query sender.
- Server-side update management component 304B acts in association with change management component 302B to ensure that notices regarding changes to data are transmitted to all interested elements of the system. Under the active notification scheme using interest objects, update management component 304B maintains a registry of clients and other servers that wish to be notified when a designated data object is changed. When a change is made, interested elements within application server 307 and interested clients receive notification of the change. Notification within each client is typically resolved by the respective client-side update management component 304A.
- Server-side query management component 312B receives query objects from the client tier, from other application servers, or from components of application server 307. Query objects thus obtained are resolved against server-side object cache 303B if only object IDs are specified by the query. If the query object cannot be resolved against object cache 303B, either because the requested objects IDs are not in the hash table or because the query is not in the form of object IDs, query management component 312B passes the query object to datastore management component 308 to be processed.
- Datastore management component 308 responds to calls from the server-side change management component 302B by making API calls to JDBC component 309 to create, delete or mutate persistent data within database server 311.
- Datastore management component also responds to query objects by submitting database requests to the database server. The results of the database requests are then encapsulated into one or more corresponding data objects. If a data object resulting from a query is already in the server-side object cache component 303B, the cached data object is returned. If the data object is not in server-side object cache component 303B, a new data object is obtained, via factory method calls directed to a data class factory object, to encapsulate the data. Typically, the factory method calls result in the instantiation of a desired data object class. However, in other embodiments, the new data object may be obtained from a pool of available data object instances. The new data objects are assigned ID numbers, loaded with appropriate data from database server 311, and returned.
- Datastore management component 308 performs the conversion from queries encapsulated in query objects to corresponding database calls by resolving the queries with database tables.
- the JDBC component 309 provides the conversion between general database calls made by datastore management component 308 and database-specific commands (e.g., SQL) and communication protocol required by the particular implementation of database server 311 (e.g., Oracle, Sybase, etc.).
- Connection 310 represents the communication link between JDBC component 309 and database server 311.
- other database connectivity components may be used in place of or in addition to JDBC component 309.
- Database server 311 may be any form of structured persistent store.
- database server 311 may comprise a flat-file data management system, a relational database management system (RDBMS), an object-oriented database management system (ODBMS), etc.
- RDBMS relational database management system
- ODBMS object-oriented database management system
- the organization of the database may be represented by one or more database tables wherein each column of the table represents a particular data attribute having a specified database type. Each row represents a set of attribute values associated with a particular index.
- each row of a database table is associated with a particular data object, and each table is associated with a data object class. Each column therefore specifies an attribute of the given data object class.
- the database organization may be independent of the data object classes in the client and application tiers.
- the datastore management component 308 handles mapping of the data objects to the database.
- the database tables are generated during, or prior to, system start-up from schema information.
- FIG. 8 illustrates the use of data objects, change objects and query objects in the client and application tiers in accordance with one embodiment of the invention.
- the client tier comprises application logic 301A, object cache 303A, and update management component 304A.
- the application tier comprises object cache 303B, datastore management component 308 and update management component 304B.
- data objects 800A and 800B reside in object cache 303A and object cache 303B, respectively.
- a transaction is initiated that includes the creation of a change object and the propagation of that change object to the database.
- Change object 802 is transmitted to the application tier, as indicated by arrow 805, where change object 802 is applied to corresponding data object 800B.
- Changed data object 808 is then applied to the database through datastore management component 308, as indicated by arrow 806.
- update management component 304B is informed of the change, as indicated by arrow 807.
- Interested clients are identified by update management component 304B, and a notice of the change is transmitted to the update management component 304A of the interested clients, as indicated by arrow 812.
- the client update management component 304A determines, based on an interest registry, which elements on the client should receive notification of the change.
- the data objects in object cache 303A are typically updated at the time the client is notified of the change.
- datastore management component 308 When application logic 301A makes a database query that cannot be resolved directly by an object cache, the query is transmitted, as shown by arrow 808, to datastore management component 308 in the form of query object 803. Transmission of query object 803 is performed under management of client-side and server-side query management components (not shown). In response to the query, datastore management component 308 returns, as shown by arrow 811, corresponding data objects 801A and 801B which are registered with the client-side object cache 303A and server-side object cache 303B, respectively. As part of the query process, interest in data objects 801A and 801B is registered with update management components 304A and 304B, as shown by arrows 809 and 810, respectively.
- FIG. 9 illustrates relationships between the design time and run time environments of an embodiment of the invention.
- the design time environment is associated with the generation of class definitions for one or more data classes, a factory class and a schema class, based on application-specific schema metadata.
- the run time environment is associated with the execution of the three-tier application (as illustrated in FIGS. 3 and 8) in which instances of the classes generated in the design time environment are integrated with the components of the three-tier application.
- data objects in the run time environment are created as instances of the data glasses generated in the design time environment.
- An instance of the generated factory class is used in the run time environment to obtain the data object instances.
- an instance of the generated schema class is used in the run time environment to structure the database at initial start-up, and to provide a facility for accessing schema metadata at run time.
- the design time environment comprises schema metadata 900, code generator 901, and generated code 902.
- Generated code 902 further comprises client data class 903, data object interface 904, application (i.e., server) data class 905, factory class 906 and schema class 907.
- client data class 903, one data object interface 904 and one application data class 905 are generated for each data class described by schema metadata 900.
- Data classes 903 and 905 include metadata describing the attributes and methods, for example, of the respective class.
- Schema class 907 includes metadata describing the data management of the system in terms of metaclasses and their constituent elements. The processes of code generation in the design time environment are described in further detail in following sections of this specification.
- the run time environment comprises the components of the client, application and database tiers as earlier described with respect to FIG. 3.
- the client tier comprises one or more clients (300A) having application logic and GUI component 301A, change management component 302A, object cache component 303A, update management component 304A, query management component 312A and communication management component 305A.
- the application tier comprises one or more application servers (307) having communication management component 305B, application logic 301B, change management component 302B, object cache component 303B, update management component 304B, query management component 312B, datastore management component 308 and JDBC component 309.
- the database tier comprises one or more database servers (311).
- the client and application tiers are joined by connection 306, and the application and database tiers are joined by connection 310.
- handling of change objects is performed by change management components 302A and 302B at the client and server tiers.
- Query management components 312A and 312B at the client and server tiers handle query object operations, such as resolving queries against a respective object cache or forwarding to another tier or to the data store component for handling.
- Object cache components 303A and 303B manage data objects for client 300A and application server 307, respectively.
- the client data objects are obtained for object cache component 303A in the form of instances of client data classes 903 generated in the design time environment.
- application data objects in object cache component 303B are obtained in the form of instances of application data classes 905.
- Corresponding data objects in the client and application tiers implement the same shared data object interface 904 generated in the design time environment.
- arrow 908 is used to illustrate the propagation of a change transaction through the three-tier system.
- the transaction begins in application logic and GUI component 301A, when the application logic initiates a change to a data object, for example, by calling one of the data object's attribute "set" accessor methods.
- the data object calls change management component 302A, where a corresponding change object is obtained.
- Change management component 302A adds the change object to a list of change objects associated with a single transaction. Other change objects may be added to the list before the transaction is closed, for example, due to receipt of an "end of transaction" call.
- change management component 302A When the transaction is closed, change management component 302A provides the list of change objects to communication management component 305A.
- Communication management component 305A serializes and transmits the list of change objects to communication management component 305B at application server 307.
- Communication management component 305B deserializes the list of change objects and provides them to change management component 302B.
- Change management component 302B then applies the list of change objects to the application data objects in object cache component 303B.
- the updated data objects in object cache component 303B are passed to data store management component 308.
- Datastore management component 308, in association with JDBC component 309, converts the updated data objects into database calls (e.g., SQL calls) to database server 311 to update the database records corresponding to the updated data objects.
- database calls e.g., SQL calls
- change management component 302B uses the list of change objects to "undo" the changes made to the data objects in object cache component 303B and sends notification to client 300A that the transaction failed to commit. If the datastore management component 308 receives confirmation of a successful update from the database server, update management component 304B is notified of the updated data objects in object cache component 303B. Update management component notifies all interested components on application server 307, and sends update notifications to all other interested servers and interested clients.
- the update notification to the client includes the updated data objects.
- Communication management component 305B serializes the data objects and transmits them to communication management component 305A.
- Communication management component 305A extracts the object IDs from the serial stream and determines whether those data objects exist in object cache 303A. If a data object already exists, the values of the data object are updated with the values of the corresponding serialized data object. If a data object does not exist in the object cache, a new data object instance is placed in object cache component 303A and loaded with the values of the corresponding serialized data object.
- update management component 304A is notified of the updated data objects in the object cache.
- Update management component 304A proceeds to notify all interested components of client 300A of the updated data objects. The transaction is completed when the initiating element of application logic and GUI component 301A receives notification of the changed data objects.
- the change objects may be applied to the data objects in object cache component 303A at the time an "end of transaction" is signalled.
- object cache component 303A would not need updating just prior to notifying update management component 304A of the updated data objects.
- any "undo" operation would include undoing data object changes in object cache component 303A.
- metadata is associated with each data object class.
- the metadata describes the elements of each data class in terms of, for example, attribute and method names, parameters, data types, inter-class relationships, etc.
- the "schema” is a description of the three-tier system, and comprises the metadata for all of the data classes associated with the system.
- the schema is utilized in the design time environment (i.e., during the building stage of development) to automate production of data class definitions for the client and application tiers, and to automate production of a factory class for instantiating those data classes. Redundant programming is therefore reduced. Further, data class definitions generated in this manner can be easily configured with interfaces that conform to expected data object specifications for integration with other components of the three-tier system.
- a schema object may be generated that contains the schema metadata for informational access by components of the three-tier system.
- Components may access the metadata in instances of these metaclasses at runtime to determine the attributes that make up the associated data class and the methods for interfacing with that data class.
- the schema is also utilized to create the database tables that are used to organize the database.
- commands such as SQL "create table” commands, can be generated and used by the datastore component to structure the database at start-up.
- FIG. 4 is a flow diagram illustrating a process for utilizing system schema to build a three-tier application with automated code generation in accordance with an embodiment of the invention.
- the schema describing the data classes to be used in the system is obtained.
- the metadata for the data classes is extracted from the schema.
- the metadata thus extracted is used, in step 402, to create data class definitions (e.g., ".java" files) for the application tier and the client tier.
- data class definitions e.g., ".java" files
- the actual implementation for the different tiers may differ, but the attributes and method calls are the same.
- an interface definition specifying the common method interface for the application and client tiers may also be created.
- a factory class is created that provides one or more factory methods for obtaining instances of the data classes described by the metadata.
- database tables are created from the schema metadata by formulating "create table" commands from the class and attribute descriptions within the metadata. It will be obvious that steps 402 and 403 may be performed in any desired order. Step 404 is typically performed at run time during initial start-up.
- the schema may be provided as a text file listing the different elements of each data class with known delimiters between each element or portion of elements.
- An example of a text file schema for a data class is provided below.
- the individualized schema entries are shown within " ⁇ >" symbols.
- Optional entries are shown inside of parentheses.
- a parsing program may be used to extract the schema metadata from the above text file.
- the metadata thus extracted may, for example, be stored in metadata structures and applied to class and table generation processes within a generator mechanism.
- the above text schema format may be expanded to include other metadata entries not illustrated in the example, such as constants or relationships with other classes.
- the schema may also be provided in a coded format where the schema file is implemented as a series of commands or method calls with the schema data provided as command or method parameters. For example, methods such as newClass(), newAttribute(), newMethod() and newParameter() could be used to specify the entry of the corresponding element. Those methods may then be defined to facilitate the setting of metadata attribute values and flags in metadata structures. By compiling the schema file and executing the method calls, the schema metadata may be extracted and loaded directly into the desired data structures, with the desired flags automatically set in accordance with the specified methods.
- An example of a coded schema file for a sample class is provided below. The individualized schema entries are shown within " ⁇ >" symbols.
- Line (1) obtains a new metaclass instance and assigns class name and superclass values to metaattributes within a new metaclass.
- Line (2) sets the value of a class version metaattribute in the new metaclass to ⁇ versioninfo>.
- Line (3) writes a string containing import information into an import data structure such as a Vector.
- a "Vector" is a data type of the Java programming language that comprises an array of elements that may be of any data type and of any length. Data types other than the Vector data type may also be used to store metadata.
- Line (4) establishes a new metaattribute within the metaclass to describe an attribute within the current class. Boolean flags within the metaattribute are set to specify that the attribute is private, persistent and non-null.
- the attribute is a string data type with the name ⁇ attributename>.
- the sequence of method calls coupled by ".” is typically evaluated from left to right. Each method call returns an object that acts as the implementor of the next method call in the sequence. For example, in line (4), the method call newAttribute() returns a metaattribute instance. The private() method of the metaattribute instance is then called which sets a private flag of the metaattribute and returns the metaattribute for the next method call. The persistent() method similarly sets a persistent flag of the metaattribute and returns the metaattribute, and likewise with the nonNull() method. The string -- () method associates a metadatatype of type string with the current metaattribute and returns the metaattribute. The name() method sets a name string in the metaattribute to the value of "attributename".
- a second metaattribute is established to describe a second attribute. Again, flags are set to specify that the attribute is private, persistent and non-null.
- the data type specified within the metaattribute is an object data type of the class ⁇ classname>.
- the name of the attribute is ⁇ attributename>.
- Line (6) establishes a metamethod to describe a method of the current class.
- a flag is set to specify that the class is public.
- the method returns an object data type of class ⁇ classname>, and the methods name is ⁇ methodname>.
- metaparameters are associated with the metamethod of line (6).
- Line (7) specifies an object data type parameter of class ⁇ classname>, and having a parameter name of ⁇ parametername>.
- Line (8) specifies an integer data type parameter having a parameter name of ⁇ parametername>.
- Lines (9) and (10) write individual lines of the method to a method body data structure (such as a Vector) as data strings.
- standard methods such as constructors and accessors are not required to be specified. Those standard methods are automatically generated in a standardized manner when class definitions are created from the metadata. Further, reflection methods, whereby other objects are able to access the attributes of an object by specifying an attribute ID to a general method, may also be automatically generated for each class.
- Simple method calls or flag indicators similar to those shown above may be added to the schema description to trigger the automatic generation of other standardized methods.
- certain classes may wish to instantiate other classes to fill an object data type attribute.
- an offerNewMethod () call may be added to the attribute command sequence to specify the automatic creation of "New” methods during class generation.
- These "New” methods may use a standard "try-catch” method format to "try” to obtain a new instance of a data class from a class factory, and to "catch” any exception generated by a failure to obtain the desired class instance.
- FIGS. 5A and 5B illustrate embodiments of metadata structures for storing metadata in accordance with an embodiment of the invention.
- FIG. 5A comprises MetaSchema 500, MetaClass 501, MetaMember 502, MetaAttribute 503 and MetaMethod 504.
- FIG. 5B comprises MetaParameter 505 and MetaDataType 506.
- One or more values within the metadata structures may be null, depending upon the class or class element being described by the metadata structures.
- MetaSchema 500 comprises a string data structure, "mySchemaVersion,” that stores schema version information such as a version date. Also, MetaSchema 500 comprises a Vector data structure, "myCoreClasses,” containing the set of MetaClasses describing the data classes of the system. Further Vector structures may be defined for metaclasses associated with other system classes aside from data classes, and for the entire set of system classes including data classes and non-data classes (i.e., those classes associated with system components 302A-305A, 302B-305B and 306-308). A reference (“myFactoryClass”) to the generated factory class is also contained within MetaSchema 500.
- MetaClass 501 comprises a reference, "mySchema,” to its associated MetaSchema, and a reference, "mySuperClass,” to the MetaClass instance describing the superclass of the current class.
- String data structures, "myClassName,” “myClassVersion” and “myChangeObject,” store the name of the class, the version of the class and the name of the class's change object, respectively.
- Boolean flags, "myAbstractFlag,” “myPersistentFlag” and “myInterfaceFlag,” indicate whether the described class is abstract, persistent and/or an interface, respectively.
- MetaClass 501 shown comprises six Vector data structures: "myAttributes,” “myMethods,” “myImports,” “myCode,” “myInterfaceCode” and “myPassedMethods,” “myAttributes” is a Vector of MetaAttribute instances describing the attributes of the current class. Similarly, “myMethods” is a Vector of MetaMethod instances describing the methods of the current class. "myImports” is a Vector of string instances containing class filenames for import into the current class. “myCode” is a Vector of string instances describing the lines of programming code for inclusion in the current class.
- myInterfaceCode is a Vector of string instances describing lines of programming code for inclusion in an interface for the current class.
- myPassedMethods is a Vector of MetaMethod instances passed by other MetaClasses to the current MetaClass instance.
- a "passed method” refers to the case where an originating class contains a method that invokes a similarly named method of a subsequent class in which the desired method steps are implemented. The originating class is said to "pass” the method to the subsequent class.
- MetaMember 502 is, in this embodiment, a superclass of MetaAttribute 503 and MetaMethod 504.
- the attributes of MetaMember 502 are included in MetaAttribute 503 and MetaMethod 504 by extension, as are those methods of the superclass not overridden by the subclasses.
- the elements of the MetaMember class may be explicitly defined for MetaAttribute 503 and MetaMethod 504 without the use of a MetaMember superclass.
- MetaMember 502 comprises an integer data structure containing "myPrivateFlag.”
- "myPrivateFlag” describes the private and protected state of the class element described by MetaMember 502.
- a reference, "myDataType,” is stored to a MetaDataType instance describing characteristics of the data type associated with the current class element.
- a string structure, "myName,” contains the name of the element as a character string.
- a reference, “myOwningClass” refers to the MetaClass instance describing the class of which the current element is a part.
- a Vector of string data structures, "myComment” is maintained which stores, as character strings, lines of comments to be associated with the current element.
- MetaAttribute 503 comprises boolean structures "myPersistentFlag,” “myNullFlag,” “myOfferNewMethodFlag,” “myPrimaryKeyFlag” and “myIndexFlag.”
- “myPersistentFlag” indicates whether the current attribute is persistent, requiring storage in the database.
- “myNullFlag” specifies whether the current attribute is allowed to have a null value.
- “myOfferNew-MethodFlag” specifies whether a "New” method is to be generated for obtaining a new instance of the current attribute's data type from, for example, a class factory.
- myPrimaryKeyFlag specifies during database table generation that the current attribute is a primary key for the table.
- “myIndexFlag” may also be used during database table generation.
- MetaAttribute 503 further comprises the following string data structures: "myDefaultValue” specifying a default attribute value as a character string, "myMirrorCollectionClassName” specifying the class name of the elements contained in the Vector represented by the current attribute (if applicable), “myMirrorAttributeName” specifying the name of a mirror attribute in each element of the Vector represented by the current attribute (if applicable), and “myChangeObject” specifying the name of the change object class associated with the attribute.
- a reference, “myMirrorCollectionClass” refers to the MetaClass instance describing the associated mirror collection element class. Also, a reference, “myMirrorAttribute,” refers to the MetaAttribute instance describing the associated mirror attribute.
- a mirror collection refers to a collection or set of elements where those elements are instances of a class (i.e., the "mirror collection class").
- Each class instance within the mirror collection may contain an attribute (i.e., the "mirror attribute") that is a reference to an owning class of the mirror collection.
- a scheduling application may include an appointment class to represent meetings and an invitation class to represent an individual invited to attend a given appointment.
- Each appointment instance may contain a collection (e.g., an "invitations" Vector) of invitation instances representing the individuals invited to the given appointment.
- the invitation instances in turn, contain a reference (i.e, a "mirror attribute") to the appointment instance containing the "invitations" Vector of which they are a part.
- respective MetaClass instances are used to describe the appointment class and the invitation class. Further, a "mirror collection" MetaAttribute instance within the appointment MetaClass instance is used to describe the invitations Vector. A "mirror attribute" MetaAttribute instance within the invitation MetaClass instance refers to the appointment MetaClass instance.
- MetaMethod 504 comprises a string structure, "myThrowsType,” that specifies the exception type, if any, thrown by the current method being described.
- MetaMethod 504 comprises two Vector data structures, "myParameters” and “myBodyParts.”
- “myParameters” is a Vector of MetaParameter instances describing the individual parameters of the current method.
- “myBodyParts” is a Vector of string structures for storing lines of method code as individual character strings.
- a reference, “myPassToAttribute” refers to the MetaAttribute instance describing an attribute to forward the method call to, if applicable.
- a boolean structure, "myPassThisFlag,” specifies whether to include "this” as a parameter in a forwarded method.
- MetaParameter 505 comprises a string structure, "myName,” specifying the parameter name as a character string.
- MetaParameter 505 further comprises a reference, "myDataType,” to a MetaDataType instance describing the data type of the parameter.
- MetaDataType 506 comprises a Vector of MetaDataType instances labeled "ourTypes.”
- the MetaDataType class has a method for populating "ourTypes" with a number of MetaDataType instances with stored metadata corresponding to different data types. "ourTypes" may be used as a library of information on data types, with methods for accessing a specific MetaDataType instance by token value.
- the integer data structure, "myToken,” stores the token value assigned to a given MetaDataType instance.
- a string data structure, "myTokenName,” stores the character string representing the token name assigned to the given MetaDataType instance.
- String structure "myJavaDeclaration” specifies a character string for declaring, in the Java programming language, the data type described by the MetaDataType instance.
- the string structure, "myJavaInterfaceDeclaration,” specifies a similar character string for declaring the current data type if the data type is an interface type. Other programming language declarations could be similarly represented, either alternatively or additionally.
- String structures “myDatabaseDeclaration” and “myDatabaseLength” are used in the construction of database tables. “myDatabaseDeclaration” specifies the character string for the database data type, and “myDatabaseLength” specifies the character string for the length of the data type in the database.
- MetaDataType 506 further comprises a reference, "myReferenceType," to a MetaClass Instance, if the MetaDataType instance corresponds to an object class described by a MetaClass.
- String structure "myObjectifier” specifies an objectifier for the MetaDataType instance
- string structure "myDeobjectifier” specifies a deobjectifier.
- Objectifiers and deobjectifiers are used respectively to convert certain non-class data types into corresponding class data types, and to convert class data types into non-class data types.
- an objectifier may be used to convert an integer variable into an Integer class instance containing the integer variable value, as well as certain methods for operating on the integer variable value.
- Boolean structure "myPassByCopyFlag" whether the represented data type is passed directly, or whether the data type is first duplicated with the copy being passed.
- String structure “myCollectionContentName” specifies, for a data type containing a collection of objects, what the class name is for the elements in the collection.
- String structure “myNullValueString” stores the null value for the current data type. Examples of null values include “null", "-1", etc.
- FIG. 6A is a flow diagram of a process, in accordance with an embodiment of the invention, that generates the class and interface definitions referred to previously with reference to step 402 of FIG. 4.
- the schema metadata is obtained to facilitate the automated class generation.
- the metadata may be, for example, provided in form of the metadata structures described with reference to FIGS. 5A and 5B.
- the first metaclass is obtained from the schema metadata.
- the metaclass comprises metadata descriptions of the properties of the class, its attributes, and its methods.
- Steps 602-604 involve building the class definition files for the application and client tiers, as well as building the shared interface file, and may be performed in any order.
- a class building operation is performed to write the class definition for the application tier.
- the class building operation uses the metadata to provide standard declarations, and to generate standard methods, such as constructors, accessors, "new" methods and reflection methods.
- the class definition is typically written to a new file in a location within the file system used for storing code associated with the application server.
- an additional template class definition is generated that is a substantially empty subclass of the first class (or "base class") definition (i.e., the template contains little or no code in the form of additional attributes or methods).
- the base class may be declared as an abstract class. A developer can easily expand the capabilities of the respective base class by, for example, filling in the template with further attributes and methods as desired.
- a class building operation is performed to write the class definition for the client tier.
- the class building operation uses the metadata to provide standard declarations, and to generate standard methods, such as constructors, accessors, "new" methods and reflection methods.
- the class definition is typically written to a new file in a location within the file system used for storing code associated with a client application. Similar to the application tier, an additional template class definition may also be generated for the addition of further client specific code.
- the class definitions for the application and client tiers share the same common interface, though the implementation of the interface may differ between the tiers.
- the interface is generated in step 604, and comprises, for example, a list of import classes, a series of constant declarations (e.g., for token values assigned to the individual class attributes), and a series of public method declarations.
- the interface is written to a location in the file system containing code files common to the application tier and the client tier. The location of the interface file is included as an import in the class definitions generated in steps 602 and 603.
- step 605 if there are no further metaclasses, the process ends (step 607). However, if further metaclasses remain in the schema metadata, the next metaclass is obtained in step 606, and the process returns to step 602 to generate class definition code from the next metaclass.
- FIG. 6B illustrates, in accordance with an embodiment of the invention, the process of the class building operation carried out in each of steps 602-604 of FIG. 6A.
- character strings for building the class definitions are depicted within quotes. Each string may be written to the respective class file using known print commands. Elements inside of " ⁇ >" are evaluated to fill the character string.
- an interface declaration and one embodiment for writing the interface declaration to a file are provided below.
- the print command uses a tabprintln() method of a print stream instance (ps). MetaClass access methods, getName() and getSuperClass(), are used to obtain the interface and superclass names to provide evaluation of elements within " ⁇ >".
- generated methods for each class implement a "try-catch" format or construct.
- the try-catch format appears as:
- the "try” sequence of operations (or a single operation) is executed. If one of the "try” sequence operations throws an exception, the "catch" sequence is executed.
- the try-catch format is advantageous because it allows for problems to be identified at runtime through the issuance of exceptions, and it provides the opportunity for action to be taken to handle those exceptions thrown (e.g., display an appropriate error message to a user based on the type of exception thrown).
- case statements are described for directing executional flow based on the result of a test, such as the matching of a token value.
- Other forms of conditional statements such as "If" statements, may be similarly applied to control executional flow.
- a class file can include some or all of the following: a class header, declarations (e.g., constant and variable declarations), program code (e.g., general code, methods, and constructor methods) and/or a footer.
- the class header is written.
- the class header may comprise elements such as a header comment, a package declaration, a list of import declarations, class comments and a class declaration.
- any constant declarations are written to the class definition file.
- a comment preface to the section e.g., "//constants", etc.
- integer attribute tokens may be assigned to each attribute. Access may then be made to each attribute using a general reflection method which includes an attribute token value as a parameter.
- the integer attribute tokens are declared as constants in the common interface during step 609.
- a chain of classes is formed from the highest superclass in the hierarchy (i.e., the superclass that does not itself have a superclass specified, or the highest superclass that is not a general framework class) to the current class.
- Each attribute in the chain of classes is enumerated and assigned an attribute token that is declared as a constant.
- each attribute is given a token name, for example, by changing the attribute name to all capital letters (for constant naming conventions), and appending "ATTRIBUTE -- TOKEN -- " as a prefix.
- Each attribute token is then assigned a different token value by incrementing the token value after each attribute token assignment.
- the list of constants may be written to the common interface in the following form:
- the variable declarations are written based on the schema attribute metadata for the current class (e.g., the Vector of MetaAttribute structures).
- Each MetaAttribute is enumerated and its MetaDataType queried to determine the corresponding declaration (e.g., "myJavaDeclaration") for the given programming language.
- the variable name may be generated by, for example, adding the prefix "my" to the attribute name.
- An example of a variable declaration string for a single attribute is:
- variable declarations are generated in the same manner for the client and server base classes. In accordance with an embodiment of the invention, variable declarations are not automatically generated for the common interface and the template classes.
- step 611 general code is written to the class file in an automated fashion.
- the general code comprises the character string elements of the Vector "myCode” for the current MetaClass.
- the general code comprises the character string elements of the Vector "myInterfaceCode” for the current MetaClass.
- Each string element is enumerated from the respective Vector, and written to the class file.
- general code is not written to the template classes.
- a standard constructor is written to the class file.
- the automated constructor may include setting default values for the variables (attributes). The default values may be determined by enumerating the MetaAttributes of the MetaClass, and determining a default value from the MetaAttribute metadata and the corresponding MetaDataType.
- An example of a constructor is as follows:
- step 613 the methods of the class file are written. No methods are written to the template classes because the methods are inherited from the base classes. Only the method declarations are written to the common interface. "New” method code is generated for those MetaAttributes whose "myOfferNewMethodFlag" is true. Method code is generated for each of the methods specified in the Vector "myMethods" of MetaMethod elements. Accessor methods are generated for the class variables (i.e., for the attributes described by the MetaAttributes in the Vector "myAttributes"). Also, reflection methods are generated that allow for the attributes to be accessed by attribute token.
- the footer is generated for the base classes, template classes and the common interface.
- the footer comprises a close bracket symbol " ⁇ " that corresponds to the open bracket symbol generated in the class header.
- the class header comprises a header comment, a package declaration, a series of import declarations, class comments, and a class declaration.
- the header comment may include, for example, a standard copyright notice and/or the date of class generation.
- the automated code generation writes the comment to the file (with appropriate comment line symbols, e.g., "/*" or "//"), for example, using known file print commands.
- the class comments may comprise more class-specific comments, and may be written to the class file in the same manner as the header comment.
- the package declaration typically corresponds to the target directory for the class file which depends on whether the class definition is being generated for the client tier ("client") or application tier ("server”), and whether the class definition is a base class, a template, or the shared interface.
- a case statement may be used to write the appropriate package declaration based on the target, where the target is one of the following: client base class, client template class, server base class, server template class, or common interface.
- An example set of packages for class targets is given below:
- the imports for the current class are determined by target.
- the path name for the package containing the interface is declared as an import.
- the path names for other elements of the three-tier framework that may be integrated with the generated class, such as change objects, may be declared as imports as well.
- the string elements of the import Vector "myImports" are enumerated to form import declarations that are added to those already written to the class file.
- the template class files may forego the addition of imports.
- the class declaration is also target dependent.
- the interface name may be generated by, for example, appending a standard interface suffix, such as "Def,” to the class name specified in the metadata. If there is a superclass specified in the metadata, an "extends" phrase may be added to the declaration which specifies a superclass interface name.
- the superclass interface name is generated by appending the interface suffix to the superclass name. If there is no superclass, then the extends phrase is omitted.
- the declaration for the interface is as follows:
- the superclass is assumed to be "Object" if no superclass is specified.
- the class declaration for the client and server base classes is, for example:
- the superclass is the respective client or server base class with the pathname (as given by the target packages) for the base class appended as a prefix to the class name.
- the respective declarations are:
- New methods (“new ⁇ attributeName>,” not “new ⁇ constructor>”) are provided for those attribute types, such as Vectors, that contain objects as elements.
- the "new” method provides a mechanism to obtain new instances of the object class forming each element of the Vector, and, in one embodiment, to initialize the mirror attribute of the new instance to refer to the class instance containing the Vector.
- the new class instances are obtained, for example, from the public store by invoking a method of the object representing the public store which returns a new instance for a specified class ID.
- the public store object calls a factory method of a class factory to construct the new class instance.
- the element "myCollectionContent-Name" of a MetaAttribute's associated MetaDataType is queried to determine the class name of the desired class instance to be created by the "new" method.
- the method declaration can then be generated as illustrated below, in terms of the desired class's corresponding interface (generally " ⁇ classname>Def”).
- the method name is generated by appending "new" as a prefix to the desired class name.
- a semicolon ";" is appended to the above method declaration.
- a method body is generated in a try-catch format, for example, to obtain a new instance or to catch an exception in the event a new instance is not obtained.
- the new instance is obtained by calling a method from a system component that handles the instantiation of the desired class within the context of the database.
- the following example of a "new" method body is provided in accordance with an embodiment of the invention.
- the method body incorporates the use of the factory class (e.g., from "myFactoryClass”) for lookup of class token values, and assumes the base class is a subclass of a "StoredObject” class that supports the use of a public store (e.g., in the form of an object cache component) that performs instantiation.
- the example form of the method body is:
- method declarations are added to the common interface. Those method declarations may include the comment strings specified in the respective string Vector “myComments" of the respective MetaMethod structure.
- the Java (or other programming language) declaration for the method's return data type is obtained from the data type metadata (e.g., from the MetaDataType structure "myDataType” of the MetaMethod), and the name of the method is obtained directly from the method metadata (e.g., "myName").
- the parameter data types and names are obtained by enumerating the MetaParameters of the MetaMethod and querying the associated MetaDataType of each MetaParameter. If the string "myThrowsType" is not null, a "throws" phrase is added to the declaration, including the specified data type.
- Example declarations in accordance with an embodiment of the invention are provided below:
- the client and server base classes receive the same general method declarations as shown above. Also, if the "myPassToAttribute" structure of the MetaMethod is null, the string elements of the Vector “myBodyParts" are enumerated and printed to the class file to complete the body of the respective method. If the "myPassToAttribute" is not null, meaning that the processing of the method is to be carried out by an identically named "passed" method of another class designated by "myPassToAttribute," the method body may be constructed, for example, as shown below, to make a further call to the other class and to return the result. The parameters of the new call include the same parameters as the current method with the addition of "this" to specify the current class as the caller, if "myPassThisFlag" is true. For example:
- the parameter list in the method declaration includes an entry for the calling class, such as by adding the corresponding class type or interface type of the calling class (e.g., " ⁇ className>Def") followed by "caller” as the standard parameter name for the calling class.
- Accessor methods are automatically generated for each attribute described in a MetaClass instance.
- the common interface receives the method declarations for the "Get” and “Set” accessor methods, whereas the client and server base classes receive the complete methods, including declaration and body.
- a further protected accessor method, "doSet,” is generated in one embodiment for use by certain instances of the "Set” method, as well as by the reflection methods.
- the protected "doSet” method is not included in the public interface of the class.
- the "Get” declaration is determined from the data type of the attribute and its corresponding Java (or other programming language) interface declaration.
- An example "Get" declaration is as follows:
- the "Get” accessor method is designed to return the value of the variable targeted by the method, or its corresponding null value if the variable value cannot be obtained.
- the "Get” accessor may simply return the variable value using the phrase "return ⁇ variable name>" within the try-catch format.
- method calls may be embedded in the generated code to access the "public store" for the variable value.
- the following two “Get” method forms are used, the first being used if "myMirrorCollectionClass” is null (i.e., the attribute is not a collection or set, such as a Vector of classes), and the second being used if "myMirrorCollectionClass” is not null.
- the "Set” accessor method is designed to write a value to the given variable (attribute), with the new value specified as a method parameter.
- attributes such as Vectors of classes (i.e., those attributes whose "myMirrorCollectionClass” is not null)
- no "Set” method is generated for collection attributes, such as Vectors of classes (i.e., those attributes whose "myMirrorCollectionClass” is not null).
- the declaration of the "Set” method may be generated as follows:
- the "Set” declaration alone is written to the common interface.
- the declaration and method body are written to the client and server base classes.
- the "Set” method initiates a transaction with the public store, obtains a change object with the appropriate attribute changes, performs the change using the change object, and ends the transaction with the public store.
- the "Set” method calls the "doSet” method.
- "Set” method body examples are provided below, with the first corresponding to a persistent attribute with a change object and the second corresponding to a nonpersistent attribute or one without an assigned change object. (Note: the attribute's "owning" class is the class containing the attribute.)
- "doSet” methods are not generated for collection attributes, such as Vectors of classes (i.e., those attributes whose "myMirrorCollectionClass” is not null).
- the "doSet” accessor methods are written to the client and server base classes, but, as stated previously, no declaration is written to the common interface for these protected methods.
- the "doSet” method is an internal method. Any transaction-based activities are handled by the caller. An example of a “doSet” method is provided below in accordance with an embodiment of the invention.
- the common interface receives the declarations, and the client and server base classes receive the full methods.
- the reflection methods provide access to the attributes of a given class, including those inherited from superclasses, through the specification of an AttributeInfo structure that contains the attribute token of the desired attribute.
- a case statement is used, for example, to call either the "Get” or "doSet” accessor method for the desired attribute, as appropriate, based on which reflection method is invoked and the resolution of the attribute token. Examples of "Get” related reflection methods in accordance with an embodiment of the invention are provided below.
- case code " ⁇ case #>" is:
- case code For attributes that do not reference user classes, the case code is:
- the "Set” related reflection method also uses a case statement to resolve attribute tokens for invocation of the appropriate accessor, in this case, the "doSet” method.
- Those attributes that represent a collection e.g., those attributes for which "myMirrorClassCollection” is not null
- An example of a "Set” related reflection method is provided below.
- the case code ("case #") takes the form of:
- user class files and interfaces are automatically generated from the schema metadata to reduce redundant programming effort, and to provide automated integration of the user class files with other elements of the three-tier framework.
- a factory object class is generated from the schema metadata.
- Classes that are part of the framework e.g., non-data objects
- a standard constructor is generated.
- Class tokens are generated as constant declarations by enumerating the MetaClass Vector "myCoreClasses" and individually assigning token names and token values. The token value is incremented between each new MetaClass.
- the token names may be assigned by adding a token prefix to each class name. For example, each token assignment may appear as a constant declaration as follows:
- a factory method is generated that will receive a token value (or some other reference that is transformed into a token value) and resolve a case statement based on the specified token value to instantiate the desired class.
- Abstract classes need not be included in the factory method as abstract methods are not instantiated.
- the factory class is generated for the server, the server template package is appended to the class name as a prefix for the class constructor.
- the client template package is similarly appended to the constructor.
- the factory method is configured to assign an "identity" class instance to the newly instantiated data class (or "core" class).
- the identity instance is set with a class identity value and a serial number.
- the public store is set for the new class instance before returning the class instance to the caller of the factory method.
- An example factory method is shown below:
- each data object is a subclass of the framework "StoredObject” class which is a subclass of a framework "AwareObject” class.
- the StoredObject class provides the inherited methods for communicating with the public store.
- the AwareObject class implements an IdentifiableDef interface that provides methods for accessing class information such as class ID and serial number (object ID).
- the AwareObject class also provides methods for obtaining a list of class attributes and token values, and for accessing attribute information via token value, for example.
- FIGS. 7A and 7B are flow diagrams illustrating a process for generating database tables from schema metadata in accordance with an embodiment of the invention.
- the processes of FIGS. 7A and 7B may be implemented, for example, within schema class 907 of FIG. 9, and executed by an instance of the schema class at run time during initial start-up.
- the database tables are generated through a "create table" command that specifies the table name (or relationship) and the attributes that make up the table.
- the following description refers to how to generate the a "create table” command from schema metadata.
- the embodiment described generates a separate create table command, and therefore a separate database table, for each MetaClass instance. Other embodiments may, for example, generate one database table for multiple MetaClass instances, or multiple database tables for a single MetaClass instance.
- An example of a create table command, in accordance with an embodiment of the invention, is provided below.
- the create table commands may be included together in a script format and submitted in a "create database” command set as shown below, for example.
- the process begins by obtaining the schema metadata in step 700.
- the first MetaClass instance is obtained from the schema metadata, for example, using an enumeration process on the Vector of MetaClasses "myCoreClasses.”
- a determination is made whether the current MetaClass is persistent, not abstract, and not an interface. If the MetaClass is abstract, is an interface or is not persistent, the process continues at step 710, bypassing generation of a "create table" command for the current MetaClass. If, however, the MetaClass is persistent, not abstract, and not an interface, the process continues at step 703, where the "create table" command is initiated, specifying the MetaClass class name as the relation or table name.
- Step 706 the superclass MetaClass is processed as described in steps 704-708 in a nested process ("A"). Nested process "A” can be executed recursively to process each superclass level in the class hierarchy. Step 706 ensures that attributes inherited from the superclass (and its superclass, and so on) are added to the "create table" command. After step 706, the process continues at step 707.
- step 709 the "create table" command is closed (e.g., by appending a close parenthesis ")"), and the command is submitted, via the data store management component, to the database management system to configure the database. If more MetaClasses remain, as determined in step 710, the next MetaClass is obtained in step 711, and the process returns to step 702. If there are no more MetaClasses in step 710, the process is completed.
- submission of the finished "create table” commands may also be performed as a set, as described above for a "create database” command set.
- FIG. 7B further describes the process of adding attribute database declarations to the "create table" command.
- the attribute database declaration has the following form:
- the first MetaAttribute instance is obtained from the MetaAttributes for the current MetaClass, for example, through an enumeration of Vector "myAttributes.”
- step 715 the MetaDataType instance of the current MetaAttribute instance is queried to determine the database type ("myDatabaseDeclaration") of the current attribute.
- step 716 the database type is added to the "create table” command to specify the column type.
- step 717 if the MetaDataType database length string "myDatabaseLength" is not "0,” in step 718, the database length is added to the "create table” command in the form "( ⁇ myDatabaseLength>)". Step 718 proceeds to step 719. If “myDatabaseLength" is "0,” the process proceeds from step 717 to step 719.
- Steps 719-723 handle the setting of the database null declaration.
- step 719 if "myPrimaryKeyFlag” is true, "PRIMARY KEY” is added to the "create table” command in step 720, and processing continues at step 724. If, in step 719, "myPrimaryKeyFlag” is false, processing continues at step 721. In step 721, if “myNullFlag” is true, “NULL” is added to the "create table” command in step 722, and processing continues at step 724. If, in step 721, "myNullFlag” is false, “NOT NULL” is added to the "create table” command in step 723 before proceeding to step 724.
- step 724 if any MetaAttribute instances remain for the current MetaClass instance, the next MetaAttribute instance is obtained in step 725, and the process returns to step 713. Otherwise, the process of entering attribute database declarations for the current "create table" command is complete.
Abstract
Description
______________________________________ CLASS <classname> (ABSTRACT) (INTERFACE) (PERSISTENT) (VERSION/"<versioninfo>") (SUPER/<superclassname>) (INTER/<intefacename>) { IMPORTS { <importstring>, <importstring>, ATTRIBUTES { <attributename> <datatype> (DEFAULT/<defaultvalue>), <attributename> <datatype> (DEFAULT/<defaultvalue>) } METHODS { <methodname> <datatype> (COMMENT/"<commentstring>") (THROW/<exceptionname>) (PRIVATE/<privateflagvalue>) { (PARAMETERS { <parametername> <datatype>, <parametername> <datatype> }) (BODY { "<methodstring>", "<methodstring>" }) } <methodname> <datatype> (COMMENT/"commentstring") (THROW/<exceptionname>) (PRIVATE/<privateflagvalue>) { (PARAMETERS { . . . }) (BODY { . . . }) } } } ______________________________________
__________________________________________________________________________ newClass = newCoreClass("<classname>", <superclass>); (1) newClass.setClassVersion("<versioninfo>"); (2) addImport("<importstring>"); (3) newAttribute( ).private( ).persistent( ).nonNull( ).string.sub.-- ( ).name("<attribut (4) ename>"); newAttribute( ).private( ).persistent( ).nonNull( ).object.sub.-- ("<classname>").n (5) ame("attributename>"); newMethod( ).public.sub.-- ( ).object.sub.-- ("<classname>").name("<method name>"); (6) newParameter( ).object.sub.-- ("<classname>").name("<parametername>"); (7) newParameter( ).int.sub.-- ( ).name("<parametername>"); (8) addBody("<methodstring>"); (9) addBody("<methodstring>"); (10) __________________________________________________________________________
______________________________________ "public interface <classname>Def extends <superclass>Def" ps.tabprintln("public interface" + getName( ) + "Def extends" + getSuperClass( ).getName( ) + "Def"); ______________________________________
__________________________________________________________________________ try { <"try" sequence of operations> } catch (Exception e) { <"catch" sequence of operations to be performed if an exception is caught> __________________________________________________________________________
__________________________________________________________________________ "public final static int ATTRIBUTE.sub.-- TOKEN.sub.-- <ATTRIBUTENAME1> = 0;" "public final static int ATTRIBUTE.sub.-- TOKEN.sub.-- <ATTRIBUTENAME2> = 1;" "public final static int ATTRIBUTE.sub.-- TOKEN.sub.-- <ATTRIBUTENAME3> = 2;" etc. __________________________________________________________________________
"private<myJavaDeclaration>my<attributename>;"
______________________________________ "public <classname>( );" "{" " super( );" " <attributename> = <defaultvalue>;" " <attributename> = <defaultvalue>;" etc. "}" ______________________________________
______________________________________ target package declaration ______________________________________ client base class "package com.cmpny.group.app.client.core.base;" client template class "package com.cmpny.group.app.client.core;" server base class "package com.cmpny.group.app.server.core.base;" server template class "package com.cmpny.group.app.server.core;" common interface "package com.cmpny.group.app.common.core;" ______________________________________
__________________________________________________________________________ superclass: "public interface <classname>Def extends <superclass>Def" no superclass: "public interface <classname>Def" __________________________________________________________________________
______________________________________ "public abstract class <classname> extends <superclass> implements <classname>Def" "{" ______________________________________
__________________________________________________________________________ client: "public class <classname> extends <clientBasePackage>.<classname>" "{" server: "public class <classname> extends <serverBasePackage>.<classname>" "{" __________________________________________________________________________
"public<desiredClassName>Def new<desiredClassName>()"
(e.g., "public SampleObjectDef newSampleObject()")
__________________________________________________________________________ "{" " try {" " SchemaInfoDef schema = getIdentity( ).getClassIdentity( ).getSchema( );" " ClassIdentityDef classID = schema.getClassForToken(<factory ClassNa me>.CLASS.sub.-- TOKEN.sub.-- <desiredClassName>);" " <desiredClassName>Def newInstance = (<desiredClassName>Def) (ge tPublicStore( ).newInstanceForClassIdentity(classID));" " newInstance.set<mirrorAttributeName>(this);" " return newInstance;" " } catch (exception e) {" " getPublicStore( ).handleException(e);" " return null;" " }" "{" __________________________________________________________________________
__________________________________________________________________________ (myThrowsType==null): "public <returnDataType> <methodName>(<parameter DataType> <parameterName>, <parameterDataType> <parameterName> <, ...>)" (myThrowsType!=null): "public <returnDataType> <methodName>(<parameter DataType> <parameterName>, <parameterDataType> <parameterName> <, ...>) throws <myThrowType>" __________________________________________________________________________
______________________________________ (myPassThisFlag): "{" " return get<attributeName>( ).<methodName>(this, <parameter>, <parameter>, <etc.>);" "}" (!myPassThisFlag): "{" " return get<attributeName>( ).<methodName>(<parameter>, <parameter>, <etc.>);" "}" ______________________________________
"public<dataType.JavaInterfaceDeclaration>get<attributeName>()"
__________________________________________________________________________ (myMirrorCollectionClass = null): "{" " try {" " if(getNeedsToBeReadFromStore( )) readFromStore( );" " return <variableName>;" " } catch (Exception e) }" " getPublicStore( ).handleException(e);" " return <nullValueString>;" " }" "}" (myMirrorCollectionClass != null): "{" " try {" " if (<variableName> == null) {" " <variableName> = new RelationshipAwareLiveSet(getPublicStore( ), getClassInfo( ).getAttributeForName("<attributeName>"), this);" " }" " return <variableName>" " } catch (Exception e) {" " getPublicStore( ).handleException(e);" " return <nullValueString>;" " }" "}" __________________________________________________________________________
______________________________________ "public void set<attributeName>(<dataTypeJavaInterfaceDeclaration> <attributeName>)" ______________________________________
__________________________________________________________________________ "{" " try {" " getPublicStore( ).beginTransaction( );" " <changeObjectName> changeObject = new <changeObjectName>(this, <attribute'sOwningClass'sInterfaceName>.ATTRIBUTE.sub.-- TOKEN.sub.-- <attributeName(all caps)>, <attributeName>);" " getPublicStore( ).performChange(changeObject);" " getPublicStore( ).endTransaction( );" " } catch (Exception e) {" " getPublicStore( ).handleException(e);" " }" "}" "{" " doSet<attributeName>(<attributeName>);" "}" __________________________________________________________________________
__________________________________________________________________________ "protected void doSet<attributeName>(<dataTypeJavaInterfaceDeclaration> <attributeName>)" "{" " try {" " if (getNeedsToBeReadFromStore( )) readFromStore( );" " <variableName> = <attributeName>;" " } catch (Exception e) {" " getPublicStore( ).handleException(e);" " }" "}" __________________________________________________________________________
______________________________________ " if (<variableName> == null)" " <variableName> = new <dataTypeJavaDeclaration>( );" " <variableName>.copy(<attributeName>);" ______________________________________
__________________________________________________________________________ "public Object getValueOrReferenceForAttribute(AttributeInfoDef attribute)" "{" " return getValueForAttribute(attribute, true);" "}" "public Object getValueForAttribute(AttributeInfoDef attribute)" "{" " return getValueForAttribute(attribute, false);" "}" "public Object getValueForAttribute(AttributeInfoDef attribute, boolean idOnly)" "{" " try {" " Object returnValue = null;" " switch(attribute.getAttributeToken( )) {" " <case 1>" " <case 2>" " <etc.>" " }" " return returnValue;" " } catch (exception e) {" " getPublicStore( ).handleException(e);" " return null;" " }" "}" __________________________________________________________________________
__________________________________________________________________________ " case <attribute'sOwningClass'sInterfaceName>.ATTRIBUTE.sub.-- TOKEN .sub.-- <attributeName(all caps)>:" " if (idOnly) {" " if (get<attributeName>( ) == null)" " returnValue = null;" " else" " returnValue = get<attributeName>( ).getIdentity( );" " } else {" " returnValue = get<attributeName>( );" " }" " break;" __________________________________________________________________________
__________________________________________________________________________ " case <attribute'sOwningClass'sInterfaceName>.ATTRIBUTE.sub.-- TOKEN .sub.-- <attributeName(all caps)>:" " returnValue = get<attributeName>( ):" " break; __________________________________________________________________________
__________________________________________________________________________ "public void setValueForAttribute(AttributeInforDef attribute, Object value)" "{" " try {" " switch(attribute.getAttributeToken( )) {" " <case 1>" " <case 2>" " <etc.>" " }" " } catch (Exception e) {" " getPublicStore( ).handleException(e);" " }" "}" __________________________________________________________________________
__________________________________________________________________________ " case <attribute'sOwningClass'sInterfaceName>.ATTRIBUTE.sub.-- TOKEN .sub.-- <attributeName(all caps)>:" " doSet<attributeName>((<dataTypeJavaDeclaration>)value);" " break;" __________________________________________________________________________
"public final static int CLASS.sub.-- TOKEN.sub.-- <className(all caps)>=<tokenNumber>;"
__________________________________________________________________________ "public IdentifiableDef newInstanceForReference(ReferenceDef ref)" "throws Factory Exception" " StoredObject newObject = null;" " try {" " ClassIndentityDef classId = null;" " Identity newIdentity = null;" " int classToken = ref.getClassIdentity( ).getClassToken( );" " switch (class Token) {" " case CLASS.sub.-- TOKEN.sub.-- <className(all caps)>:" " newObject = new <(server/client)templatePakcage>.<class Name>( );" " newIdentity = new Identity( );" " classId = getSchema( ).getClassForToken(CLASS.sub.-- TOKEN.sub.- - <className(all caps)>);" " newIdentity.setClassIdentity(classId);" " newIdentity.setSerialNumber(ref.getSerialNumber( ));" " newIdentity.setIdentitySpace(ref.getIdentitySpace( ));" " newObject.setIdentity(newIdentity);" " break;" " <further case statements - one for each non-abstract class>" " default:" " break;" " }" " if(newObject == null) {" " throw new FactoryException( );" " } else {" " newObject.setNeedsToBeReadFromStore(false);" " newObject.setPublicStore(getPublicStore( ));" " AttributeInfoDef aid = newObject.getClassInfo( ).getAttributeFor Token(CoreObjectDef.ATTRIBUTE.sub.-- TOKEN.sub.-- HASBEENDELETED);" " newObject.setValueForAttribute(aid, new Boolean(false));" " }" " } catch (SchemaException e) { }" " return newObject;" "}" __________________________________________________________________________
______________________________________ CREATE TABLE <className> ( <attributeDatabaseDeclaration>, <attributeDatabaseDeclaration>, <etc.> ) ______________________________________
______________________________________ CREATE DATABASE <databaseName> USE <databaseName> CREATE TABLE <className1> ( <attributeDatabaseDeclaration>, <attributeDatabaseDeclaration>, <etc.> ) CREATE TABLE <className2> ( <attributeDatabaseDeclaration>, <attributeDatabaseDeclaration>, <etc.> ) <etc.> ______________________________________
______________________________________ <attributeName> <attributeDatabaseType> <(<databaseLength>)> <"PRIMARY KEY"/"NULL"/"NOT NULL"> ______________________________________
Claims (7)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/092,610 US6085198A (en) | 1998-06-05 | 1998-06-05 | Integrated three-tier application framework with automated class and table generation |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/092,610 US6085198A (en) | 1998-06-05 | 1998-06-05 | Integrated three-tier application framework with automated class and table generation |
Publications (1)
Publication Number | Publication Date |
---|---|
US6085198A true US6085198A (en) | 2000-07-04 |
Family
ID=22234108
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/092,610 Expired - Lifetime US6085198A (en) | 1998-06-05 | 1998-06-05 | Integrated three-tier application framework with automated class and table generation |
Country Status (1)
Country | Link |
---|---|
US (1) | US6085198A (en) |
Cited By (225)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6236909B1 (en) * | 1998-12-28 | 2001-05-22 | International Business Machines Corporation | Method for representing automotive device functionality and software services to applications using JavaBeans |
US6278791B1 (en) * | 1998-05-07 | 2001-08-21 | Eastman Kodak Company | Lossless recovery of an original image containing embedded data |
US6298353B1 (en) * | 1998-11-19 | 2001-10-02 | International Business Machines Corporation | Checking serialization compatibility between versions of java classes |
US20010032207A1 (en) * | 1998-03-12 | 2001-10-18 | Bruce Hartley | Operational system for operating on client defined rules |
US6314430B1 (en) * | 1999-02-23 | 2001-11-06 | International Business Machines Corporation | System and method for accessing a database from a task written in an object-oriented programming language |
US6327628B1 (en) * | 2000-05-19 | 2001-12-04 | Epicentric, Inc. | Portal server that provides a customizable user Interface for access to computer networks |
US6330709B1 (en) * | 1998-03-30 | 2001-12-11 | International Business Machines Corporation | Virtual machine implementation for shared persistent objects |
US6338160B1 (en) * | 1998-12-08 | 2002-01-08 | Nazomi Communications, Inc. | Constant pool reference resolution method |
US6339841B1 (en) * | 1998-10-19 | 2002-01-15 | International Business Machines Corporation | Class loading model |
WO2002012982A2 (en) * | 2000-08-08 | 2002-02-14 | Object Services And Consulting, Inc. | Guided natural language interface system and method |
US6353836B1 (en) * | 1998-02-13 | 2002-03-05 | Oracle Corporation | Method and apparatus for transferring data from the cache of one node to the cache of another node |
US6363394B1 (en) * | 1999-03-18 | 2002-03-26 | Microsoft Corporation | Auto-generation of table neighborhoods |
WO2002029609A1 (en) * | 2000-10-05 | 2002-04-11 | Arzoon, Inc. | Software isolation of presentation and mark-up language using intermediate function language and library |
US20020066083A1 (en) * | 1998-12-08 | 2002-05-30 | Patel Mukesh K. | Java virtual machine hardware for RISC and CISC processors |
US20020087663A1 (en) * | 2000-12-28 | 2002-07-04 | Xerox Corporation | Remote order entry system and method |
US20020095403A1 (en) * | 1998-11-24 | 2002-07-18 | Sashikanth Chandrasekaran | Methods to perform disk writes in a distributed shared disk system needing consistency across failures |
US20020099729A1 (en) * | 1998-11-24 | 2002-07-25 | Oracle Corporation | Managing checkpoint queues in a multiple node system |
US6427228B1 (en) * | 1999-05-12 | 2002-07-30 | International Business Machines Corporation | Combining a meta data file and java source code to dynamically create java classes and javabeans |
US20020103810A1 (en) * | 2000-10-19 | 2002-08-01 | Kobi Menachemi | Dynamic building of applications |
US6434628B1 (en) * | 1999-08-31 | 2002-08-13 | Accenture Llp | Common interface for handling exception interface name with additional prefix and suffix for handling exceptions in environment services patterns |
US6434555B1 (en) * | 2000-01-24 | 2002-08-13 | Hewlett Packard Company | Method for transaction recovery in three-tier applications |
US20020112114A1 (en) * | 2001-02-13 | 2002-08-15 | Blair William R. | Method and system for extracting information from RFQ documents and compressing RFQ files into a common RFQ file type |
US6442552B1 (en) * | 2000-06-30 | 2002-08-27 | Hewlett-Packard Company | Method and apparatus for implementing three tier client asynchronous transparency |
US20020120792A1 (en) * | 2001-02-13 | 2002-08-29 | Free Markets, Inc. | Method and system for processing files using a printer driver |
US6446077B2 (en) * | 1998-09-21 | 2002-09-03 | Microsoft Corporation | Inherited information propagator for objects |
US20020156790A1 (en) * | 2000-11-17 | 2002-10-24 | Kagalwala Raxit A. | Mapping database file class to operating system file class in a computer schema |
US6477580B1 (en) * | 1999-08-31 | 2002-11-05 | Accenture Llp | Self-described stream in a communication services patterns environment |
US6477701B1 (en) * | 1999-09-30 | 2002-11-05 | Seiko Epson Corporation | Version-adaptive serialization and deserialization of program objects in an object-oriented environment |
US20020184612A1 (en) * | 2001-06-01 | 2002-12-05 | Hunt Joseph R. | Runtime configurable caching for component factories |
US20030004963A1 (en) * | 2000-11-17 | 2003-01-02 | Kagalwala Raxit A. | Mapping database users to operating system users in a computer schema |
US6504913B1 (en) * | 1998-06-10 | 2003-01-07 | Sun Microsystems Inc | Call handling mechanism |
US6507833B1 (en) * | 1999-09-13 | 2003-01-14 | Oracle Corporation | Method and apparatus for dynamically rendering components at run time |
US20030028682A1 (en) * | 2001-08-01 | 2003-02-06 | Sutherland James Bryce | System and method for object persistence life-cycle and object caching integration |
US20030028503A1 (en) * | 2001-04-13 | 2003-02-06 | Giovanni Giuffrida | Method and apparatus for automatically extracting metadata from electronic documents using spatial rules |
US20030061352A1 (en) * | 2001-09-27 | 2003-03-27 | International Business Machines Corporation | Optimized file cache organization in a network server |
US20030061316A1 (en) * | 2001-02-13 | 2003-03-27 | Freemarkets | Variable length file header apparatus and system |
WO2003030020A2 (en) * | 2001-10-02 | 2003-04-10 | Treewise Aps | Handling relational metanodes in databases |
US20030069758A1 (en) * | 2001-10-10 | 2003-04-10 | Anderson Laura M. | System and method for use in providing a healthcare information database |
US6549949B1 (en) | 1999-08-31 | 2003-04-15 | Accenture Llp | Fixed format stream in a communication services patterns environment |
US6570972B2 (en) | 1998-06-10 | 2003-05-27 | Microsystems, Inc. | Telephony control mechanism |
US6571282B1 (en) | 1999-08-31 | 2003-05-27 | Accenture Llp | Block-based communication in a communication services patterns environment |
US6574631B1 (en) * | 2000-08-09 | 2003-06-03 | Oracle International Corporation | Methods and systems for runtime optimization and customization of database applications and application entities |
US20030105732A1 (en) * | 2000-11-17 | 2003-06-05 | Kagalwala Raxit A. | Database schema for structure query language (SQL) server |
US6578044B1 (en) * | 1997-11-17 | 2003-06-10 | Sun Microsystems, Inc. | Method and system for typesafe attribute matching |
US6578068B1 (en) | 1999-08-31 | 2003-06-10 | Accenture Llp | Load balancer in environment services patterns |
US6591274B1 (en) * | 2000-05-31 | 2003-07-08 | Sprint Communications Company, L.P. | Computer software framework and method for accessing data from one or more datastores for use by one or more computing applications |
US6591276B1 (en) * | 2000-07-21 | 2003-07-08 | International Business Machines Corporation | Method and system for managing object types for objects defined externally to the system |
US6598093B1 (en) * | 1998-05-14 | 2003-07-22 | Sun Microsystems, Inc. | Method and apparatus for a core application programming interface |
US6601234B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Attribute dictionary in a business logic services environment |
US6601192B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Assertion component in environment services patterns |
US20030154233A1 (en) * | 1998-06-10 | 2003-08-14 | David John Martin Patterson | Scheduling processes for resource allocation |
US6615253B1 (en) | 1999-08-31 | 2003-09-02 | Accenture Llp | Efficient server side data retrieval for execution of client side applications |
US20030167257A1 (en) * | 2002-01-18 | 2003-09-04 | De Bonet Jeremy S. | Multi-tiered caching mechanism for the storage and retrieval of content multiple versions |
US20030167349A1 (en) * | 2001-04-23 | 2003-09-04 | Petri Krohn | Handling different service versions in a server |
US20030172370A1 (en) * | 2002-03-06 | 2003-09-11 | Sridhar Satuloori | Application programs with dynamic components |
US6636242B2 (en) | 1999-08-31 | 2003-10-21 | Accenture Llp | View configurer in a presentation services patterns environment |
US6637021B1 (en) * | 1999-06-30 | 2003-10-21 | Sun Microsystems, Inc. | JavaBean activation framework-common desktop environment bridge |
US6640249B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Presentation services patterns in a netcentric environment |
US6640244B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Request batcher in a transaction services patterns environment |
US6640238B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Activity component in a presentation services patterns environment |
US20030229849A1 (en) * | 2002-06-06 | 2003-12-11 | David Wendt | Web content management software utilizing a workspace aware JSP servlet |
US20030233373A1 (en) * | 2002-06-14 | 2003-12-18 | International Business Machines Corporation | Method, computer program product, and system for automatic class generation with simultaneous customization and interchange capability |
US20030233632A1 (en) * | 2002-06-12 | 2003-12-18 | Lockheed Martin Corporation | Automatically generated client application source code using database table definitions |
US20040002965A1 (en) * | 2002-02-21 | 2004-01-01 | Matthew Shinn | Systems and methods for cursored collections |
US20040006565A1 (en) * | 2002-07-08 | 2004-01-08 | International Business Machines Corporation | Method, apparatus and computer program product for mapping file handles |
US6681225B1 (en) * | 2000-05-31 | 2004-01-20 | International Business Machines Corporation | Method, system and program products for concurrent write access to a global data repository |
US20040015784A1 (en) * | 2002-07-18 | 2004-01-22 | Xerox Corporation | Method for automatic wrapper repair |
US20040019600A1 (en) * | 2002-07-23 | 2004-01-29 | International Business Machines Corporation | Method, computer program product, and system for automatically generating a hierarchical database schema report to facilitate writing application code for accessing hierarchical databases |
WO2004010298A1 (en) * | 2002-07-17 | 2004-01-29 | Collation, Inc. | Topology mapping of a multitier compute infrastructure |
US6687702B2 (en) * | 2001-06-15 | 2004-02-03 | Sybass, Inc. | Methodology providing high-speed shared memory access between database middle tier and database server |
US6697797B1 (en) * | 2000-04-28 | 2004-02-24 | Micro Data Base Systems, Inc. | Method and apparatus for tracking data in a database, employing last-known location registers |
US20040049544A1 (en) * | 2002-09-05 | 2004-03-11 | Hitachi, Ltd. | In-context launch management method, system therefor, and computer-readable storage medium |
US20040055002A1 (en) * | 2002-09-17 | 2004-03-18 | International Business Machines Corporation | Application connector parallelism in enterprise application integration systems |
US6714935B1 (en) * | 1998-09-21 | 2004-03-30 | Microsoft Corporation | Management of non-persistent data in a persistent database |
US6715145B1 (en) | 1999-08-31 | 2004-03-30 | Accenture Llp | Processing pipeline in a base services pattern environment |
US20040083234A1 (en) * | 2002-03-25 | 2004-04-29 | Takashi Higuchi | System, program and method for producing computer application |
US6742175B1 (en) * | 1998-10-13 | 2004-05-25 | Codagen Technologies Corp. | Component-based source code generator |
US6742015B1 (en) | 1999-08-31 | 2004-05-25 | Accenture Llp | Base services patterns in a netcentric environment |
WO2004046962A2 (en) * | 2002-11-18 | 2004-06-03 | Active Limited | Database management |
US6754670B1 (en) * | 1999-12-17 | 2004-06-22 | International Business Machines Corporation | Mapping relational tables to object oriented classes |
US6757670B1 (en) * | 1999-09-13 | 2004-06-29 | Hitachi, Ltd. | Method and system for query processing |
US6757708B1 (en) * | 2000-03-03 | 2004-06-29 | International Business Machines Corporation | Caching dynamic content |
EP1442398A1 (en) * | 2001-10-25 | 2004-08-04 | Bea Systems, Inc. | System and method for flushing bean cache |
US20040153469A1 (en) * | 2002-07-24 | 2004-08-05 | Keith-Hill Roderic M. | Database comparator |
US6778990B2 (en) | 2001-07-27 | 2004-08-17 | Hewlett-Packard Development Company, L.P. | Dynamic component activation method using a relational database as the repository for registration information |
US20040167975A1 (en) * | 2003-02-20 | 2004-08-26 | International Business Machines Corporation | Method, system, and program for managing devices in a network |
US20040172614A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Dynamic code generation method |
US20040172639A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Method for dynamically generating a wrapper |
US20040172613A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Dynamic code generation system |
US20040172640A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Dynamically generated wrapper |
US6792576B1 (en) * | 1999-07-26 | 2004-09-14 | Xerox Corporation | System and method of automatic wrapper grammar generation |
US20040181771A1 (en) * | 2003-03-12 | 2004-09-16 | Microsoft Corporation | Framework for supporting business software applications |
US20040181775A1 (en) * | 2003-03-12 | 2004-09-16 | Microsoft Corporation | Software business process model |
WO2004079512A2 (en) * | 2003-02-28 | 2004-09-16 | Bea Systems Inc. | Dynamic code generation |
US20040193651A1 (en) * | 2000-09-13 | 2004-09-30 | American Management System, Inc. | System and method for efficient integration of government administrative and program systems |
US6801919B2 (en) | 2001-07-27 | 2004-10-05 | Hewlett-Packard Development Company, L.P. | Object oriented database interface encapsulation that allows for chronologically overlapping transactions in a multi-threaded environment |
US6810400B2 (en) | 2000-11-17 | 2004-10-26 | Microsoft Corporation | Representing database permissions as associations in computer schema |
US20040215645A1 (en) * | 2002-01-08 | 2004-10-28 | Redpath Richard J. | Method, apparatus. and program to efficiently serialize objects |
US6842906B1 (en) | 1999-08-31 | 2005-01-11 | Accenture Llp | System and method for a refreshable proxy pool in a communication services patterns environment |
US6850953B1 (en) * | 1999-08-23 | 2005-02-01 | Sun Microsystems, Inc. | Creating multiple sets of data by spawning a secondary virtual machine |
US6850938B1 (en) | 2001-02-08 | 2005-02-01 | Cisco Technology, Inc. | Method and apparatus providing optimistic locking of shared computer resources |
US20050027697A1 (en) * | 2003-07-31 | 2005-02-03 | Tom Cheng | Generalized data handler |
US20050050092A1 (en) * | 2003-08-25 | 2005-03-03 | Oracle International Corporation | Direct loading of semistructured data |
US20050050058A1 (en) * | 2003-08-25 | 2005-03-03 | Oracle International Corporation | Direct loading of opaque types |
US20050060309A1 (en) * | 2003-09-15 | 2005-03-17 | Oliver Scheerer | Query objects |
US20050065966A1 (en) * | 2003-09-24 | 2005-03-24 | Salleh Diab | Table-oriented application development environment |
US20050066338A1 (en) * | 2003-09-18 | 2005-03-24 | Anthony Bloesch | Exstensibility application programming interface and framework for meta-model objects |
US6892234B2 (en) * | 2002-06-12 | 2005-05-10 | Electronic Data Systems Corporation | Multi-tiered enterprise management system and method including a presentation services unit external to the enterprise |
US20050120293A1 (en) * | 2003-12-01 | 2005-06-02 | International Business Machines Corporation | Table column spanning |
US20050171953A1 (en) * | 2004-01-30 | 2005-08-04 | International Business Machines Corporation | Method, system, and article of manufacture for generating device specific requests |
US20050171931A1 (en) * | 2002-04-03 | 2005-08-04 | Biowisdom Limited | Database searching method and system |
EP1565815A1 (en) * | 2002-07-17 | 2005-08-24 | Collation, Inc. | Service descriptor for a multitier compute infrastructure |
EP1565851A2 (en) * | 2002-07-17 | 2005-08-24 | Collation, Inc. | Business service for a multitier compute infrastructure |
US6944642B1 (en) * | 1999-10-04 | 2005-09-13 | Microsoft Corporation | Systems and methods for detecting and resolving resource conflicts |
US20050204340A1 (en) * | 2004-03-10 | 2005-09-15 | Ruminer Michael D. | Attribute-based automated business rule identifier and methods of implementing same |
US6950848B1 (en) * | 2000-05-05 | 2005-09-27 | Yousefi Zadeh Homayoun | Database load balancing for multi-tier computer systems |
US6954220B1 (en) | 1999-08-31 | 2005-10-11 | Accenture Llp | User context component in environment services patterns |
US6957228B1 (en) * | 2000-01-07 | 2005-10-18 | International Business Machines Corporation | Object oriented apparatus and method for providing context-based class replacement in an object oriented system |
US6971085B1 (en) * | 2000-08-31 | 2005-11-29 | International Business Machines Corporation | Object oriented structured query language (OOSQL) support for enterprise java beans |
US6970925B1 (en) * | 1999-02-03 | 2005-11-29 | William H. Gates, III | Method and system for property notification |
US20060010421A1 (en) * | 2000-02-01 | 2006-01-12 | Gurevich Michael N | Methods and apparatus for portable object-oriented components |
US20060026568A1 (en) * | 2001-07-05 | 2006-02-02 | Microsoft Corporation | System and methods for providing versioning of software components in a computer programming language |
US7003548B1 (en) * | 1999-03-29 | 2006-02-21 | Gelco Corporation | Method and apparatus for developing and checking technical configurations of a product |
US20060041861A1 (en) * | 2003-05-06 | 2006-02-23 | Pegasystems Inc. | Methods and apparatus for digital data processing with mutable inheritance |
US7016906B1 (en) * | 2000-05-04 | 2006-03-21 | Unisys Corporation | Data processing method and apparatus employing OLE DB and having dual schema and auto update features |
US7024656B1 (en) * | 1999-11-29 | 2006-04-04 | Oracle International Corporation | Persistent agents |
US7036124B1 (en) | 1998-06-10 | 2006-04-25 | Sun Microsystems, Inc. | Computer resource management for competing processes |
US7047522B1 (en) * | 2001-04-30 | 2006-05-16 | General Electric Capital Corporation | Method and system for verifying a computer program |
US20060107222A1 (en) * | 2004-09-10 | 2006-05-18 | Bea Systems, Inc. | Dynamic generation of wrapper classes to implement call-by-value semantics |
US20060117294A1 (en) * | 2002-08-29 | 2006-06-01 | Crossmarx B.V. | System and method for executing and building a software application |
US20060122975A1 (en) * | 2004-12-03 | 2006-06-08 | Taylor Paul S | System and method for query management in a database management system |
US20060122976A1 (en) * | 2004-12-03 | 2006-06-08 | Shumeet Baluja | Predictive information retrieval |
US20060143193A1 (en) * | 2004-12-29 | 2006-06-29 | Microsoft Corporation | Method and apparatus for metadata driven business logic processing |
US20060143148A1 (en) * | 2004-12-29 | 2006-06-29 | Microsoft Corporation | Method and apparatus for building metadata driven software development kit |
US7072907B2 (en) * | 2000-05-09 | 2006-07-04 | Fujitsu Limited | Information providing system and mediating apparatus |
US20060150083A1 (en) * | 2004-12-30 | 2006-07-06 | Microsoft Corporation | Methods and systems for preserving unknown markup in a strongly typed environment |
US20060174235A1 (en) * | 2003-02-18 | 2006-08-03 | Tomihisa Kamada | Native compile method, native compile preprocessing method, computer program, and server |
US20060184926A1 (en) * | 2002-07-17 | 2006-08-17 | Yan Or | Deployment of applications in a multitier compute infrastructure |
US7107272B1 (en) * | 2002-12-02 | 2006-09-12 | Storage Technology Corporation | Independent distributed metadata system and method |
US20060218174A1 (en) * | 2005-03-23 | 2006-09-28 | Cook John L Iii | Method for coordinating schema and data access objects |
US7120863B1 (en) * | 1999-11-15 | 2006-10-10 | International Business Machines Corporation | Method, system, and program for interfacing with elements in a document |
US7127677B2 (en) | 2001-01-23 | 2006-10-24 | Xerox Corporation | Customizable remote order entry system and method |
US20060253540A1 (en) * | 1999-06-10 | 2006-11-09 | Ec Enabler, Ltd. (A New York Corporation) | Method and system for transferring information |
US20060269148A1 (en) * | 2004-11-14 | 2006-11-30 | Emanuel Farber | Systems and methods for data coding, transmission, storage and decoding |
US20070016604A1 (en) * | 2005-07-18 | 2007-01-18 | Ravi Murthy | Document level indexes for efficient processing in multiple tiers of a computer system |
US20070016605A1 (en) * | 2005-07-18 | 2007-01-18 | Ravi Murthy | Mechanism for computing structural summaries of XML document collections in a database system |
US20070038666A1 (en) * | 2005-08-15 | 2007-02-15 | Microsoft Corporation | Independent explicit interface implementation |
US20070089117A1 (en) * | 2005-09-22 | 2007-04-19 | Xcalia | Implementation system for business applications |
US20070130195A1 (en) * | 2005-12-06 | 2007-06-07 | Xiang Li | Modeling enumeration tables for relational databases |
US20070143091A1 (en) * | 2001-11-30 | 2007-06-21 | Takashi Hiquchi | Microcomputer logic development system |
US7236981B1 (en) * | 2002-12-17 | 2007-06-26 | Oracle International Corporation | Technique for generating code to implement value objects for use with database systems |
US7240329B1 (en) | 2000-05-12 | 2007-07-03 | Oracle International Corporation | Policies on a per instance basis |
US20070226272A1 (en) * | 2001-09-28 | 2007-09-27 | Huang Xiao F | Method And System For Server Synchronization With A Computing Device |
US20070233902A1 (en) * | 2006-03-30 | 2007-10-04 | Alan Trefler | User interface methods and apparatus for rules processing |
US20070239646A1 (en) * | 2006-03-03 | 2007-10-11 | Alan Trefler | Rules base systems and methods with circumstance translation |
US7283991B1 (en) * | 1999-03-11 | 2007-10-16 | Microsoft Corporation | Caching system for path search optimization |
US20070288892A1 (en) * | 2006-03-24 | 2007-12-13 | The Mathworks, Inc. | System and method for providing and using meta-data in a dynamically typed array-based language |
US7318225B1 (en) * | 2001-09-21 | 2008-01-08 | Novatel Wireless, Inc. | Object oriented software architecture for software reconfigurable wireless modem |
US7337184B1 (en) | 2002-07-17 | 2008-02-26 | International Business Machines Corporation | Topology mapping of a multitier compute infrastructure |
US20080071838A1 (en) * | 2002-04-12 | 2008-03-20 | Yoshimi Moriya | Metadata editing apparatus, metadata reproduction apparatus, metadata delivery apparatus, metadata search apparatus, metadata re-generation condition setting apparatus, metadata delivery method and hint information description method |
US7350191B1 (en) * | 2003-04-22 | 2008-03-25 | Noetix, Inc. | Computer implemented system and method for the generation of data access applications |
US20080098346A1 (en) * | 2006-10-10 | 2008-04-24 | Rohan Angrish | Mapping Web Services Description Language documents to XQuery functions |
US7370270B2 (en) | 2002-10-23 | 2008-05-06 | Aol Llc A Delaware Limited Liability Company | XML schema evolution |
US20080147781A1 (en) * | 1999-10-04 | 2008-06-19 | Hopmann Alexander I | Method and system for supporting off-line mode of operation and synchronization |
US7406676B2 (en) | 2000-09-18 | 2008-07-29 | Microsoft Corporation | Access redirector and entry reflector |
US20080183724A1 (en) * | 2007-01-30 | 2008-07-31 | Bmc Software, Inc. | Configuration Management Database Reference Instance |
US20080189678A1 (en) * | 2007-02-02 | 2008-08-07 | Microsoft Corporation | N-tiered applications support via common interface |
US20080216055A1 (en) * | 2007-03-02 | 2008-09-04 | Pegasystems, Inc. | Proactive performance management for multi-user enterprise software systems |
US20080243857A1 (en) * | 2004-02-13 | 2008-10-02 | France Telecom | Method for Editing a Multimedia Page Using Pre-Stored Data |
WO2008141801A1 (en) * | 2007-05-21 | 2008-11-27 | Stefan Becker | A method for providing or operating a framework for the realization of independently developed programs |
US7461076B1 (en) * | 2000-07-25 | 2008-12-02 | Epiphany, Inc. | Method and apparatus for creating a well-formed database system using a computer |
US7490093B2 (en) | 2003-08-25 | 2009-02-10 | Oracle International Corporation | Generating a schema-specific load structure to load data into a relational database based on determining whether the schema-specific load structure already exists |
US20090077536A1 (en) * | 2007-07-12 | 2009-03-19 | The Mathworks, Inc. | Programming environment with support for handle and non-handle user-created classes |
US20090138894A1 (en) * | 2007-11-28 | 2009-05-28 | Red Hat, Inc. | Automatic Object Instantiation |
US20090187885A1 (en) * | 2008-01-23 | 2009-07-23 | Schneider James P | Calling functions as methods |
US7574461B1 (en) * | 2005-12-28 | 2009-08-11 | Emc Corporation | Dividing data for multi-thread backup |
US7665063B1 (en) * | 2004-05-26 | 2010-02-16 | Pegasystems, Inc. | Integration of declarative rule-based processing with procedural programming |
US20100057834A1 (en) * | 2008-08-29 | 2010-03-04 | Macken Luke J | Method and System for Facilitating Client Server Interaction |
US20100057937A1 (en) * | 2008-08-29 | 2010-03-04 | Macken Luke J | Method and System for Facilitating Client Server Interaction |
US20100083285A1 (en) * | 2008-09-26 | 2010-04-01 | Microsoft Corporation | Data-tier application component |
US7693889B1 (en) | 2005-12-28 | 2010-04-06 | Emc Corporation | Automated backup and recovery for content repository |
US7739224B1 (en) | 1998-05-06 | 2010-06-15 | Infor Global Solutions (Michigan), Inc. | Method and system for creating a well-formed database using semantic definitions |
US7930278B2 (en) | 1998-02-13 | 2011-04-19 | Oracle International Corporation | Methods to perform disk writes in a distributed shared disk system needing consistency across failures |
US20110106778A1 (en) * | 2009-11-05 | 2011-05-05 | Oracle International Corporation | Lock manager on disk |
US8001523B1 (en) | 2001-07-05 | 2011-08-16 | Microsoft Corporation | System and methods for implementing an explicit interface member in a computer programming language |
US20110231481A1 (en) * | 2010-03-16 | 2011-09-22 | Saleforce.com, inc. | System, method and computer program product for communicating data between a database and a cache |
US20110258224A1 (en) * | 2010-04-15 | 2011-10-20 | Dee Gee Holdings, Llc | Method and computer program product for creating content management systems |
US8108451B2 (en) | 2000-05-31 | 2012-01-31 | International Business Machines Corporation | System and program products for efficiently locking resources of a global data repository |
US20120144405A1 (en) * | 2010-12-06 | 2012-06-07 | Ibm Corporation | Efficient Serialization of Mutable Objects |
US8266384B1 (en) * | 2011-11-04 | 2012-09-11 | Recursion Software, Inc. | System and method for managing an object cache |
US8335704B2 (en) | 2005-01-28 | 2012-12-18 | Pegasystems Inc. | Methods and apparatus for work management and routing |
US20130117405A1 (en) * | 2011-11-04 | 2013-05-09 | Recursion Software, Inc. | System and method for managing an object cache |
US8473718B2 (en) | 2000-10-10 | 2013-06-25 | Nazomi Communications Inc. | Java hardware accelerator using microcode engine |
US20130297755A1 (en) * | 2010-11-23 | 2013-11-07 | Nokia Siemens Networks Oy | Network element configuration management |
US8769508B2 (en) | 2001-08-24 | 2014-07-01 | Nazomi Communications Inc. | Virtual machine hardware for RISC and CISC processors |
US8880487B1 (en) | 2011-02-18 | 2014-11-04 | Pegasystems Inc. | Systems and methods for distributed rules processing |
US20140331118A1 (en) * | 2013-05-06 | 2014-11-06 | Sap Ag | Persisting Objects in a Single Data Table |
US8924335B1 (en) | 2006-03-30 | 2014-12-30 | Pegasystems Inc. | Rule-based user interface conformance methods |
US20150019591A1 (en) * | 2004-05-21 | 2015-01-15 | Ronald Scott Visscher | Architectural Frameworks, Functions and Interfaces for Relationship Management (AFFIRM) |
US9015661B1 (en) * | 2011-06-23 | 2015-04-21 | The Mathworks, Inc. | Restricting class inheritance relationships |
US9195936B1 (en) | 2011-12-30 | 2015-11-24 | Pegasystems Inc. | System and method for updating or modifying an application without manual coding |
US20150347476A1 (en) * | 2014-05-30 | 2015-12-03 | Amadeus S.A.S. | Content management in a travel management system |
US9442941B1 (en) * | 2014-03-28 | 2016-09-13 | Emc Corporation | Data structure for hash digest metadata component |
US9678719B1 (en) | 2009-03-30 | 2017-06-13 | Pegasystems Inc. | System and software for creation and modification of software |
US9857990B1 (en) | 2016-03-24 | 2018-01-02 | EMC IP Holding Company LLC | Fast startup for modular storage systems |
US10049329B2 (en) | 2014-05-30 | 2018-08-14 | Amadeus S.A.S. | Content exchange with a travel management system |
US10101934B1 (en) | 2016-03-24 | 2018-10-16 | Emc Corporation | Memory allocation balancing for storage systems |
US10152371B1 (en) | 2016-09-30 | 2018-12-11 | EMC IP Holding Company LLC | End-to-end data protection for distributed storage |
US10152527B1 (en) | 2015-12-28 | 2018-12-11 | EMC IP Holding Company LLC | Increment resynchronization in hash-based replication |
US10223008B1 (en) | 2016-09-30 | 2019-03-05 | EMC IP Holding Company LLC | Storage array sizing for compressed applications |
US10255172B1 (en) | 2016-09-30 | 2019-04-09 | EMC IP Holding Company LLC | Controlled testing using code error injection |
US10324782B1 (en) | 2016-03-24 | 2019-06-18 | Emc Corporation | Hiccup management in a storage array |
US10339337B1 (en) * | 2017-01-12 | 2019-07-02 | Marklogic Corporation | Apparatus and method for supplying secure relational query results from a semi-structured document database |
US10467200B1 (en) | 2009-03-12 | 2019-11-05 | Pegasystems, Inc. | Techniques for dynamic data processing |
US10469396B2 (en) | 2014-10-10 | 2019-11-05 | Pegasystems, Inc. | Event processing with enhanced throughput |
US10671366B2 (en) * | 2015-12-22 | 2020-06-02 | Alibaba Group Holding Limited | App program running method and apparatus |
US10698647B2 (en) | 2016-07-11 | 2020-06-30 | Pegasystems Inc. | Selective sharing for collaborative application usage |
US10698599B2 (en) | 2016-06-03 | 2020-06-30 | Pegasystems, Inc. | Connecting graphical shapes using gestures |
US10705907B1 (en) | 2016-03-24 | 2020-07-07 | EMC IP Holding Company LLC | Data protection in a heterogeneous random access storage array |
US10789048B2 (en) * | 2019-01-30 | 2020-09-29 | Salesforce.Com, Inc. | Namespace and class utilities for managed packages |
CN112817580A (en) * | 2021-01-27 | 2021-05-18 | 北京奇艺世纪科技有限公司 | Data processing method and device, electronic equipment and storage medium |
US11048488B2 (en) | 2018-08-14 | 2021-06-29 | Pegasystems, Inc. | Software code optimizer and method |
US11567945B1 (en) | 2020-08-27 | 2023-01-31 | Pegasystems Inc. | Customized digital content generation systems and methods |
US20230042944A1 (en) * | 2010-05-14 | 2023-02-09 | Sap Se | Integrated Application Server and Data Server Processes with Matching Data Formats |
US11755744B2 (en) * | 2019-11-07 | 2023-09-12 | Oracle International Corporation | Application programming interface specification inference |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5925100A (en) * | 1996-03-21 | 1999-07-20 | Sybase, Inc. | Client/server system with methods for prefetching and managing semantic objects based on object-based prefetch primitive present in client's executing application |
US5950006A (en) * | 1997-11-05 | 1999-09-07 | Control Technology Corporation | Object-oriented programmable controller |
US5987497A (en) * | 1996-12-30 | 1999-11-16 | J.D. Edwards World Source Company | System and method for managing the configuration of distributed objects |
US5987514A (en) * | 1996-10-30 | 1999-11-16 | Sun Microsystems, Inc. | System and method for advanced event request management for networks |
US5995972A (en) * | 1996-12-30 | 1999-11-30 | J.D. Edwards World Source Company | System and method for retrieving data |
-
1998
- 1998-06-05 US US09/092,610 patent/US6085198A/en not_active Expired - Lifetime
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5925100A (en) * | 1996-03-21 | 1999-07-20 | Sybase, Inc. | Client/server system with methods for prefetching and managing semantic objects based on object-based prefetch primitive present in client's executing application |
US5987514A (en) * | 1996-10-30 | 1999-11-16 | Sun Microsystems, Inc. | System and method for advanced event request management for networks |
US5987497A (en) * | 1996-12-30 | 1999-11-16 | J.D. Edwards World Source Company | System and method for managing the configuration of distributed objects |
US5995972A (en) * | 1996-12-30 | 1999-11-30 | J.D. Edwards World Source Company | System and method for retrieving data |
US5950006A (en) * | 1997-11-05 | 1999-09-07 | Control Technology Corporation | Object-oriented programmable controller |
Cited By (390)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6578044B1 (en) * | 1997-11-17 | 2003-06-10 | Sun Microsystems, Inc. | Method and system for typesafe attribute matching |
US6564234B2 (en) | 1998-02-13 | 2003-05-13 | Oracle Corporation | Managing a resource used by a plurality of nodes |
US7930278B2 (en) | 1998-02-13 | 2011-04-19 | Oracle International Corporation | Methods to perform disk writes in a distributed shared disk system needing consistency across failures |
US6507853B2 (en) | 1998-02-13 | 2003-01-14 | Oracle Corporation | Recovering data from a failed cache using recovery logs of caches that updated the data |
US6411968B2 (en) | 1998-02-13 | 2002-06-25 | Oracle Corporation | Managing recovery of data after failure of one or more caches |
US6609136B2 (en) | 1998-02-13 | 2003-08-19 | Oracle Corporation | Recovering data from a failed cache using a surviving cache |
US6564230B2 (en) | 1998-02-13 | 2003-05-13 | Oracle Corporation | Transferring a resource between caches of different nodes |
US6567827B2 (en) | 1998-02-13 | 2003-05-20 | Oracle Corporation | Using a checkpoint to manage data that is shared by a plurality of nodes |
US6353836B1 (en) * | 1998-02-13 | 2002-03-05 | Oracle Corporation | Method and apparatus for transferring data from the cache of one node to the cache of another node |
US6532465B2 (en) * | 1998-03-12 | 2003-03-11 | Bruce Hartley | Operational system for operating on client defined rules |
US20010032207A1 (en) * | 1998-03-12 | 2001-10-18 | Bruce Hartley | Operational system for operating on client defined rules |
US6330709B1 (en) * | 1998-03-30 | 2001-12-11 | International Business Machines Corporation | Virtual machine implementation for shared persistent objects |
US7739224B1 (en) | 1998-05-06 | 2010-06-15 | Infor Global Solutions (Michigan), Inc. | Method and system for creating a well-formed database using semantic definitions |
US6278791B1 (en) * | 1998-05-07 | 2001-08-21 | Eastman Kodak Company | Lossless recovery of an original image containing embedded data |
US6598093B1 (en) * | 1998-05-14 | 2003-07-22 | Sun Microsystems, Inc. | Method and apparatus for a core application programming interface |
US6504913B1 (en) * | 1998-06-10 | 2003-01-07 | Sun Microsystems Inc | Call handling mechanism |
US6570972B2 (en) | 1998-06-10 | 2003-05-27 | Microsystems, Inc. | Telephony control mechanism |
US20030154233A1 (en) * | 1998-06-10 | 2003-08-14 | David John Martin Patterson | Scheduling processes for resource allocation |
US7036124B1 (en) | 1998-06-10 | 2006-04-25 | Sun Microsystems, Inc. | Computer resource management for competing processes |
US6714935B1 (en) * | 1998-09-21 | 2004-03-30 | Microsoft Corporation | Management of non-persistent data in a persistent database |
US6446077B2 (en) * | 1998-09-21 | 2002-09-03 | Microsoft Corporation | Inherited information propagator for objects |
US6742175B1 (en) * | 1998-10-13 | 2004-05-25 | Codagen Technologies Corp. | Component-based source code generator |
US6339841B1 (en) * | 1998-10-19 | 2002-01-15 | International Business Machines Corporation | Class loading model |
US6298353B1 (en) * | 1998-11-19 | 2001-10-02 | International Business Machines Corporation | Checking serialization compatibility between versions of java classes |
US7200623B2 (en) | 1998-11-24 | 2007-04-03 | Oracle International Corp. | Methods to perform disk writes in a distributed shared disk system needing consistency across failures |
US7065540B2 (en) | 1998-11-24 | 2006-06-20 | Oracle International Corporation | Managing checkpoint queues in a multiple node system |
US7296039B2 (en) | 1998-11-24 | 2007-11-13 | Oracle International Corporation | Managing checkpoint queues in a multiple node system |
US20050065907A1 (en) * | 1998-11-24 | 2005-03-24 | Oracle Corporation | Managing checkpoint queues in a multiple node system |
US20060195648A1 (en) * | 1998-11-24 | 2006-08-31 | Oracle International Corporation | Managing checkpoint queues in a multiple node system |
US7577690B2 (en) | 1998-11-24 | 2009-08-18 | Oracle International Corporation | Managing checkpoint queues in a multiple node system |
US20020095403A1 (en) * | 1998-11-24 | 2002-07-18 | Sashikanth Chandrasekaran | Methods to perform disk writes in a distributed shared disk system needing consistency across failures |
US20020099729A1 (en) * | 1998-11-24 | 2002-07-25 | Oracle Corporation | Managing checkpoint queues in a multiple node system |
US7080362B2 (en) | 1998-12-08 | 2006-07-18 | Nazomi Communication, Inc. | Java virtual machine hardware for RISC and CISC processors |
US6338160B1 (en) * | 1998-12-08 | 2002-01-08 | Nazomi Communications, Inc. | Constant pool reference resolution method |
US20020066083A1 (en) * | 1998-12-08 | 2002-05-30 | Patel Mukesh K. | Java virtual machine hardware for RISC and CISC processors |
US8185882B2 (en) | 1998-12-08 | 2012-05-22 | Nazomi Communications Inc. | Java virtual machine hardware for RISC and CISC processors |
US6236909B1 (en) * | 1998-12-28 | 2001-05-22 | International Business Machines Corporation | Method for representing automotive device functionality and software services to applications using JavaBeans |
US6970925B1 (en) * | 1999-02-03 | 2005-11-29 | William H. Gates, III | Method and system for property notification |
US6314430B1 (en) * | 1999-02-23 | 2001-11-06 | International Business Machines Corporation | System and method for accessing a database from a task written in an object-oriented programming language |
US7283991B1 (en) * | 1999-03-11 | 2007-10-16 | Microsoft Corporation | Caching system for path search optimization |
US6363394B1 (en) * | 1999-03-18 | 2002-03-26 | Microsoft Corporation | Auto-generation of table neighborhoods |
US20060167988A1 (en) * | 1999-03-29 | 2006-07-27 | David Barck | Method and sytem for developing technical configurations |
US7003548B1 (en) * | 1999-03-29 | 2006-02-21 | Gelco Corporation | Method and apparatus for developing and checking technical configurations of a product |
US6427228B1 (en) * | 1999-05-12 | 2002-07-30 | International Business Machines Corporation | Combining a meta data file and java source code to dynamically create java classes and javabeans |
US8484379B2 (en) * | 1999-06-10 | 2013-07-09 | E C Enabler, Ltd | Method and system for transferring information |
US20060253540A1 (en) * | 1999-06-10 | 2006-11-09 | Ec Enabler, Ltd. (A New York Corporation) | Method and system for transferring information |
US6637021B1 (en) * | 1999-06-30 | 2003-10-21 | Sun Microsystems, Inc. | JavaBean activation framework-common desktop environment bridge |
US6792576B1 (en) * | 1999-07-26 | 2004-09-14 | Xerox Corporation | System and method of automatic wrapper grammar generation |
US6850953B1 (en) * | 1999-08-23 | 2005-02-01 | Sun Microsystems, Inc. | Creating multiple sets of data by spawning a secondary virtual machine |
US6842906B1 (en) | 1999-08-31 | 2005-01-11 | Accenture Llp | System and method for a refreshable proxy pool in a communication services patterns environment |
US6640249B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Presentation services patterns in a netcentric environment |
US6742015B1 (en) | 1999-08-31 | 2004-05-25 | Accenture Llp | Base services patterns in a netcentric environment |
US6578068B1 (en) | 1999-08-31 | 2003-06-10 | Accenture Llp | Load balancer in environment services patterns |
US6434628B1 (en) * | 1999-08-31 | 2002-08-13 | Accenture Llp | Common interface for handling exception interface name with additional prefix and suffix for handling exceptions in environment services patterns |
US6640238B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Activity component in a presentation services patterns environment |
US6571282B1 (en) | 1999-08-31 | 2003-05-27 | Accenture Llp | Block-based communication in a communication services patterns environment |
US6601234B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Attribute dictionary in a business logic services environment |
US6601192B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Assertion component in environment services patterns |
US6549949B1 (en) | 1999-08-31 | 2003-04-15 | Accenture Llp | Fixed format stream in a communication services patterns environment |
US6477580B1 (en) * | 1999-08-31 | 2002-11-05 | Accenture Llp | Self-described stream in a communication services patterns environment |
US6615253B1 (en) | 1999-08-31 | 2003-09-02 | Accenture Llp | Efficient server side data retrieval for execution of client side applications |
US6640244B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Request batcher in a transaction services patterns environment |
US6954220B1 (en) | 1999-08-31 | 2005-10-11 | Accenture Llp | User context component in environment services patterns |
US6715145B1 (en) | 1999-08-31 | 2004-03-30 | Accenture Llp | Processing pipeline in a base services pattern environment |
US6636242B2 (en) | 1999-08-31 | 2003-10-21 | Accenture Llp | View configurer in a presentation services patterns environment |
US6757670B1 (en) * | 1999-09-13 | 2004-06-29 | Hitachi, Ltd. | Method and system for query processing |
US6507833B1 (en) * | 1999-09-13 | 2003-01-14 | Oracle Corporation | Method and apparatus for dynamically rendering components at run time |
US6477701B1 (en) * | 1999-09-30 | 2002-11-05 | Seiko Epson Corporation | Version-adaptive serialization and deserialization of program objects in an object-oriented environment |
US8972348B2 (en) | 1999-10-04 | 2015-03-03 | Microsoft Corporation | Method and system for supporting off-line mode of operation and synchronization |
US7865469B2 (en) | 1999-10-04 | 2011-01-04 | Microsoft Corporation | Method and system for supporting off-line mode of operation and synchronization |
US6944642B1 (en) * | 1999-10-04 | 2005-09-13 | Microsoft Corporation | Systems and methods for detecting and resolving resource conflicts |
US20110093597A1 (en) * | 1999-10-04 | 2011-04-21 | Microsoft Corporation | Method and System for Supporting Off-Line Mode of Operation and Synchronization |
US20080147781A1 (en) * | 1999-10-04 | 2008-06-19 | Hopmann Alexander I | Method and system for supporting off-line mode of operation and synchronization |
US7120863B1 (en) * | 1999-11-15 | 2006-10-10 | International Business Machines Corporation | Method, system, and program for interfacing with elements in a document |
US7024656B1 (en) * | 1999-11-29 | 2006-04-04 | Oracle International Corporation | Persistent agents |
US6754670B1 (en) * | 1999-12-17 | 2004-06-22 | International Business Machines Corporation | Mapping relational tables to object oriented classes |
US6957228B1 (en) * | 2000-01-07 | 2005-10-18 | International Business Machines Corporation | Object oriented apparatus and method for providing context-based class replacement in an object oriented system |
US6434555B1 (en) * | 2000-01-24 | 2002-08-13 | Hewlett Packard Company | Method for transaction recovery in three-tier applications |
US20060010421A1 (en) * | 2000-02-01 | 2006-01-12 | Gurevich Michael N | Methods and apparatus for portable object-oriented components |
US6757708B1 (en) * | 2000-03-03 | 2004-06-29 | International Business Machines Corporation | Caching dynamic content |
US6697797B1 (en) * | 2000-04-28 | 2004-02-24 | Micro Data Base Systems, Inc. | Method and apparatus for tracking data in a database, employing last-known location registers |
US7016906B1 (en) * | 2000-05-04 | 2006-03-21 | Unisys Corporation | Data processing method and apparatus employing OLE DB and having dual schema and auto update features |
US6950848B1 (en) * | 2000-05-05 | 2005-09-27 | Yousefi Zadeh Homayoun | Database load balancing for multi-tier computer systems |
US7072907B2 (en) * | 2000-05-09 | 2006-07-04 | Fujitsu Limited | Information providing system and mediating apparatus |
US7240329B1 (en) | 2000-05-12 | 2007-07-03 | Oracle International Corporation | Policies on a per instance basis |
US6327628B1 (en) * | 2000-05-19 | 2001-12-04 | Epicentric, Inc. | Portal server that provides a customizable user Interface for access to computer networks |
US6591274B1 (en) * | 2000-05-31 | 2003-07-08 | Sprint Communications Company, L.P. | Computer software framework and method for accessing data from one or more datastores for use by one or more computing applications |
US8108451B2 (en) | 2000-05-31 | 2012-01-31 | International Business Machines Corporation | System and program products for efficiently locking resources of a global data repository |
US6681225B1 (en) * | 2000-05-31 | 2004-01-20 | International Business Machines Corporation | Method, system and program products for concurrent write access to a global data repository |
US6442552B1 (en) * | 2000-06-30 | 2002-08-27 | Hewlett-Packard Company | Method and apparatus for implementing three tier client asynchronous transparency |
US6591276B1 (en) * | 2000-07-21 | 2003-07-08 | International Business Machines Corporation | Method and system for managing object types for objects defined externally to the system |
US7461076B1 (en) * | 2000-07-25 | 2008-12-02 | Epiphany, Inc. | Method and apparatus for creating a well-formed database system using a computer |
US7027975B1 (en) | 2000-08-08 | 2006-04-11 | Object Services And Consulting, Inc. | Guided natural language interface system and method |
WO2002012982A2 (en) * | 2000-08-08 | 2002-02-14 | Object Services And Consulting, Inc. | Guided natural language interface system and method |
WO2002012982A3 (en) * | 2000-08-08 | 2002-05-16 | Object Services And Consulting | Guided natural language interface system and method |
US6574631B1 (en) * | 2000-08-09 | 2003-06-03 | Oracle International Corporation | Methods and systems for runtime optimization and customization of database applications and application entities |
US6971085B1 (en) * | 2000-08-31 | 2005-11-29 | International Business Machines Corporation | Object oriented structured query language (OOSQL) support for enterprise java beans |
US7631293B2 (en) | 2000-08-31 | 2009-12-08 | International Business Machines Corporation | Object oriented structured query language (OOSQL) support for Enterprise Java Beans |
US20060004774A1 (en) * | 2000-08-31 | 2006-01-05 | Alcorn John W | Object oriented structured query language (OOSQL) support for enterprise Java beans |
US20040193651A1 (en) * | 2000-09-13 | 2004-09-30 | American Management System, Inc. | System and method for efficient integration of government administrative and program systems |
US7406676B2 (en) | 2000-09-18 | 2008-07-29 | Microsoft Corporation | Access redirector and entry reflector |
WO2002029609A1 (en) * | 2000-10-05 | 2002-04-11 | Arzoon, Inc. | Software isolation of presentation and mark-up language using intermediate function language and library |
US8473718B2 (en) | 2000-10-10 | 2013-06-25 | Nazomi Communications Inc. | Java hardware accelerator using microcode engine |
US20020103810A1 (en) * | 2000-10-19 | 2002-08-01 | Kobi Menachemi | Dynamic building of applications |
US20030105732A1 (en) * | 2000-11-17 | 2003-06-05 | Kagalwala Raxit A. | Database schema for structure query language (SQL) server |
US6990499B2 (en) | 2000-11-17 | 2006-01-24 | Microsoft Corporation | Mapping database users to operating system users in a computer schema |
US6810400B2 (en) | 2000-11-17 | 2004-10-26 | Microsoft Corporation | Representing database permissions as associations in computer schema |
US7020655B2 (en) | 2000-11-17 | 2006-03-28 | Microsoft Corporation | Representing database permissions as associations in computer schema |
US6816869B2 (en) * | 2000-11-17 | 2004-11-09 | Microsoft Corporation | Mapping database users to operating system users in a computer schema |
US20020156790A1 (en) * | 2000-11-17 | 2002-10-24 | Kagalwala Raxit A. | Mapping database file class to operating system file class in a computer schema |
US20050050081A1 (en) * | 2000-11-17 | 2005-03-03 | Microsoft Corporation | Mapping database users to operating system users in a computer schema |
US7653652B2 (en) | 2000-11-17 | 2010-01-26 | Microsoft Corporation | Database schema for structured query language (SQL) server |
US6961730B2 (en) | 2000-11-17 | 2005-11-01 | Microsoft Corporation | Mapping database file class to operating system file class in a computer schema |
US20050076044A1 (en) * | 2000-11-17 | 2005-04-07 | Microsoft Corporation | Representing database permissions as associations in computer schema |
US20030004963A1 (en) * | 2000-11-17 | 2003-01-02 | Kagalwala Raxit A. | Mapping database users to operating system users in a computer schema |
US7269656B2 (en) | 2000-12-28 | 2007-09-11 | Xerox Corporation | Remote order entry system and method |
US20020087663A1 (en) * | 2000-12-28 | 2002-07-04 | Xerox Corporation | Remote order entry system and method |
US7127677B2 (en) | 2001-01-23 | 2006-10-24 | Xerox Corporation | Customizable remote order entry system and method |
US20050138375A1 (en) * | 2001-02-08 | 2005-06-23 | Shahrokh Sadjadi | Method and apparatus providing optimistic locking of shared computer resources |
US6850938B1 (en) | 2001-02-08 | 2005-02-01 | Cisco Technology, Inc. | Method and apparatus providing optimistic locking of shared computer resources |
US8745707B2 (en) | 2001-02-08 | 2014-06-03 | Cisco Technology, Inc. | Method and apparatus providing optimistic locking of shared computer resources |
US7072061B2 (en) | 2001-02-13 | 2006-07-04 | Ariba, Inc. | Method and system for extracting information from RFQ documents and compressing RFQ files into a common RFQ file type |
US7277878B2 (en) * | 2001-02-13 | 2007-10-02 | Ariba, Inc. | Variable length file header apparatus and system |
US7870115B2 (en) * | 2001-02-13 | 2011-01-11 | Ariba, Inc. | Variable length file header apparatus and system |
US20030061316A1 (en) * | 2001-02-13 | 2003-03-27 | Freemarkets | Variable length file header apparatus and system |
US7084998B2 (en) | 2001-02-13 | 2006-08-01 | Ariba, Inc. | Method and system for processing files using a printer driver |
US20080059612A1 (en) * | 2001-02-13 | 2008-03-06 | Ariba, Inc. | Variable length file header apparatus and system |
US20020120792A1 (en) * | 2001-02-13 | 2002-08-29 | Free Markets, Inc. | Method and system for processing files using a printer driver |
US20020112114A1 (en) * | 2001-02-13 | 2002-08-15 | Blair William R. | Method and system for extracting information from RFQ documents and compressing RFQ files into a common RFQ file type |
US20110173169A1 (en) * | 2001-03-07 | 2011-07-14 | Oracle International Corporation | Methods To Perform Disk Writes In A Distributed Shared Disk System Needing Consistency Across Failures |
US20030028503A1 (en) * | 2001-04-13 | 2003-02-06 | Giovanni Giuffrida | Method and apparatus for automatically extracting metadata from electronic documents using spatial rules |
US7653914B2 (en) * | 2001-04-23 | 2010-01-26 | Nokia Corporation | Handling different service versions in a server |
US20030167349A1 (en) * | 2001-04-23 | 2003-09-04 | Petri Krohn | Handling different service versions in a server |
US7047522B1 (en) * | 2001-04-30 | 2006-05-16 | General Electric Capital Corporation | Method and system for verifying a computer program |
GB2378547B (en) * | 2001-06-01 | 2005-06-29 | Hewlett Packard Co | Runtime configurable caching for component factories |
GB2378547A (en) * | 2001-06-01 | 2003-02-12 | Hewlett Packard Co | Runtime configurable caching for component object factories |
US20020184612A1 (en) * | 2001-06-01 | 2002-12-05 | Hunt Joseph R. | Runtime configurable caching for component factories |
US6687702B2 (en) * | 2001-06-15 | 2004-02-03 | Sybass, Inc. | Methodology providing high-speed shared memory access between database middle tier and database server |
US20060026568A1 (en) * | 2001-07-05 | 2006-02-02 | Microsoft Corporation | System and methods for providing versioning of software components in a computer programming language |
US7873958B2 (en) | 2001-07-05 | 2011-01-18 | Microsoft Corporation | System and methods for providing versioning of software components in a computer programming language |
US8001523B1 (en) | 2001-07-05 | 2011-08-16 | Microsoft Corporation | System and methods for implementing an explicit interface member in a computer programming language |
US6778990B2 (en) | 2001-07-27 | 2004-08-17 | Hewlett-Packard Development Company, L.P. | Dynamic component activation method using a relational database as the repository for registration information |
US6801919B2 (en) | 2001-07-27 | 2004-10-05 | Hewlett-Packard Development Company, L.P. | Object oriented database interface encapsulation that allows for chronologically overlapping transactions in a multi-threaded environment |
US20030028682A1 (en) * | 2001-08-01 | 2003-02-06 | Sutherland James Bryce | System and method for object persistence life-cycle and object caching integration |
US7003776B2 (en) * | 2001-08-01 | 2006-02-21 | Oic Acquisition I Corporation | System and method for object persistence life-cycle and object caching integration |
US8769508B2 (en) | 2001-08-24 | 2014-07-01 | Nazomi Communications Inc. | Virtual machine hardware for RISC and CISC processors |
US7318225B1 (en) * | 2001-09-21 | 2008-01-08 | Novatel Wireless, Inc. | Object oriented software architecture for software reconfigurable wireless modem |
US20030061352A1 (en) * | 2001-09-27 | 2003-03-27 | International Business Machines Corporation | Optimized file cache organization in a network server |
US20070226272A1 (en) * | 2001-09-28 | 2007-09-27 | Huang Xiao F | Method And System For Server Synchronization With A Computing Device |
US8533154B2 (en) * | 2001-09-28 | 2013-09-10 | Siebel Systems, Inc. | Method and system for server synchronization with a computing device |
WO2003030020A2 (en) * | 2001-10-02 | 2003-04-10 | Treewise Aps | Handling relational metanodes in databases |
WO2003030020A3 (en) * | 2001-10-02 | 2004-03-04 | Treewise Aps | Handling relational metanodes in databases |
US20030069758A1 (en) * | 2001-10-10 | 2003-04-10 | Anderson Laura M. | System and method for use in providing a healthcare information database |
EP1442398A1 (en) * | 2001-10-25 | 2004-08-04 | Bea Systems, Inc. | System and method for flushing bean cache |
EP1442398A4 (en) * | 2001-10-25 | 2008-01-16 | Bea Systems Inc | System and method for flushing bean cache |
US7650274B2 (en) | 2001-11-30 | 2010-01-19 | Fujitsu Ten Limited | Microcomputer logic development system |
US20070143091A1 (en) * | 2001-11-30 | 2007-06-21 | Takashi Hiquchi | Microcomputer logic development system |
US6931409B2 (en) | 2002-01-08 | 2005-08-16 | International Business Machines Corporation | Method, apparatus, and program to efficiently serialize objects |
US7171419B2 (en) | 2002-01-08 | 2007-01-30 | International Business Machines Corporation | Method, apparatus, and program to efficiently serialize objects |
US20040215645A1 (en) * | 2002-01-08 | 2004-10-28 | Redpath Richard J. | Method, apparatus. and program to efficiently serialize objects |
US7130872B2 (en) * | 2002-01-18 | 2006-10-31 | Mobitv, Inc. | Multi-tiered caching mechanism for the storage and retrieval of content multiple versions |
US20030167257A1 (en) * | 2002-01-18 | 2003-09-04 | De Bonet Jeremy S. | Multi-tiered caching mechanism for the storage and retrieval of content multiple versions |
US20060253461A1 (en) * | 2002-01-18 | 2006-11-09 | De Bonet Jeremy S | Multi-tiered caching mechanism for the storage and retrieval of content multiple versions |
US7447675B2 (en) * | 2002-02-21 | 2008-11-04 | Bea Systems, Inc. | Systems and methods for cursored collections |
US20040002965A1 (en) * | 2002-02-21 | 2004-01-01 | Matthew Shinn | Systems and methods for cursored collections |
US7363612B2 (en) * | 2002-03-06 | 2008-04-22 | Sun Microsystems, Inc. | Application programs with dynamic components |
US20030172370A1 (en) * | 2002-03-06 | 2003-09-11 | Sridhar Satuloori | Application programs with dynamic components |
US20040083234A1 (en) * | 2002-03-25 | 2004-04-29 | Takashi Higuchi | System, program and method for producing computer application |
US20050171931A1 (en) * | 2002-04-03 | 2005-08-04 | Biowisdom Limited | Database searching method and system |
US20080071838A1 (en) * | 2002-04-12 | 2008-03-20 | Yoshimi Moriya | Metadata editing apparatus, metadata reproduction apparatus, metadata delivery apparatus, metadata search apparatus, metadata re-generation condition setting apparatus, metadata delivery method and hint information description method |
US8811800B2 (en) * | 2002-04-12 | 2014-08-19 | Mitsubishi Electric Corporation | Metadata editing apparatus, metadata reproduction apparatus, metadata delivery apparatus, metadata search apparatus, metadata re-generation condition setting apparatus, metadata delivery method and hint information description method |
US20030229849A1 (en) * | 2002-06-06 | 2003-12-11 | David Wendt | Web content management software utilizing a workspace aware JSP servlet |
US6993713B2 (en) * | 2002-06-06 | 2006-01-31 | International Business Machines Corporation | Web content management software utilizing a workspace aware JSP servlet |
US6892234B2 (en) * | 2002-06-12 | 2005-05-10 | Electronic Data Systems Corporation | Multi-tiered enterprise management system and method including a presentation services unit external to the enterprise |
US20030233632A1 (en) * | 2002-06-12 | 2003-12-18 | Lockheed Martin Corporation | Automatically generated client application source code using database table definitions |
US7058651B2 (en) | 2002-06-14 | 2006-06-06 | International Business Machines Corporation | Method, computer program product, and system for automatic class generation with simultaneous customization and interchange capability |
US20030233373A1 (en) * | 2002-06-14 | 2003-12-18 | International Business Machines Corporation | Method, computer program product, and system for automatic class generation with simultaneous customization and interchange capability |
US20040006565A1 (en) * | 2002-07-08 | 2004-01-08 | International Business Machines Corporation | Method, apparatus and computer program product for mapping file handles |
US6980994B2 (en) * | 2002-07-08 | 2005-12-27 | International Business Machines Corporation | Method, apparatus and computer program product for mapping file handles |
EP1565811A4 (en) * | 2002-07-17 | 2007-09-05 | Collation Inc | Topology mapping of a multitier compute infrastructure |
EP1565815A1 (en) * | 2002-07-17 | 2005-08-24 | Collation, Inc. | Service descriptor for a multitier compute infrastructure |
EP1565851A2 (en) * | 2002-07-17 | 2005-08-24 | Collation, Inc. | Business service for a multitier compute infrastructure |
US20080082978A1 (en) * | 2002-07-17 | 2008-04-03 | International Business Machines Corporation | Topology mapping of a mulitier compute infrastructure |
EP1565811A1 (en) * | 2002-07-17 | 2005-08-24 | Collation, Inc. | Topology mapping of a multitier compute infrastructure |
US20060184926A1 (en) * | 2002-07-17 | 2006-08-17 | Yan Or | Deployment of applications in a multitier compute infrastructure |
EP1565851A4 (en) * | 2002-07-17 | 2007-09-05 | Collation Inc | Business service for a multitier compute infrastructure |
EP1565815A4 (en) * | 2002-07-17 | 2007-09-05 | Collation Inc | Service descriptor for a multitier compute infrastructure |
US7243306B1 (en) | 2002-07-17 | 2007-07-10 | International Business Machines Corporation | Service descriptor for a multitier compute infrastructure |
US7337184B1 (en) | 2002-07-17 | 2008-02-26 | International Business Machines Corporation | Topology mapping of a multitier compute infrastructure |
US7912873B2 (en) | 2002-07-17 | 2011-03-22 | International Business Machines Corporation | Topology mapping of a mulitier compute infrastructure |
US7210143B2 (en) | 2002-07-17 | 2007-04-24 | International Business Machines Corporation | Deployment of applications in a multitier compute infrastructure |
WO2004010298A1 (en) * | 2002-07-17 | 2004-01-29 | Collation, Inc. | Topology mapping of a multitier compute infrastructure |
US7962590B1 (en) | 2002-07-17 | 2011-06-14 | International Business Machines Corporation | Automated discovery of a multitier compute infrastructure |
US7035841B2 (en) * | 2002-07-18 | 2006-04-25 | Xerox Corporation | Method for automatic wrapper repair |
US7440951B2 (en) * | 2002-07-18 | 2008-10-21 | Xerox Corporation | Method for automatic wrapper repair |
US20060074998A1 (en) * | 2002-07-18 | 2006-04-06 | Xerox Corporation | Method for automatic wrapper repair |
US20060074999A1 (en) * | 2002-07-18 | 2006-04-06 | Xerox Corporation | Method for automatic wrapper repair |
US20060085468A1 (en) * | 2002-07-18 | 2006-04-20 | Xerox Corporation | Method for automatic wrapper repair |
US7139777B2 (en) * | 2002-07-18 | 2006-11-21 | Xerox Corporation | Method for automatic wrapper repair |
US7440974B2 (en) * | 2002-07-18 | 2008-10-21 | Xerox Corporation | Method for automatic wrapper repair |
US20040015784A1 (en) * | 2002-07-18 | 2004-01-22 | Xerox Corporation | Method for automatic wrapper repair |
US6980995B2 (en) | 2002-07-23 | 2005-12-27 | International Business Machines Corporation | Method, computer program product, and system for automatically generating a hierarchial database schema report to facilitate writing application code for accessing hierarchial databases |
US20040019600A1 (en) * | 2002-07-23 | 2004-01-29 | International Business Machines Corporation | Method, computer program product, and system for automatically generating a hierarchical database schema report to facilitate writing application code for accessing hierarchical databases |
US20040153469A1 (en) * | 2002-07-24 | 2004-08-05 | Keith-Hill Roderic M. | Database comparator |
US20060117294A1 (en) * | 2002-08-29 | 2006-06-01 | Crossmarx B.V. | System and method for executing and building a software application |
US20040049544A1 (en) * | 2002-09-05 | 2004-03-11 | Hitachi, Ltd. | In-context launch management method, system therefor, and computer-readable storage medium |
US7165251B2 (en) | 2002-09-05 | 2007-01-16 | Hitachi, Ltd. | In-context launch management method, system therefor, and computer-readable storage medium |
US20040055002A1 (en) * | 2002-09-17 | 2004-03-18 | International Business Machines Corporation | Application connector parallelism in enterprise application integration systems |
US20080052726A1 (en) * | 2002-09-17 | 2008-02-28 | International Business Machines Corporation | Application connector parallelism in enterprise application integration systems |
US7900210B2 (en) | 2002-09-17 | 2011-03-01 | International Business Machines Corporation | Application connector parallelism in enterprise application integration systems |
US8010972B2 (en) | 2002-09-17 | 2011-08-30 | International Business Machines Corporation | Application connector parallelism in enterprise application integration systems |
US7386857B2 (en) | 2002-09-17 | 2008-06-10 | International Business Machines Corporation | Application connector parallelism in enterprise application integration systems |
US7370270B2 (en) | 2002-10-23 | 2008-05-06 | Aol Llc A Delaware Limited Liability Company | XML schema evolution |
WO2004046962A2 (en) * | 2002-11-18 | 2004-06-03 | Active Limited | Database management |
WO2004046962A3 (en) * | 2002-11-18 | 2004-12-02 | Active Ltd | Database management |
US7107272B1 (en) * | 2002-12-02 | 2006-09-12 | Storage Technology Corporation | Independent distributed metadata system and method |
US7236981B1 (en) * | 2002-12-17 | 2007-06-26 | Oracle International Corporation | Technique for generating code to implement value objects for use with database systems |
US20060174235A1 (en) * | 2003-02-18 | 2006-08-03 | Tomihisa Kamada | Native compile method, native compile preprocessing method, computer program, and server |
US7386609B2 (en) | 2003-02-20 | 2008-06-10 | International Business Machines Corporation | Method, system, and program for managing devices in a network |
US20040167975A1 (en) * | 2003-02-20 | 2004-08-26 | International Business Machines Corporation | Method, system, and program for managing devices in a network |
US7849179B2 (en) | 2003-02-20 | 2010-12-07 | International Business Machines Corporation | System and program for managing devices in a network |
US20080228909A1 (en) * | 2003-02-20 | 2008-09-18 | International Business Machines Corporation | System and program for managing devices in a network |
US20040172639A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Method for dynamically generating a wrapper |
US20040172613A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Dynamic code generation system |
WO2004079512A3 (en) * | 2003-02-28 | 2005-06-02 | Bea Systems Inc | Dynamic code generation |
US7536675B2 (en) * | 2003-02-28 | 2009-05-19 | Bea Systems, Inc. | Dynamic code generation system |
US7472400B2 (en) | 2003-02-28 | 2008-12-30 | Bea Systems, Inc. | Method for dynamically generating a wrapper class |
US7472401B2 (en) | 2003-02-28 | 2008-12-30 | Bea Systems, Inc. | Computer product for a dynamically generated wrapper class |
WO2004079512A2 (en) * | 2003-02-28 | 2004-09-16 | Bea Systems Inc. | Dynamic code generation |
US20040172614A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Dynamic code generation method |
US20040172640A1 (en) * | 2003-02-28 | 2004-09-02 | Bea Systems, Inc. | Dynamically generated wrapper |
US7730446B2 (en) | 2003-03-12 | 2010-06-01 | Microsoft Corporation | Software business process model |
US7577934B2 (en) * | 2003-03-12 | 2009-08-18 | Microsoft Corporation | Framework for modeling and providing runtime behavior for business software applications |
US20040181775A1 (en) * | 2003-03-12 | 2004-09-16 | Microsoft Corporation | Software business process model |
US20040181771A1 (en) * | 2003-03-12 | 2004-09-16 | Microsoft Corporation | Framework for supporting business software applications |
US8255871B1 (en) * | 2003-04-22 | 2012-08-28 | Noetix Corporation | Computer implemented system and method for the generation of data access applications |
US7350191B1 (en) * | 2003-04-22 | 2008-03-25 | Noetix, Inc. | Computer implemented system and method for the generation of data access applications |
US7711919B2 (en) | 2003-05-06 | 2010-05-04 | Pegasystems Inc. | Methods and apparatus for digital data processing with mutable inheritance |
US20060041861A1 (en) * | 2003-05-06 | 2006-02-23 | Pegasystems Inc. | Methods and apparatus for digital data processing with mutable inheritance |
US20050027697A1 (en) * | 2003-07-31 | 2005-02-03 | Tom Cheng | Generalized data handler |
US7814047B2 (en) * | 2003-08-25 | 2010-10-12 | Oracle International Corporation | Direct loading of semistructured data |
US7747580B2 (en) * | 2003-08-25 | 2010-06-29 | Oracle International Corporation | Direct loading of opaque types |
US20050050058A1 (en) * | 2003-08-25 | 2005-03-03 | Oracle International Corporation | Direct loading of opaque types |
US20050050092A1 (en) * | 2003-08-25 | 2005-03-03 | Oracle International Corporation | Direct loading of semistructured data |
US7490093B2 (en) | 2003-08-25 | 2009-02-10 | Oracle International Corporation | Generating a schema-specific load structure to load data into a relational database based on determining whether the schema-specific load structure already exists |
WO2005026986A3 (en) * | 2003-09-15 | 2006-03-09 | Sap Ag | Query objects |
US20050060309A1 (en) * | 2003-09-15 | 2005-03-17 | Oliver Scheerer | Query objects |
US7979842B2 (en) | 2003-09-18 | 2011-07-12 | Microsoft Corporation | Extensibility application programming interface and framework for meta-model objects |
US20080163160A1 (en) * | 2003-09-18 | 2008-07-03 | Microsoft Corporation | Extensibility application programming interface and framework for meta-model objects |
US7293254B2 (en) * | 2003-09-18 | 2007-11-06 | Microsoft Corporation | Extensibility application programming interface and framework for meta-model objects |
US20050066338A1 (en) * | 2003-09-18 | 2005-03-24 | Anthony Bloesch | Exstensibility application programming interface and framework for meta-model objects |
US20050066306A1 (en) * | 2003-09-24 | 2005-03-24 | Salleh Diab | Direct deployment of a software application from code written in tables |
US7130863B2 (en) | 2003-09-24 | 2006-10-31 | Tablecode Software Corporation | Method for enhancing object-oriented programming through extending metadata associated with class-body class-head by adding additional metadata to the database |
US20050065942A1 (en) * | 2003-09-24 | 2005-03-24 | Salleh Diab | Enhancing object-oriented programming through tables |
US20050065966A1 (en) * | 2003-09-24 | 2005-03-24 | Salleh Diab | Table-oriented application development environment |
US7266565B2 (en) * | 2003-09-24 | 2007-09-04 | Tablecode Software Corporation | Table-oriented application development environment |
US7318216B2 (en) * | 2003-09-24 | 2008-01-08 | Tablecode Software Corporation | Software application development environment facilitating development of a software application |
US20050120293A1 (en) * | 2003-12-01 | 2005-06-02 | International Business Machines Corporation | Table column spanning |
US8938667B2 (en) | 2003-12-01 | 2015-01-20 | International Business Machines Corporation | Table column spanning |
US20080005658A1 (en) * | 2003-12-01 | 2008-01-03 | International Business Machines Corporation | Table column spanning |
US8214732B2 (en) | 2003-12-01 | 2012-07-03 | International Business Machines Corporation | Table column spanning |
US7328400B2 (en) | 2003-12-01 | 2008-02-05 | International Business Machines Corporation | Table column spanning |
US9645991B2 (en) | 2003-12-01 | 2017-05-09 | International Business Machines Corporation | Table column spanning |
US7587421B2 (en) | 2004-01-30 | 2009-09-08 | International Business Machines Corporation | Method, system, and article of manufacture for generating device specific requests |
US20050171953A1 (en) * | 2004-01-30 | 2005-08-04 | International Business Machines Corporation | Method, system, and article of manufacture for generating device specific requests |
US20080243857A1 (en) * | 2004-02-13 | 2008-10-02 | France Telecom | Method for Editing a Multimedia Page Using Pre-Stored Data |
US20050204340A1 (en) * | 2004-03-10 | 2005-09-15 | Ruminer Michael D. | Attribute-based automated business rule identifier and methods of implementing same |
US20150019591A1 (en) * | 2004-05-21 | 2015-01-15 | Ronald Scott Visscher | Architectural Frameworks, Functions and Interfaces for Relationship Management (AFFIRM) |
US10579649B2 (en) * | 2004-05-21 | 2020-03-03 | Ronald Scott Visscher | Architectural frameworks, functions and interfaces for relationship management (AFFIRM) |
US8479157B2 (en) | 2004-05-26 | 2013-07-02 | Pegasystems Inc. | Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing evironment |
US7665063B1 (en) * | 2004-05-26 | 2010-02-16 | Pegasystems, Inc. | Integration of declarative rule-based processing with procedural programming |
US8959480B2 (en) | 2004-05-26 | 2015-02-17 | Pegasystems Inc. | Methods and apparatus for integration of declarative rule-based processing with procedural programming in a digital data-processing environment |
US20060107222A1 (en) * | 2004-09-10 | 2006-05-18 | Bea Systems, Inc. | Dynamic generation of wrapper classes to implement call-by-value semantics |
US8321465B2 (en) | 2004-11-14 | 2012-11-27 | Bloomberg Finance L.P. | Systems and methods for data coding, transmission, storage and decoding |
US20060269148A1 (en) * | 2004-11-14 | 2006-11-30 | Emanuel Farber | Systems and methods for data coding, transmission, storage and decoding |
US20060122976A1 (en) * | 2004-12-03 | 2006-06-08 | Shumeet Baluja | Predictive information retrieval |
US7574425B2 (en) * | 2004-12-03 | 2009-08-11 | International Business Machines Corporation | System and method for query management in a database management system |
US20060122975A1 (en) * | 2004-12-03 | 2006-06-08 | Taylor Paul S | System and method for query management in a database management system |
US20060143193A1 (en) * | 2004-12-29 | 2006-06-29 | Microsoft Corporation | Method and apparatus for metadata driven business logic processing |
US7321894B2 (en) * | 2004-12-29 | 2008-01-22 | Microsoft Corporation | Method and apparatus for building metadata driven software development kit |
AU2005229697B2 (en) * | 2004-12-29 | 2010-09-30 | Microsoft Corporation | Method and apparatus for metadata driven business logic processing |
US7433887B2 (en) * | 2004-12-29 | 2008-10-07 | Microsoft Corporation | Method and apparatus for metadata driven business logic processing |
KR101219875B1 (en) * | 2004-12-29 | 2013-01-08 | 마이크로소프트 코포레이션 | Method and apparatus for metadata driven business logic processing |
US20060143148A1 (en) * | 2004-12-29 | 2006-06-29 | Microsoft Corporation | Method and apparatus for building metadata driven software development kit |
KR101169169B1 (en) | 2004-12-30 | 2012-07-30 | 마이크로소프트 코포레이션 | Method and system for preserving unknown markup in a strongly typed environment |
US7559020B2 (en) * | 2004-12-30 | 2009-07-07 | Microsoft Corporation | Methods and systems for preserving unknown markup in a strongly typed environment |
US20060150083A1 (en) * | 2004-12-30 | 2006-07-06 | Microsoft Corporation | Methods and systems for preserving unknown markup in a strongly typed environment |
US8335704B2 (en) | 2005-01-28 | 2012-12-18 | Pegasystems Inc. | Methods and apparatus for work management and routing |
US20060218174A1 (en) * | 2005-03-23 | 2006-09-28 | Cook John L Iii | Method for coordinating schema and data access objects |
US8762410B2 (en) * | 2005-07-18 | 2014-06-24 | Oracle International Corporation | Document level indexes for efficient processing in multiple tiers of a computer system |
US20070016604A1 (en) * | 2005-07-18 | 2007-01-18 | Ravi Murthy | Document level indexes for efficient processing in multiple tiers of a computer system |
US20070016605A1 (en) * | 2005-07-18 | 2007-01-18 | Ravi Murthy | Mechanism for computing structural summaries of XML document collections in a database system |
US20070038666A1 (en) * | 2005-08-15 | 2007-02-15 | Microsoft Corporation | Independent explicit interface implementation |
US20070089117A1 (en) * | 2005-09-22 | 2007-04-19 | Xcalia | Implementation system for business applications |
US8209710B2 (en) * | 2005-09-22 | 2012-06-26 | Xcalia | Implementation system for business applications |
US20070130195A1 (en) * | 2005-12-06 | 2007-06-07 | Xiang Li | Modeling enumeration tables for relational databases |
US7693889B1 (en) | 2005-12-28 | 2010-04-06 | Emc Corporation | Automated backup and recovery for content repository |
US7574461B1 (en) * | 2005-12-28 | 2009-08-11 | Emc Corporation | Dividing data for multi-thread backup |
US7640222B2 (en) | 2006-03-03 | 2009-12-29 | Pegasystems Inc. | Rules base systems and methods with circumstance translation |
US8073802B2 (en) | 2006-03-03 | 2011-12-06 | Pegasystems, Inc. | Rules base systems and methods with circumstance translation |
US20070239646A1 (en) * | 2006-03-03 | 2007-10-11 | Alan Trefler | Rules base systems and methods with circumstance translation |
US20100088266A1 (en) * | 2006-03-03 | 2010-04-08 | Pegasystems Inc. | Rules base systems and methods with circumstance translation |
US8966456B2 (en) * | 2006-03-24 | 2015-02-24 | The Mathworks, Inc. | System and method for providing and using meta-data in a dynamically typed array-based language |
US20070288892A1 (en) * | 2006-03-24 | 2007-12-13 | The Mathworks, Inc. | System and method for providing and using meta-data in a dynamically typed array-based language |
US9658735B2 (en) | 2006-03-30 | 2017-05-23 | Pegasystems Inc. | Methods and apparatus for user interface optimization |
US8924335B1 (en) | 2006-03-30 | 2014-12-30 | Pegasystems Inc. | Rule-based user interface conformance methods |
US10838569B2 (en) | 2006-03-30 | 2020-11-17 | Pegasystems Inc. | Method and apparatus for user interface non-conformance detection and correction |
US20070233902A1 (en) * | 2006-03-30 | 2007-10-04 | Alan Trefler | User interface methods and apparatus for rules processing |
US9395963B1 (en) * | 2006-07-17 | 2016-07-19 | The Mathworks, Inc. | System and method for accessing meta-data in a dynamically typed array-based language |
US7945893B2 (en) | 2006-10-10 | 2011-05-17 | Oracle International Corporation | Mapping web services description language documents to XQuery functions |
US20080098346A1 (en) * | 2006-10-10 | 2008-04-24 | Rohan Angrish | Mapping Web Services Description Language documents to XQuery functions |
US7685167B2 (en) * | 2007-01-30 | 2010-03-23 | Bmc Software, Inc. | Configuration management database reference instance |
US20080183724A1 (en) * | 2007-01-30 | 2008-07-31 | Bmc Software, Inc. | Configuration Management Database Reference Instance |
US8141032B2 (en) | 2007-02-02 | 2012-03-20 | Microsoft Corporation | N-tiered applications support via common interface |
US20080189678A1 (en) * | 2007-02-02 | 2008-08-07 | Microsoft Corporation | N-tiered applications support via common interface |
US8250525B2 (en) | 2007-03-02 | 2012-08-21 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
US20080216055A1 (en) * | 2007-03-02 | 2008-09-04 | Pegasystems, Inc. | Proactive performance management for multi-user enterprise software systems |
US9189361B2 (en) | 2007-03-02 | 2015-11-17 | Pegasystems Inc. | Proactive performance management for multi-user enterprise software systems |
US20100287212A1 (en) * | 2007-05-21 | 2010-11-11 | Stefan Becker | Method for providing or operating a framework for the realization of independently developed programs |
US8396898B2 (en) * | 2007-05-21 | 2013-03-12 | Stefan Becker | Method for providing or operating a framework for the realization of independently developed programs |
WO2008141801A1 (en) * | 2007-05-21 | 2008-11-27 | Stefan Becker | A method for providing or operating a framework for the realization of independently developed programs |
US20090077536A1 (en) * | 2007-07-12 | 2009-03-19 | The Mathworks, Inc. | Programming environment with support for handle and non-handle user-created classes |
US9311111B2 (en) * | 2007-07-12 | 2016-04-12 | The Mathworks, Inc. | Programming environment with support for handle and non-handle user-created classes |
US20090138894A1 (en) * | 2007-11-28 | 2009-05-28 | Red Hat, Inc. | Automatic Object Instantiation |
US8707257B2 (en) | 2007-11-28 | 2014-04-22 | Red Hat, Inc. | Automatic object instantiation |
US8504986B2 (en) * | 2008-01-23 | 2013-08-06 | Red Hat, Inc. | Calling functions as methods |
US20090187885A1 (en) * | 2008-01-23 | 2009-07-23 | Schneider James P | Calling functions as methods |
US20100057834A1 (en) * | 2008-08-29 | 2010-03-04 | Macken Luke J | Method and System for Facilitating Client Server Interaction |
US20100057937A1 (en) * | 2008-08-29 | 2010-03-04 | Macken Luke J | Method and System for Facilitating Client Server Interaction |
US8793398B2 (en) * | 2008-08-29 | 2014-07-29 | Red Hat, Inc. | Facilitating client server interaction |
US8793339B2 (en) | 2008-08-29 | 2014-07-29 | Red Hat, Inc. | Facilitating client server interaction |
US20100083285A1 (en) * | 2008-09-26 | 2010-04-01 | Microsoft Corporation | Data-tier application component |
US8396845B2 (en) | 2008-09-26 | 2013-03-12 | Microsoft Corporation | Data-tier application component |
US10467200B1 (en) | 2009-03-12 | 2019-11-05 | Pegasystems, Inc. | Techniques for dynamic data processing |
US9678719B1 (en) | 2009-03-30 | 2017-06-13 | Pegasystems Inc. | System and software for creation and modification of software |
US20110106778A1 (en) * | 2009-11-05 | 2011-05-05 | Oracle International Corporation | Lock manager on disk |
US8510334B2 (en) | 2009-11-05 | 2013-08-13 | Oracle International Corporation | Lock manager on disk |
US9111006B2 (en) * | 2010-03-16 | 2015-08-18 | Salesforce.Com, Inc. | System, method and computer program product for communicating data between a database and a cache |
US20110231481A1 (en) * | 2010-03-16 | 2011-09-22 | Saleforce.com, inc. | System, method and computer program product for communicating data between a database and a cache |
US8392442B2 (en) * | 2010-04-15 | 2013-03-05 | Dee Gee Holdings, Llc | Method and computer program product for creating content management systems |
US20110258224A1 (en) * | 2010-04-15 | 2011-10-20 | Dee Gee Holdings, Llc | Method and computer program product for creating content management systems |
US20230042944A1 (en) * | 2010-05-14 | 2023-02-09 | Sap Se | Integrated Application Server and Data Server Processes with Matching Data Formats |
US11822569B2 (en) * | 2010-05-14 | 2023-11-21 | Sap Se | Integrated application server and data server processes with matching data formats |
US20130297755A1 (en) * | 2010-11-23 | 2013-11-07 | Nokia Siemens Networks Oy | Network element configuration management |
US9104437B2 (en) | 2010-12-06 | 2015-08-11 | International Business Machines Corporation | Efficient serialization of mutable objects |
US9158555B2 (en) * | 2010-12-06 | 2015-10-13 | International Business Machines Corporation | Efficient serialization of mutable objects |
US20120144405A1 (en) * | 2010-12-06 | 2012-06-07 | Ibm Corporation | Efficient Serialization of Mutable Objects |
US9270743B2 (en) | 2011-02-18 | 2016-02-23 | Pegasystems Inc. | Systems and methods for distributed rules processing |
US8880487B1 (en) | 2011-02-18 | 2014-11-04 | Pegasystems Inc. | Systems and methods for distributed rules processing |
US9740458B1 (en) | 2011-06-23 | 2017-08-22 | The Mathworks, Inc. | Restricting class inheritance relationships |
US9015661B1 (en) * | 2011-06-23 | 2015-04-21 | The Mathworks, Inc. | Restricting class inheritance relationships |
US8583871B2 (en) * | 2011-11-04 | 2013-11-12 | Paul A. Lipari | System and method for managing an object cache |
US9542329B1 (en) * | 2011-11-04 | 2017-01-10 | Open Invention Network, Llc | System and method for managing an object cache |
US8266384B1 (en) * | 2011-11-04 | 2012-09-11 | Recursion Software, Inc. | System and method for managing an object cache |
US9792166B2 (en) * | 2011-11-04 | 2017-10-17 | Open Invention Network, Llc | System and method for managing an object cache |
US8769203B2 (en) * | 2011-11-04 | 2014-07-01 | Open Invention Network, Llc | System and method for managing an object cache |
US9940243B1 (en) * | 2011-11-04 | 2018-04-10 | Red Hat, Inc. | System and method for managing an object cache |
US9280481B1 (en) * | 2011-11-04 | 2016-03-08 | Open Invention Network Llc | System and method for managing an object cache |
US20130117405A1 (en) * | 2011-11-04 | 2013-05-09 | Recursion Software, Inc. | System and method for managing an object cache |
US8954677B1 (en) * | 2011-11-04 | 2015-02-10 | Open Invention Network, Llc | System and method for managing an object cache |
US9195936B1 (en) | 2011-12-30 | 2015-11-24 | Pegasystems Inc. | System and method for updating or modifying an application without manual coding |
US10572236B2 (en) | 2011-12-30 | 2020-02-25 | Pegasystems, Inc. | System and method for updating or modifying an application without manual coding |
US20140331118A1 (en) * | 2013-05-06 | 2014-11-06 | Sap Ag | Persisting Objects in a Single Data Table |
US9442941B1 (en) * | 2014-03-28 | 2016-09-13 | Emc Corporation | Data structure for hash digest metadata component |
US10042871B2 (en) * | 2014-05-30 | 2018-08-07 | Amadeaus S.A.S. | Content management in a travel management system |
US10891279B2 (en) | 2014-05-30 | 2021-01-12 | Amadeus S.A.S. | Content management in a travel management system |
US11107010B2 (en) | 2014-05-30 | 2021-08-31 | Amadeus S.A.S. | Content exchange with a travel management system |
US11113637B2 (en) | 2014-05-30 | 2021-09-07 | Amadeus S.A.S. | Content exchange with a travel management system |
US10049329B2 (en) | 2014-05-30 | 2018-08-14 | Amadeus S.A.S. | Content exchange with a travel management system |
US20150347476A1 (en) * | 2014-05-30 | 2015-12-03 | Amadeus S.A.S. | Content management in a travel management system |
US10469396B2 (en) | 2014-10-10 | 2019-11-05 | Pegasystems, Inc. | Event processing with enhanced throughput |
US11057313B2 (en) | 2014-10-10 | 2021-07-06 | Pegasystems Inc. | Event processing with enhanced throughput |
US10671366B2 (en) * | 2015-12-22 | 2020-06-02 | Alibaba Group Holding Limited | App program running method and apparatus |
US10152527B1 (en) | 2015-12-28 | 2018-12-11 | EMC IP Holding Company LLC | Increment resynchronization in hash-based replication |
US10324782B1 (en) | 2016-03-24 | 2019-06-18 | Emc Corporation | Hiccup management in a storage array |
US9857990B1 (en) | 2016-03-24 | 2018-01-02 | EMC IP Holding Company LLC | Fast startup for modular storage systems |
US10101934B1 (en) | 2016-03-24 | 2018-10-16 | Emc Corporation | Memory allocation balancing for storage systems |
US10705907B1 (en) | 2016-03-24 | 2020-07-07 | EMC IP Holding Company LLC | Data protection in a heterogeneous random access storage array |
US10698599B2 (en) | 2016-06-03 | 2020-06-30 | Pegasystems, Inc. | Connecting graphical shapes using gestures |
US10698647B2 (en) | 2016-07-11 | 2020-06-30 | Pegasystems Inc. | Selective sharing for collaborative application usage |
US10223008B1 (en) | 2016-09-30 | 2019-03-05 | EMC IP Holding Company LLC | Storage array sizing for compressed applications |
US10255172B1 (en) | 2016-09-30 | 2019-04-09 | EMC IP Holding Company LLC | Controlled testing using code error injection |
US10152371B1 (en) | 2016-09-30 | 2018-12-11 | EMC IP Holding Company LLC | End-to-end data protection for distributed storage |
US10339337B1 (en) * | 2017-01-12 | 2019-07-02 | Marklogic Corporation | Apparatus and method for supplying secure relational query results from a semi-structured document database |
US11048488B2 (en) | 2018-08-14 | 2021-06-29 | Pegasystems, Inc. | Software code optimizer and method |
US10789048B2 (en) * | 2019-01-30 | 2020-09-29 | Salesforce.Com, Inc. | Namespace and class utilities for managed packages |
US11755744B2 (en) * | 2019-11-07 | 2023-09-12 | Oracle International Corporation | Application programming interface specification inference |
US11567945B1 (en) | 2020-08-27 | 2023-01-31 | Pegasystems Inc. | Customized digital content generation systems and methods |
CN112817580A (en) * | 2021-01-27 | 2021-05-18 | 北京奇艺世纪科技有限公司 | Data processing method and device, electronic equipment and storage medium |
CN112817580B (en) * | 2021-01-27 | 2023-09-01 | 北京奇艺世纪科技有限公司 | Data processing method and device, electronic equipment and storage medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6085198A (en) | Integrated three-tier application framework with automated class and table generation | |
US6895401B2 (en) | Method and apparatus of performing active update notification | |
Balter et al. | Architecture and implementation of Guide, an object-oriented distributed system | |
US6993743B2 (en) | Method and apparatus for developing enterprise applications using design patterns | |
US5737607A (en) | Method and apparatus for allowing generic stubs to marshal and unmarshal data in object reference specific data formats | |
US6564377B1 (en) | Self-describing components within a software catalog | |
US5815710A (en) | Method and apparatus for managing relationships among objects in a distributed object environment | |
US6959307B2 (en) | Process and system for a client object to perform a remote method invocation of a method in a server object | |
US6006230A (en) | Database application development system with improved methods for distributing and executing objects across multiple tiers | |
US7213049B2 (en) | System and method for transaction processing with transaction property feature | |
US6263498B1 (en) | Method and apparatus for enabling server side distributed object modification | |
US20020178298A1 (en) | Method and apparatus for fast, local CORBA object references | |
AU2002318249A1 (en) | System and method for transaction processing with transaction property feature | |
Myerson | The complete book of middleware | |
US6405363B1 (en) | Class casting support for run-time extensible items in an object oriented framework | |
US6256780B1 (en) | Method and system for assembling software components | |
WO2002037335A2 (en) | Object-oriented database abstraction and statement generation | |
Pour | Enterprise JavaBeans, JavaBeans and XML expanding the possibilities for Web-based enterprise application development | |
WO2002037336A2 (en) | Object-oriented database abstraction and statement generation | |
Austin et al. | Advanced Programming for the JavaTM 2 Platform | |
US20040230602A1 (en) | System and method for decoupling data presentation layer and data gathering and storage layer in a distributed data processing system | |
US20090228900A1 (en) | Systems and methods for application programming using persistent objects | |
WO2003030020A2 (en) | Handling relational metanodes in databases | |
Fatoohi et al. | Middleware for Building Distributed Applications Infrastructure | |
Pour | Component Technologies: Expanding the Possibilities for Development of Web-Based Enterprise Applications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SKINNER, BRIAN;TURK, ANDY KITTRIDGE;MCDONNELL, KEVIN;AND OTHERS;REEL/FRAME:009482/0788;SIGNING DATES FROM 19980819 TO 19980820 Owner name: SUN MICROSYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SKINNER, BRIAN;TURK, ANDY KITTRIDGE;MCDONNELL, KEVIN;AND OTHERS;REEL/FRAME:010548/0885;SIGNING DATES FROM 19980819 TO 19980820 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REMI | Maintenance fee reminder mailed | ||
FPAY | Fee payment |
Year of fee payment: 8 |
|
SULP | Surcharge for late payment |
Year of fee payment: 7 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: S.F. IP PROPERTIES 15 LLC, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SUN MICROSYSTEMS, INC.;REEL/FRAME:021861/0306 Effective date: 20080304 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: RATEZE REMOTE MGMT. L.L.C., DELAWARE Free format text: MERGER;ASSIGNOR:S.F. IP PROPERTIES 15 LLC;REEL/FRAME:037183/0391 Effective date: 20150826 |
|
AS | Assignment |
Owner name: HANGER SOLUTIONS, LLC, GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLECTUAL VENTURES ASSETS 161 LLC;REEL/FRAME:052159/0509 Effective date: 20191206 |
|
AS | Assignment |
Owner name: INTELLECTUAL VENTURES ASSETS 161 LLC, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RATEZE REMOTE MGMT. L.L.C.;REEL/FRAME:051949/0145 Effective date: 20191126 |