|Publication number||US8015572 B2|
|Application number||US 11/734,239|
|Publication date||Sep 6, 2011|
|Filing date||Apr 11, 2007|
|Priority date||Feb 22, 2002|
|Also published as||CA2477790A1, CN1647042A, EP1485800A1, EP1485800A4, US7516447, US8484664, US20030167358, US20070199002, US20110289477, WO2003073275A1|
|Publication number||11734239, 734239, US 8015572 B2, US 8015572B2, US-B2-8015572, US8015572 B2, US8015572B2|
|Inventors||Kyle W. Marvin, David Bau, III, Roderick A. Chavez|
|Original Assignee||Oracle International Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (212), Non-Patent Citations (53), Classifications (14), Legal Events (2)|
|External Links: USPTO, USPTO Assignment, Espacenet|
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
This application is a divisional of U.S. patent application Ser. No. 10/233,118, filed Aug. 30, 2002, by Kyle W. Marvin et al., entitled METHODS AND APPARATUS FOR BUILDING, CUSTOMIZING AND USING SOFTWARE ABSTRACTIONS OF EXTERNAL ENTITIES, which claims benefit from U.S. Provisional Patent Application No. 60/359,409, filed Feb. 22, 2002, by Kyle W. Marvin, et al., entitled UNIFIED FRAMEWORK FOR INTERACTING WITH EXTERNAL ENTITIES FROM A PROGRAMMING LANGUAGE AND EXAMPLE APPLICATIONS.
This application is related to the following co-pending application which is hereby incorporated by reference in its entirety:
U.S. patent application Ser. No. 10/780,346, filed Feb. 17, 2004, by Kyle W. Marvin, et al., entitled SYSTEMS AND METHODS FOR AN EXTENSIBLE SOFTWARE PROXY, (Attorney Docket No. BEAS-01444US1).
U.S. patent application Ser. No. 10/784,492, filed Feb. 23, 2004, by Kyle W. Marvin, et al., entitled SYSTEMS AND METHODS FOR CREATING NETWORK-BASED SOFTWARE SERVICES USING SOURCE CODE ANNOTATIONS.
The present invention relates to the field of data processing. More specifically, the present invention is related to software interaction methods.
In the course of developing modern software applications, developers are often confronted with the problem of interacting with external entities that don't look, feel or behave like familiar internal programming language objects. These external entities include databases, legacy systems, web services, non-native software components, as well as physical objects (e.g. to control their settings).
Generally, the programmer must learn new paradigms, skills and techniques for interacting with each of these entities. In addition, the programmer must develop or acquire a potentially large body of software to deal with the intricacies of each type of external entity. For example, writing software that interacts with an external web service may require the developer to master several new technologies, including the eXtensible Markup Language (XML), the XML Schema Language, the XML Protocol (XP a.k.a SOAP) and the Web Service Description Language (WSDL).
Each type of external entity with which the application interacts requires a different set of skills, knowledge and software from the developer. E.g., interacting with a database requires a completely difference set of skills, knowledge and software than interacting with an external web services. The additional burden associated with learning and implementing technologies for interacting with a variety of external entities increases the time, knowledge, skills and ultimately money required to develop a software application.
What is needed is a simple software abstraction that provides uniform access to external entities, reuses the developer's existing knowledge of general software concepts, and minimizes the specialized knowledge required for interacting with each type of external entity. Not only should these software abstractions be easy to use, but they should also be easy to customize for a particular purpose, with little or no software development. The software abstraction should make it easy to interact with several instances of an external entity simultaneously (e.g., use several instances of a web service to perform credit checks for several customers simultaneously). It should also simplify the handling of asynchronous events (e.g., a database trigger) generated by one or more instances of an external entity.
Consider for example the computing environment of
Server 125 offers as an example ecommerce application 130, with which users of various client devices, such as client 112, may shop and purchase various items. Ecommerce application 130 may include a number of web pages 131 having contents, such as merchandise descriptions, reviews and pricing information, and one or more functions 132.
Complementarily, server 102 offers, as an example, shopping cart service 104 used by ecommerce applications, such as ecommerce application 130 (e.g., when users of client devices interact with their web pages/functions 131/132). As a result, developers of ecommerce applications need not develop their own “shopping cart” functions, and may concentrate their effort on the contents of web pages 131 instead.
Shopping cart service 104 may include e.g. an “add an item to cart” function, a “remove an item from cart” function, and a “checkout” function. In response to a user's selection of e.g. a graphical button displayed on a web page 131, one of functions 132 may cause one or more requests for the appropriate shopping cart functions to be generated and sent to shopping cart service 104 for processing on server 102.
Processing of these requests may in turn require the shopping cart functions to interact for example with services 118 and 128 of servers 115 and 120. Examples of services 118 and 128 are credit authorization, inventory or production slots confirmation, shipment/delivery scheduling, and so forth.
Thus, even in this limited example, developers of ecommerce applications 130 have to equip applications 130 to interact with an external “shopping cart” service 104, while developers of “shopping cart” service 104 have to equip service 104 to interact with external entities such as credit authorization, inventory/production slot confirmation, shipment/delivery scheduling, and so forth.
In addition to the general purpose web service software (e.g., XML, SOAP, WSDL) normally required to facilitate these interactions, each type of web service (e.g., shopping card, credit authorization, shipping) requires specialized software be written to interact with its specific features. For example, software must be written to create the “add item to cart” XML message and send it to the URL address associated with the correct shopping basket. In addition, software must be written to map messages returned by the credit check and shipping services into a form that may be presented to the end user.
As those skilled in the art would appreciate, typically, the example would require simultaneous and asynchronous interaction with several instances of each external service. E.g., at any instance in time, an ecommerce application 130 may be hosting many users, each having a separate shopping cart, containing different items. Shopping cart service 104 in turn may be processing shopping cart interactions for a multitude of carts of different users of different ecommerce applications. In like manner, a credit authorization service may be processing authorization requests for a multitude of checkouts occurring for a number of ecommerce applications at the same time. Notification of final credit approval and shipping arrangements for each of these transactions may occur asynchronously (e.g., via e-mail) after the customer has completed their order(s). Clearly, it is critical that the shopping carts, credit authorizations, shipping details and notifications associated with each customer are correlated and kept separate from that of other customers, even when several customer requests are processed simultaneously. The software required to handle the required correlation and asynchronous event handling can become quite complex.
Even in this relatively simple example, it is clear application developers must generally acquire new and specialized skills, knowledge and software to interact with external entities. They must often create specialized software for interacting with specific forms of each external entity. They must also deal with the complexities of interacting simultaneously and asynchronously with several instances of a given type of entity. Accordingly, a simple software abstraction that provides uniform access to external entities, simplifies creating specialized software abstractions for specific types of external entities, and facilitates interacting simultaneously and asynchronously with multiple instances of an external entity is desired.
The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denote similar elements, and in which:
The present invention includes a method and apparatus for simplifying the development, customization and use of proxy objects as software abstractions for interacting with external entities from within a software application.
In the following description, various aspects of the present invention will be described. However, it will be apparent to those skilled in the art that the present invention may be practiced with only some or all aspects of the present invention. For purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one skilled in the art that the present invention may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the present invention.
Parts of the description will be presented in data processing terms, such as data, selection, retrieval, generation, and so forth, consistent with the manner commonly employed by those skilled in the art to convey the substance of their work to others skilled in the art. As well understood by those skilled in the art, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, and otherwise manipulated through electrical and/or optical components of a processor and its subsystems.
Part of the descriptions will employ various abbreviations, including but are not limited to:
Uniform Resource Locator
eXtended Markup Language
The term “external entity” as used in the application (including the claims) to refer to “external” hardware as well as software entities. “External” is viewed from the perspective of the software application interacting with the entity.
Section Headings, Order of Descriptions and Embodiments
Section headings are merely employed to improve readability, and they are not to be construed to restrict or narrow the present invention.
Various operations will be described as multiple discrete steps in turn, in a manner that is most helpful in understanding the present invention, however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations need not be performed in the order of presentation.
The phrase “in one embodiment” is used repeatedly. The phrase generally does not refer to the same embodiment, however, it may. The terms “comprising”, “having” and “including” are synonymous, unless the context dictates otherwise.
More specifically, a developer may create a proxy object definition 204 for external entity 202. The developer may be the developer of external entity 202, a third party developer, or even the developer of application 240.
Proxy object definition 204 includes interface declaration 205 identifying that a proxy object 254 should be generated based on the definition for interacting with an external entity. Further proxy objection definition 204 includes default property settings 206 for defining the default behavior and default implementation 210 of proxy object 254, callback declarations 208 for handling asynchronous events from external entity 202 and function declarations 209 for initiating interactions with external entity 202.
In one embodiment, the one or more proxy object implementation classes 210 include a run-time implementation class. In another embodiment, the one or more implementation classes 210 further include a compile-time implementation class. In yet another embodiment, implementation classes 210 further include a design-time implementation class.
The run-time implementation class provides the run-time implementations for the functions declared in proxy object declaration 204 and used by software application code 220 to interact with external entity 202 programmatically. The run-time implementation class may provide one or more built-in functions 211 for initiating interaction with external entity 202 and one or more built-in callbacks 212 for handling asynchronous events generated by external entity 202.
The optional compile time implementation class provides the compile time validation implementation to assist compiler 230 in validating usage of the functions and property settings by proxy object definition 204 and by application code 220, during compilation.
The optional design-time implementation class provides the design-time implementation for assisting developers of proxy object definitions 204 and application code 220. It assists developers to extend and use properties and functions implemented by the run-time implementation for interacting with external entity 202 programmatically. An example of such design-time implementation includes but is not limited to a graphical wizard that guides the developer through the creation of a proxy object definition for a specific external web service given the WSDL description of that web service. Another example is the provision of graphic icons corresponding to usage of the functions of proxy object definition 204, which when selected for an application code 220, inserts the corresponding function call into the application code 220.
For the illustrated embodiment, the proxy object implementation 210 may implement one or more interfaces 214-218. In particular, for the embodiment, proxy object implementation 210 may implement builder interface 214, resource interface 216, and extensible interface 218.
Builder interface 214 may be implemented by the compile-time component of proxy object implementation 210 to assist compiler 230 in validating the usage of properties and functions implemented by proxy object implementation 210. Resource interface 216 may be implemented by the run-time component of proxy object implementation 210 to acquire and release critical resources, such as databases and file handles, needed by the proxy object implementation. Extensible interface 214 may be implemented by the run-time component of proxy object implementation 210 to enable proxy object definitions 204 to declare new functions not built-in to proxy object implementation 210.
Still referring to
Software application code 220, proxy object definitions 204, and proxy object implementations 210 equipped in accordance with the present invention are compiled into application 240, proxy objects 254, and meta-data 252 using enhanced compiler 230.
Compiler 230 is enhanced to recognize proxy object definitions 204 and generate associated proxy objects 254 using proxy object implementations 210 to facilitate interaction with software entity 202 at runtime. Compiler also generates proxy initialization code 242 that creates a proxy object for each proxy object declaration 222, assigns the proxy object to the declared variable, and registers the proxy object with asynchronous event router 256 to receive appropriate events generated by the associated external entity 202. Further, compiler 230 is enhanced to gather and output meta-data 252 describing the interfaces, functions, callbacks and property settings of property object definitions 204 for use by the corresponding proxy object 254 at runtime.
Still referring to
For the embodiment, as described earlier, proxy object definition 204 may declare one or more callback functions 208 for handling asynchronous events generated by corresponding external entity 202. Complementarily, runtime engine 250 includes asynchronous event router 256 for listening for, receiving, and routing asynchronous events generated by external entity 202 to appropriate proxy objects 254 for processing by event handling code 246 of application 240. The locations listened to by asynchronous event router 256 are specified by proxy initialization code 242 based on proxy object implementation 210 and associated property settings 204 and 223.
Using the mechanisms described above, developers may create application code 220 to interact with external entities 202 by invoking functions on declared proxy objects 222, setting proxy object properties 223 and defining event handlers 224. Interacting with external entities in this way is very similar to interacting with other software objects and does not require the developer to learn excessive new paradigms, skills and/or techniques. In addition, developers may create new proxy object definitions 204, even with new functions and callbacks without specifying the implementation of the new functions or callbacks. The resulting proxy objects 254 in cooperation with run-time engine 250 handle multiple simultaneous and asynchronous interactions with external entity 202.
In various embodiments, the external entity 202 may be a web service, a database, or a legacy system, as well as physical objects.
Provision of the optional design time implementation class is not an essential aspect to practice the present invention. Moreover, it is within the ability of those ordinarily skilled in the art, thus will not be further described. Other aspects of the present invention will be further described in turn below.
Proxy Object Definition
In one embodiment, this is achieved by declaring that proxy object definition 204 extends a special “proxy object” marker interface (402 of
Referring back to
Further, the programmer or design-time tool may optionally specify function declarations 209 of proxy object definition 204, block 304. Application code 220 may use the declared functions to programmatically interact with external entity 202. Function declarations 209 may correspond to built-in functions 211 of proxy object implementation 210, or if proxy object implementation 210 implements extensible interface 214, function declarations 209 may introduce new functions not provided explicitly by proxy object implementation 210.
In addition, the programmer or design-time tool may optionally specify callback function declarations 208 representing asynchronous events that may be generated at run-time by external entity 202. Callback function declarations 208 may correspond to built-in callback functions 212 of proxy object implementation 210, in which case proxy object 254 will route corresponding asynchronous events generated by external entity 202 to proxy object implementation 210 for processing (which may, in turn, route them to event handling code 246 of application 240). When callback function declarations 208 do not correspond to built-in callback functions 212 of proxy object implementation 210, proxy object 254 will route corresponding asynchronous events generated by external entity 202 directly to event handling code 246 of application 240.
Further, the developer or design-time tool may specify the implementation classes of the proxy object definition 204, which includes the runtime implementation class, and optionally, the compile time implementation class and/or the design time implementation class, block 306. Proxy object definition 204 need not specify implementation classes if it extends another proxy object definition that specifies implementation classes. In this case, the implementation class specifications are inherited from the extended proxy object definition.
In one embodiment, specifications of the implementation classes are made using property settings. In one embodiment, property settings are specified in an annotation form, i.e. in what is conventionally considered to be comments of a source file.
Further, the Timer interface is specified as having a setTimeoutIn(int milliseconds) function 504 a, a setTimeoutAt(java.util.Date date) function 504 b, and so forth for application code 220 to set an “alarm” after n elapsed units of time or at a specific moment in time.
In addition, the Timer interface includes a callback function 504 c for handling alarm events generated by external entity 202 e.g., by passing them to application 240 asynchronously, when the timer expires at the requested time. In one embodiment, callback declarations are functions defined in a nested interface named “Callback” as depicted in
The runtime, compile time and design time implementation classes are specified as “com.bea.jws.private.TimerImpl” 512, “com.bea.jws.private.TimerValidator” 514, and “com.bea.jws.private.TimerDesigner” 516 respectively. The specifications are made using property settings. In one embodiment, property settings are specified in an annotation form in a comment section. As those skilled in the art will recognize, property settings in this example are specified using the special Javadoc annotation @implementation 510.
Proxy Object Implementation
Except for the exploitation of extensible, resource and/or builder interfaces 214-218, usage of proxy context object 258, and implementation of facilities in conformance to the expected execution paradigm, the core constitution of each implementation class, whether it is runtime, compile time, or design time, is application dependent. That is, they vary depending on the behavior of and services offered by external entity 202, and the nature of the functions.
However, as alluded earlier, the runtime implementation class is expected to implement the functions of the proxy object definition 204 in the execution context of the present invention either directly through built-in functions 211 or indirectly through the “invoke” function of extensible interface 218.
As described earlier, builder interface 214, when implemented by a compile time implementation class, assists compiler 230 to validate the properties defined by the proxy object definition 204 and used by application code 220 are supported by proxy object implementation 210. In addition, builder interface may be used by an integrated development environment to help the developer understand where and how properties may be used.
Resource interface 216, when implemented by a runtime implementation class, assists the runtime implementation class in acquiring and releasing resources, such as database connections and file handles.
Extensible interface 218, when implemented by a runtime implementation class, enables proxy object definitions 204 to declare new functions, not directly supported by proxy object implementation 210, without defining how those functions are implemented.
For the illustrated embodiment, builder interface 218 includes in particular a Get Property Syntax function 602, Validate Class Properties function 604, and Validate Field Properties function 606. As the names of these functions suggest, when invoked, these functions return a description of the valid property syntaxes for the proxy object and validate the class and field level properties of the proxy object.
In one embodiment, when invoked, Get Property Syntax function 602 returns a URL identifying a file provided by the developer of the compile time implementation class, describing the valid property syntax in the form of a XML file.
An example snippet of such a XML file is illustrated in
For the example snippet, it specifies that the “@sql” property is only allowed in front of proxy object definition functions 208, and the presence of the property is required here. The @sql property may have statement, maxcount, and returnType attributes. The statement attribute is required. Unless specified otherwise, all attributes must be assigned values. Maxcount and returnType are optional. Maxcount takes an integer value, and the default value is infinity. Unless specified otherwise, attributes (such as Statement and returnType) take string values, and the default value is the empty string. The @pool annotation is allowed in front of proxy object declarations 222, proxy object definition functions 209, and proxy object definitions 204, and is optional in all these locations. Finally, the @pool annotation can have a name attribute, which should be present and have a string value.
In alternate embodiments, the information may be provided and/or returned in other formats or using other data organization techniques.
Implementations of Get Property Syntax function 602, Validate Class Properties function 604, and Validate Filed Properties function 606 are within the ability of those skilled in the art, accordingly will not be further described.
Implementing the builder interface 218 enables a compile time implementation class to use these functions to provide the expected syntax, and to validate the meta data, for compiler 230.
Referring back to
Still referring to
Similarly, implementation of Invoke Object function 616 is within the ability of those skilled in the art, accordingly will not be further described.
Then, at block 802, a proxy object definition 204 is created, extending the marker ProxyObject interface directly or indirectly through another proxy object definition. If proxy object definition extends ProxyObject marker interface directly it specifies the associated proxy object implementation 210 e.g. using an “implementation” property. A proxy object definition that extends the ProxyObject marker interface indirectly may also specify an associated implementation overriding the implementation associated with its base class. The proxy object definition may also specify new default property values and if implementation 210 is extensible specify new functions and callbacks. The proxy object definition may be made by the developer of application 220, developer of proxy object implementation 210 or another independent third party. As described earlier, a proxy object definition 204 is extensible if the associated implementation 210 implements extension interface 214. Example extensions will be described below referencing
At block 804, a developer of application 220 inserts one or more proxy object declarations 222 into application code 220 referencing proxy object definition 204. As alluded to earlier, the proxy object definition 204 may be the base proxy object definition 204 e.g. offered by the developer of the software abstraction of external entity 202 or it may be a customized version of the proxy object definition 204. An example declaration will be described below referencing
At block 806, a developer of application 220 specifies values for applicable ones of the properties of the proxy object definition 204. In one embodiment, the specification is in annotation form within a comment section of the source file. An example specification will be described below referencing
Having inserted proxy object declarations 222, and for applicable ones, if any, the property values, at block 808, an application 220 may interact with external entity 202 programmatically, using the functions defined by proxy object definitions 204 and implemented by implementation 210 either directly using built-in functions 211 or indirectly by the extensible interface 218.
As alluded to earlier, a developer of application 220 may also specify a handler for asynchronous events generated and sent by an asynchronous event generation function of the software abstraction of external entity 202. An example specification will be described below referencing
Customizing Proxy Object Properties
Those skilled in the art of course will recognize that the above example is purposely kept simply to facilitate illustration and ease of understanding. In practice, a proxy object definition of the present invention may customize default property settings much more extensively. In particular, a proxy object definition may also customize properties associated with property object functions and callbacks. In addition, property object definitions may be customized multiple times successively, that is a customized property object definition may itself be further customized.
Customizing Proxy Object Interfaces
When a proxy object implementation 210 implements extensible interface 214, it is also possible to customize the interface of associated proxy object definitions 204 by adding new function declarations 209 and callback declarations 208.
Line 1028 is a function declaration adding the function getEmployeeData to the existing list of functions inherited from the Database proxy object definition. This function may be invoked by application 240 at run-time to interact with the external employee database described by proxy object definition 1020. Note, however, that none of the proxy object definitions or proxy object implementation specifically implements the getEmployeeData function. The details of exactly how invocations to functions 209 declared by proxy object declarations 204 are handled at run-time is further specified below.
Line 1026 is a property setting describing the desired semantics of the getEmployeeData function and line 1024 defines the EmployeeRecord data structure returned by the getEmployeeData function. All interface declarations 205, property settings 206, callback declarations 208, function declarations 209 and associated definitions (e.g., the EmployeeRecord data structure) are stored by compiler 230 in meta-data 252 and available to proxy object 254 at run-time via proxy context object 258. This meta-data assists proxy object 254 and proxy object implementation 210 to provide implementations of functions 208 and callbacks 209 declared by proxy object definitions 204.
Using Proxy Objects
If no proxy object declarations of the present invention are found, application code 220 is compiled as other software entities in the prior art, block 1106. The exact nature of this compilation is language and compiler implementation dependent.
If at least one proxy object declaration of the present invention is found, compiler 230 gathers the meta data necessary to describe each proxy object of the present invention, block 1108.
In one embodiment, the meta data gathering operation includes identifying and extracting property settings 223 from application code 220 and default property settings 206 from all associated proxy object definitions 204, including proxy object definitions from which the proxy object definitions identified in proxy object declarations 222 are derived. In addition, meta data gathering includes identifying and extracting the names and signatures of declared interfaces 205, declared functions 209 and declared callbacks 208 from all associated proxy object definitions 204 as well as the names and signatures of built-in functions 211 and built-in callbacks 212 of proxy object implementation 210.
In one embodiment, property settings are specified using a Javadoc annotation form in the comment sections of the source file of application code 220 and proxy object definitions 204. Compiler 230 includes a property processor (not shown) responsible for parsing the comment sections of the source file of application code 220 and proxy object definitions 204.
In one embodiment, consultation with the compile time implementation class is also performed by the property processor of compiler 230 to verify the property settings and associated properties are implemented and allowed by proxy object implementation 210. In one embodiment, the consultation is made through the functions of builder interface 218.
Upon gathering up the meta data necessary to describe each proxy object of the present invention, compiler 230 outputs one or more meta data files 252 containing the gathered meta data, block 1110, for use by the corresponding proxy object 254 during runtime.
Then, compiler 230 generates a proxy object 254 for each proxy object definitions 204 associated with (e.g., referenced by) proxy object declarations 222 to facilitate the interaction between the application 240 and the external entity 202. This process is described in more detail below referencing
Further, compiler 230 generates proxy initialization code 242 for each proxy object declaration 222, block 1124. At run-time, each instance of proxy initialization code 242 creates a proxy object implementing the interface identified in the associated proxy object declaration 222, assigns the proxy object to the proxy object variable identified in the associated proxy object declaration 222 and registers the proxy object with asynchronous event router 256 to receive all asynchronous events from associated external entity 202.
Next, compiler 230 compiles the rest of the application code 220 as in the prior art inserting proxy initialization code 242 to run prior to associated proxy invocation code 244 and event handling code 246, block 1106. The manner the compilation is performed is language and compiler dependent.
Further, implementation of the property processor is within the ability of those skilled in the art, and will not be further described.
Further, Proxy object 254 and proxy object implementation 210 have access to meta-data 252 via proxy object context 258 describing associated proxy object definitions 204 (including interface declarations, property settings, callback declarations and function declarations) and property settings 223. This meta-data may be used at runtime to determine the desired semantics of invocations to function interfaces 1224 that don't have a corresponding built-in function 211. In one embodiment, a reference to proxy object context 258 may be obtained by calling the global function getProxyContext( ) provided by runtime engine 250. At run-time, the getProxyContext( ) function will return the proxy object instance associated with the current proxy object invocation as described further below.
As described earlier, in various embodiments, proxy object context 258 includes various methods for facilitating access of the “context” information. In one embodiment, these methods include a getMetaData( ) method for getting meta data, and a getAttribute( ) method for getting particular property values. Meta data may e.g. include methods, arguments, fields, and/or annotations associated with the proxy object functions and callbacks.
In one embodiment, proxy object context 258 also includes a getInstanceID( ) to facilitate obtaining the unique ID of the proxy object instance, and a sendEvent( ) for sending asynchronous events to application 240. In one embodiment, sendEvent( ) determines the appropriate event handler 246 to invoke by appending the name of the event to the name of the proxy object variable specified in proxy object declaration 222. It extracts the event name and proxy object variable name from meta-data 252. Implementation of these methods are within the ability of those skilled in the art, accordingly will not be further described. In alternate embodiments, the present invention may be practiced with more or less methods associated with proxy object context 258.
As described earlier, at block 1112, compiler 230 generates proxy object 254, more specifically, using information collected from application code 220, proxy object definitions 204 and proxy object implementation 210. As illustrated in
If proxy object implementation 210 implements extensible interface 214, compiler 230 also generates proxy object functions 1224 for each function declaration 209 in proxy object definitions 204 that do not have a corresponding built-in function 211 in proxy object implementation 210, block 1124. Each implementation of proxy object functions 1224 invokes “invoke” function 616 passing the list of provided parameters and returns the result.
Similarly, compiler 230 generates proxy object callback functions 1226 for each callback declaration 208 in proxy object definitions 204 that have a corresponding built-in callback 212 in proxy object implementation 210, block 1126. Each implementation of callback functions 1226 simply calls the corresponding built-in callback 212 passing provided parameters and returning any results.
Further, for each callback declaration 208 in proxy object definitions 204 that does not have a corresponding built-in callback 212 in proxy object implementation 210, compiler 230 determines whether an appropriate event handler 246 exists in application 240 to handle the call back, block 1128. If an appropriate event handler 246 exists, compiler 230 generates a proxy callback function 1228, which, invokes the appropriate event handler 246 passing in provided parameters and returns any results generated by the event handler, block 1128. If an appropriate event handler does not exist, compiler 230 generates and error, block 1128. In one embodiment, compiler 230 identifies the appropriate event handler and determines its existence by searching for a function in application 240 with a special name formed by appending the name of the associated event to the name of the associated proxy object variable specified in proxy object declaration 222. The names of the appropriate event and proxy object variable are extracted from meta-data 252.
Additional non-essential details of runtime engine 250 may be found in copending U.S. patent application Ser. No. 10/082,807, entitled “ANNOTATION BASED DEVELOPMENT PLATFORM FOR ASYNCHRONOUS WEB SERVICES”, filed on 2/22/02, having at least partial common inventorship with the present application. The '807 specification is hereby fully incorporated by reference.
Upon initialization of the runtime environment, runtime engine 250 waits for requests to execute applications, block 1304. At block 1306, runtime engine 250 loads application 240, whose execution is requested (or creates a new instance of the application if the application has been previously loaded for an earlier execution request). After loading and/or creating an instance of application 220, execution engine 250 “executes” the application 220, or more specifically, transfers execution control to application 220.
As previously described, proxy initialization code 242 instantiates a proxy object for each proxy object declaration 222 and assigns the proxy object to the associated variable specified in proxy object declaration 222, block 1312. Then, proxy initialization code 242 registers all callbacks functions 208 declared in associated proxy object definitions 204 and implemented by proxy object 254 with asynchronous event router 256 as handlers for asynchronous events from external entity 202, block 1314.
Thereafter, execution engine 250 continues to execute application 240,. In the course of execution, if application 240 has a need to interact with external entities, it invokes proxy object functions 1222-1224 using the associated variable declared in proxy object declaration 222, block 1318. As designated by compiler 230, proxy object functions 1222-1224 create an instance of proxy context object 258 associated with the invoked function using a function invocation ID. In one embodiment a separate thread is created for each function invocation and the thread ID is used as the function invocation ID.
Functions 2222 further invoke associated built-in functions 211 of proxy object implementation 210, block 1318. The behavior of built-in functions 211 varies for each proxy object implementation 210 and depends largely on the nature of associated external entity 202. If provided, proxy object functions 1224 invoke the “invoke” function 616 of proxy object implementation 210, block 1318.
In one embodiment, built-in functions send messages to external entity 202 via Internet or messaging protocols and optionally wait for a response. In one embodiment, if a response is received, built-in function 211 returns a representative result, which is in turn returned to proxy invocation code 244 inside application 240 by proxy object function 1222. In one embodiment, built-in functions include a callback location and proxy object instance identifier in messages sent to external entity 202 to facilitate the generation and routing of callback events generated by external entity 202.
Both built-in functions 211 and the “invoke” function 616 of extensible interface 218 may obtain a reference to the current proxy context object 258 for accessing meta-data 252 by calling the global getProxyContext( ) function provided by run-time engine 250. The getProxyContext( ) function finds and returns the appropriate context object based on the invocation ID associated with the current function invocation. In one embodiment, a separate thread is created for each function ID and the current invocation ID is the same as the current thread ID.
Like built-in functions 211, the behavior of invoke function 616 varies for each proxy object implementation 210 and depends largely on the nature of the associated external entity 202. In one embodiment, invoke function 616 accesses meta-data 252 via proxy context object 258 to determine the desired semantics of proxy object functions 1224, then sends appropriate messages to external entity 202, optionally waits for a response and returns a representative result to proxy object function 1224, which in turn returns the result to proxy invocation code 244 in application 240. In one embodiment, invoke function 616 includes a callback location and proxy object instance identifier in messages sent to external entity 202 to facilitate the generation and routing of callback events generated by external entity 202.
Upon receiving a request from application 240, external entity 202 handles the request in an application dependent manner and optionally records a callback address and instance identifier provided by the request. External entity 202 may generate asynchronous events detectable by asynchronous event handler 256 and may specify the recorded callback address and instance identifier to facilitate handling of the event. In one embodiment, external entity 202 provides event notifications to asynchronous event router 256 in the form of messages.
At block 1320, as asynchronous event router 256 detects an event from external entity 202, it checks its list of registered handlers and invokes the designated callback function 1226-1228 of the designated proxy object passing a representation of the event as a set of parameters. In one embodiment, asynchronous event router 256 uses a provided callback location to identify which registered handler and callback function should handle the event. In one embodiment, asynchronous event router 256 uses a provided instance identifier to determine which instance of the identified handler should receive the callback.
As designated by compiler 230, at block 1324, proxy object callbacks 1226 invoke associated built-in callbacks 212 of proxy object implementation 210 passing along any provided parameters, block 1322. The behavior of built-in callbacks 212 varies for each proxy object implementation 210 and depends largely on the nature of associated external entity 202.
In one embodiment built-in callback 212 may invoke an appropriate event handler 246 in application 240 passing provided parameters and optionally wait for a response, block 1322.
Upon receipt of a response to the event for external entity 202, built-in callback 212 returns any returned result to proxy object callback function 1226, which returns it to asynchronous event router 252, which provides the result to external entity 202, block 1324. In one embodiment, the result is returned to the external entity in the form of a representative message.
Also as designated by the compiler, proxy object callbacks 1228 do not have corresponding built-in callbacks 212 and are therefore forwarded directly to appropriate event handlers 246 with any corresponding results returned optionally to external entity 202 via proxy callback function 1228 and asynchronous event router 256, block 1324.
In one embodiment, appropriate event handlers 246 are identified as specially named functions defined in application 240. In one embodiment, this naming convention is determined by appending the name of proxy callback function 1226-1228 corresponding to callback declarations 208 to the name of the proxy object variable declared in proxy object declaration 222 in application code 220.
Managing n-way Relationships
For some applications, there is a need to manage an n-way interaction with an external entity. I.e., a single instance of application 240 may need to simultaneously interact with multiple instances of external entity 202. The required number of instances may vary based on run-time data; therefore, it may not be possible to determine how many proxy object instances will be required when application code 220 is written. For example, an application instance may have a need to disassemble the line items of a purchase order and conduct a concurrent conversation with a separate instance of the external entity for each line item.
In various embodiments, to address this need, the application developer may specify a proxy object factory in proxy object declaration 222 instead of specifying a single proxy object. For these embodiments, compiler 230 automatically generates a “factory class” for each proxy object 254. For example, for a proxy object 254 named MyService, a factory class (not separately shown) by the name MyServiceFactory is automatically generated.
In some or all of these embodiments, the automatically generated proxy object factory may include a create( ) function to enable application 240 to control the creation of new proxy object instances and a destroy( ) function to enable application 240 to control the destruction of previously created proxy object instances. As such, application 240 may create as many instances of the proxy object as required at run-time.
Each automatically generated proxy object factory may be used by a software application to interact with the corresponding external entity in a n-way interaction, substantially as earlier described for the singleton case, referencing
To facilitate proper asynchronous event routing, developer of application code 220 names associated event handlers 224 using the name of the proxy object factory variable instead of a proxy object variable name. In addition, the developer specifies a “proxy object instance” variable as a predetermined parameter, e.g. the first parameter, of each event handler 224. Proxy object 254 will provide the appropriate proxy object instance for each callback event, so application 240 may determine which instance of external entity 202 generated the event and interact with it using the provided proxy object instance.
Example Computer System
Example computer system 1500 may also be used to host the development of application 220 that programmatically interacts with abstracted external entity 202, including its compilation, or execution of application 240 during runtime.
As shown, computer system 1500 includes one or more processors 1502, and system memory 1504. Additionally, computer system 1500 includes mass storage devices 1506 (such as diskette, hard drive, CDROM and so forth), input/output devices 1508 (such as keyboard, cursor control and so forth) and communication interfaces 1510 (such as network interface cards, modems and so forth). The elements are coupled to each other via system bus 1512, which represents one or more buses. In the case of multiple buses, they are bridged by one or more bus bridges (not shown).
Each of these elements performs its conventional functions known in the art.
In particular, system memory 1504 and mass storage 1506 are employed to store a working copy and a permanent copy of the programming instructions implementing the various aspects of the present invention, i.e. the software abstractions of external entities 202, implementations of the software abstractions 210, applications 220, compiler 230, and/or runtime engine 250. System memory 1504 and mass storage 1506 function as a computer or machine readable medium. The permanent copy of the programming instructions may be loaded into mass storage 1506 in the factory, or in the field, through e.g. a distribution medium (not shown) or through communication interface 1510 (from a distribution server (not shown)).
The constitution of these elements 1502-1512 are known, and accordingly will not be further described
Conclusion And Epilogue
Thus, it can be seen from the above descriptions, a novel method and apparatus for simplifying the development, customization and use of software abstractions for interacting with external entities from within a software application has been described. The present invention advantageously assists a software developer to develop software that interacts with a variety of other external entities, without necessarily requiring the software developer to learn a large number of new paradigms or acquire a large number of new techniques.
While the present invention has been described in terms of the above described embodiments, those skilled in the art will recognize that the invention is not limited to the embodiments described. The present invention can be practiced with modification and alteration within the spirit and scope of the appended claims. Thus, the description is to be regarded as illustrative instead of restrictive on the present invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5321841||Jan 29, 1993||Jun 14, 1994||Digital Equipment Corporation||System for determining the rights of object access for a server process by combining them with the rights of the client process|
|US5469562||Jun 26, 1992||Nov 21, 1995||Digital Equipment Corporation||Durable atomic storage update manager|
|US5475817||Nov 30, 1993||Dec 12, 1995||Hewlett-Packard Company||Object oriented distributed computing system processing request to other object model with code mapping by object managers located by manager of object managers|
|US5604860||Oct 27, 1994||Feb 18, 1997||Xerox Corporation||Feature library and stored customized control interfaces|
|US5630131||Nov 14, 1994||May 13, 1997||Object Technology Licensing Corp.||Method and apparatus for importing and exporting archive files for a graphical user interface|
|US5642511||Dec 16, 1994||Jun 24, 1997||International Business Machines Corporation||System and method for providing a visual application builder framework|
|US5724588||Jun 7, 1995||Mar 3, 1998||Microsoft Corporation||Method and system for network marshalling of interface pointers for remote procedure calls|
|US5748975||Jul 6, 1995||May 5, 1998||Sun Microsystems, Inc.||System and method for textual editing of structurally-represented computer programs with on-the-fly typographical display|
|US5801958||Sep 10, 1996||Sep 1, 1998||Lsi Logic Corporation||Method and system for creating and validating low level description of electronic design from higher level, behavior-oriented description, including interactive system for hierarchical display of control and dataflow information|
|US5835769||Sep 19, 1995||Nov 10, 1998||Sun Microsystems, Inc.||Apparatti and computer program products for integrating editors with applications|
|US5836014||May 16, 1994||Nov 10, 1998||Digital Equipment Corporation||Method of constructing a constant-folding mechanism in a multilanguage optimizing compiler|
|US5862327||Jun 10, 1996||Jan 19, 1999||Tactica Corporation||Activity based long-lived transaction system|
|US5867822||Jun 26, 1996||Feb 2, 1999||Sun Microsystems, Inc.||Method and apparatus for management of electronic calendars throughout an enterprise and management of events in a distributed system|
|US5903725||Sep 6, 1996||May 11, 1999||International Business Machines Corporation||Recoverable proxy object in an object oriented environment|
|US5944794||Oct 2, 1995||Aug 31, 1999||Kabushiki Kaisha Toshiba||User identification data management scheme for networking computer systems using wide area network|
|US5950010||Nov 25, 1996||Sep 7, 1999||J.D. Edwards World Source Co.||System and method for customized application package building and installation|
|US5961593||Jan 22, 1997||Oct 5, 1999||Lucent Technologies, Inc.||System and method for providing anonymous personalized browsing by a proxy system in a network|
|US5966535||Dec 7, 1995||Oct 12, 1999||At&T Corporation||Method and apparatus for generating program code for world wide web service applications|
|US6012083||Sep 24, 1996||Jan 4, 2000||Ricoh Company Ltd.||Method and apparatus for document processing using agents to process transactions created based on document content|
|US6016495||Sep 19, 1997||Jan 18, 2000||International Business Machines Corporation||Object-oriented framework mechanism for providing persistent storage|
|US6018730||Dec 22, 1998||Jan 25, 2000||Ac Properties B.V.||System, method and article of manufacture for a simulation engine with a help website and processing engine|
|US6023578||May 9, 1997||Feb 8, 2000||International Business Macines Corporation||Systems, methods and computer program products for generating an object oriented application for an object oriented environment|
|US6023722||Jul 23, 1997||Feb 8, 2000||International Business Machines Corp.||High-availability WWW computer server system with pull-based load balancing using a messaging and queuing unit in front of back-end servers|
|US6028997||May 30, 1997||Feb 22, 2000||International Business Machines Corporation||Method of generating an implementation of reusable parts from containers of a workflow process-model|
|US6029000||Dec 22, 1997||Feb 22, 2000||Texas Instruments Incorporated||Mobile communication system with cross compiler and cross linker|
|US6044217||Oct 23, 1997||Mar 28, 2000||International Business Machines Corporation||Hierarchical metadata store for an integrated development environment|
|US6067548||Jul 16, 1998||May 23, 2000||E Guanxi, Inc.||Dynamic organization model and management computing system and method therefor|
|US6067623||Nov 21, 1997||May 23, 2000||International Business Machines Corp.||System and method for secure web server gateway access using credential transform|
|US6070184||Aug 28, 1997||May 30, 2000||International Business Machines Corporation||Server-side asynchronous form management|
|US6092102||Oct 24, 1997||Jul 18, 2000||University Of Pittsburgh Of The Commonwealth System Of Higher Education||System and method for notifying users about information or events of an enterprise|
|US6119149||Jun 5, 1998||Sep 12, 2000||I2 Technologies, Inc.||System and process allowing collaboration within and between enterprises for optimal decision making|
|US6141686||Jun 23, 1998||Oct 31, 2000||Deterministic Networks, Inc.||Client-side application-classifier gathering network-traffic statistics and application and user names using extensible-service provider plugin for policy-based network control|
|US6141701||Mar 11, 1998||Oct 31, 2000||Whitney; Mark M.||System for, and method of, off-loading network transactions from a mainframe to an intelligent input/output device, including off-loading message queuing facilities|
|US6182155 *||Jan 2, 1998||Jan 30, 2001||International Business Machines Corporation||Uniform access to and interchange between objects employing a plurality of access methods|
|US6212546||Oct 1, 1998||Apr 3, 2001||Unisys Corporation||Providing a modular gateway architecture which isolates attributes of the client and server systems into independent components|
|US6222533||Aug 25, 1997||Apr 24, 2001||I2 Technologies, Inc.||System and process having a universal adapter framework and providing a global user interface and global messaging bus|
|US6226675||Oct 16, 1998||May 1, 2001||Commerce One, Inc.||Participant server which process documents for commerce in trading partner networks|
|US6226690||Jun 14, 1993||May 1, 2001||International Business Machines Corporation||Method and apparatus for utilizing proxy objects to communicate with target objects|
|US6230287||Sep 3, 1998||May 8, 2001||Mitel Corporation||Web based help desk|
|US6230309||Apr 25, 1997||May 8, 2001||Sterling Software, Inc||Method and system for assembling and utilizing components in component object systems|
|US6237135||Sep 11, 1998||May 22, 2001||Borland Software Corporation||Development system with visual design tools for creating and maintaining Java Beans components|
|US6243737||Apr 9, 1999||Jun 5, 2001||Translink Software, Inc.||Method and apparatus for providing direct transaction access to information residing on a host system|
|US6253252 *||Jul 11, 1996||Jun 26, 2001||Andrew Schofield||Method and apparatus for asynchronously calling and implementing objects|
|US6282711||Aug 10, 1999||Aug 28, 2001||Hewlett-Packard Company||Method for more efficiently installing software components from a remote server source|
|US6292932||May 28, 1999||Sep 18, 2001||Unisys Corp.||System and method for converting from one modeling language to another|
|US6311327||Feb 12, 1999||Oct 30, 2001||Applied Microsystems Corp.||Method and apparatus for analyzing software in a language-independent manner|
|US6324681||Oct 1, 1998||Nov 27, 2001||Unisys Corporation||Automated development system for developing applications that interface with both distributed component object model (DCOM) and enterprise server environments|
|US6330569||Jun 30, 1999||Dec 11, 2001||Unisys Corp.||Method for versioning a UML model in a repository in accordance with an updated XML representation of the UML model|
|US6334114||Oct 31, 1997||Dec 25, 2001||Oracle Corporation||Method and apparatus for performing transactions in a stateless web environment which supports a declarative paradigm|
|US6338064||May 14, 1998||Jan 8, 2002||International Business Machines Corporation||Method for enabling a web server running a “closed” native operating system to impersonate a user of a web client to obtain a protected file|
|US6343265||Jul 28, 1998||Jan 29, 2002||International Business Machines Corporation||System and method for mapping a design model to a common repository with context preservation|
|US6345382 *||Feb 12, 1998||Feb 5, 2002||International Business Machines Corporation||Run-time customization in object-oriented design|
|US6349408||Jun 30, 1998||Feb 19, 2002||Sun Microsystems, Inc.||Techniques for implementing a framework for extensible applications|
|US6353923||Jan 30, 1998||Mar 5, 2002||Microsoft Corporation||Active debugging environment for debugging mixed-language scripting code|
|US6360358||Mar 11, 1999||Mar 19, 2002||Microsoft Corporation||Maintenance of code knowledge for up-to-date access thereof|
|US6367068||Nov 13, 1998||Apr 2, 2002||Microsoft Corporation||Dynamic parsing|
|US6377939||May 4, 1999||Apr 23, 2002||Metratech||Pipelined method and apparatus for processing communication metering data|
|US6385661||Oct 19, 1998||May 7, 2002||Recursion Software, Inc.||System and method for dynamic generation of remote proxies|
|US6393605||Nov 17, 1999||May 21, 2002||Siebel Systems, Inc.||Apparatus and system for efficient delivery and deployment of an application|
|US6408311||Jun 30, 1999||Jun 18, 2002||Unisys Corp.||Method for identifying UML objects in a repository with objects in XML content|
|US6411698||Oct 13, 1998||Jun 25, 2002||Mci Communication Corporation||System and method for communication between a telephone data repository and downstream data processing applications|
|US6445711||Apr 21, 2000||Sep 3, 2002||Sony Corporation||Method of and apparatus for implementing and sending an asynchronous control mechanism packet used to control bridge devices within a network of IEEE STD 1394 serial buses|
|US6470364||Feb 23, 1999||Oct 22, 2002||Sun Microsystems, Inc.||Method and apparatus for generating text components|
|US6516322||Apr 28, 2000||Feb 4, 2003||Microsoft Corporation||XML-based representation of mobile process calculi|
|US6549949||Aug 31, 1999||Apr 15, 2003||Accenture Llp||Fixed format stream in a communication services patterns environment|
|US6560769||Sep 28, 2000||May 6, 2003||Unisys Corporation||Computer-implemented method for generating a UML representation from JAVA source code|
|US6567738||Jan 30, 2001||May 20, 2003||Ford Global Technologies, Llc||Fueling control system|
|US6578191||May 17, 1999||Jun 10, 2003||International Business Machines Corporation||Method and apparatus for dynamic generation of adapters|
|US6584454||Dec 31, 1999||Jun 24, 2003||Ge Medical Technology Services, Inc.||Method and apparatus for community management in remote system servicing|
|US6594693||Jan 22, 1999||Jul 15, 2003||Nitin A. Borwankar||Method and apparatus for a structured, synchronized conversation using electronic messages over a computer network|
|US6594700||Jun 14, 1999||Jul 15, 2003||International Business Machines Corporation||System and method for implementing a universal service broker interchange mechanism|
|US6601113||Jun 8, 1998||Jul 29, 2003||Telefonaktiebolaget Lm Ericsson (Publ)||System platform for a communication system|
|US6604198||May 3, 2002||Aug 5, 2003||Microsoft Corporation||Automatic object caller chain with declarative impersonation and transitive trust|
|US6609115||Dec 30, 1999||Aug 19, 2003||Ge Medical Systems||Method and apparatus for limited online access to restricted documentation|
|US6615258||Sep 24, 1998||Sep 2, 2003||Worldcom, Inc.||Integrated customer interface for web based data management|
|US6636491||Jan 11, 1999||Oct 21, 2003||Nokia Corporation||Access control method for a mobile communications system|
|US6637020||Dec 3, 1998||Oct 21, 2003||International Business Machines Corporation||Creating applications within data processing systems by combining program components dynamically|
|US6643652||Jan 12, 2001||Nov 4, 2003||Saba Software, Inc.||Method and apparatus for managing data exchange among systems in a network|
|US6654932||Oct 29, 1999||Nov 25, 2003||International Business Machines Corporation||Validating data within container objects handled by view controllers|
|US6678518||Dec 9, 1999||Jan 13, 2004||Nokia Corporation||Dynamic content filter in a gateway|
|US6684388||Aug 22, 2000||Jan 27, 2004||International Business Machines Corporation||Method for generating platform independent, language specific computer code|
|US6687702||Sep 25, 2001||Feb 3, 2004||Sybass, Inc.||Methodology providing high-speed shared memory access between database middle tier and database server|
|US6687848||Oct 30, 2000||Feb 3, 2004||Sun Microsystems, Inc.||Techniques for preventing information loss in a business to business message in an enterprise computer system|
|US6721740||Jun 5, 1998||Apr 13, 2004||Sun Microsystems, Inc.||Method and apparatus of performing active update notification|
|US6721779||Jul 7, 2000||Apr 13, 2004||Softwired Ag||Messaging proxy system|
|US6732237||Aug 29, 2000||May 4, 2004||Oracle International Corporation||Multi-tier caching system|
|US6735771||Mar 12, 1999||May 11, 2004||Perot Systems Corporation||System and method for delivering web services using common object request broker architecture|
|US6748420||Oct 11, 2000||Jun 8, 2004||Cisco Technology, Inc.||Methods and apparatus for providing shared access to an application|
|US6754884||Jul 2, 2001||Jun 22, 2004||Bea Systems, Inc.||Programming language extensions for processing XML objects and related applications|
|US6757689||Sep 7, 2001||Jun 29, 2004||Hewlett-Packard Development Company, L.P.||Enabling a zero latency enterprise|
|US6789054||Apr 25, 1999||Sep 7, 2004||Mahmoud A. Makhlouf||Geometric display tools and methods for the visual specification, design automation, and control of adaptive real systems|
|US6795967||Jan 26, 1999||Sep 21, 2004||Microsoft Corporation||Changing user identities without closing applications|
|US6799718||Jul 10, 2002||Oct 5, 2004||Borland Software Corp.||Development assistance for mixed-language sources|
|US6802000||Oct 28, 1999||Oct 5, 2004||Xerox Corporation||System for authenticating access to online content referenced in hardcopy documents|
|US6804686||Sep 10, 2002||Oct 12, 2004||Borland Software Corporation||System and methodology for providing fixed UML layout for an object oriented class browser|
|US6823495||Sep 14, 2000||Nov 23, 2004||Microsoft Corporation||Mapping tool graphical user interface|
|US6832238||May 24, 2000||Dec 14, 2004||Sun Microsystems, Inc.||Local transaction management|
|US6836883||Jun 21, 2000||Dec 28, 2004||Microsoft Corporation||Method and system for compiling multiple languages|
|US6847981||Feb 7, 2003||Jan 25, 2005||Electronics And Telecommunications Research Institute||System and method for generating EJB components from reusable business logics in servlet program|
|US6850979||Aug 31, 2000||Feb 1, 2005||Sun Microsystems, Inc.||Message gates in a distributed computing environment|
|US6859180||Sep 15, 2003||Feb 22, 2005||The United States Of America As Represented By The Secretary Of The Navy||Gravity-actuated submarine antenna|
|US6874143||Jun 21, 2000||Mar 29, 2005||Microsoft Corporation||Architectures for and methods of providing network-based software extensions|
|US6877163||Jun 14, 1999||Apr 5, 2005||Sun Microsystems, Inc.||Method and system for dynamic proxy classes|
|US6889244||Oct 31, 2000||May 3, 2005||Hewlett-Packard Development Company, L.P.||Method and apparatus for passing messages using a fault tolerant storage system|
|US6895444||Sep 15, 2000||May 17, 2005||Motorola, Inc.||Service framework with local proxy for representing remote services|
|US6901588||Apr 17, 2000||May 31, 2005||Codemesh, Inc.||Sharing components between programming languages by use of polymorphic proxy|
|US6915519||Jul 12, 2001||Jul 5, 2005||International Business Machines Corporation||Pluggable JMS providers in a J2EE server|
|US6918084||Aug 31, 2000||Jul 12, 2005||Sun Microsystems, Inc.||Spawning new repository spaces using information provided in advertisement schema messages|
|US6918088||Nov 5, 2001||Jul 12, 2005||Sun Microsystems, Inc.||Service portal with application framework for facilitating application and feature development|
|US6922827||Feb 22, 2002||Jul 26, 2005||Bea Systems, Inc.||Iterative software development environment with prioritized build rules|
|US6950872||Dec 19, 2001||Sep 27, 2005||Sun Microsystems, Inc.||Methods and systems for facilitating message exchange between networked computing entities|
|US6959307||Nov 3, 2003||Oct 25, 2005||International Business Machines Corporation||Process and system for a client object to perform a remote method invocation of a method in a server object|
|US6963914||Jun 9, 1999||Nov 8, 2005||Lucent Technologies Inc.||Method and apparatus for retrieving a network file using a logical reference|
|US6971096||May 19, 2000||Nov 29, 2005||Sun Microsystems, Inc.||Transaction data structure for process communications among network-distributed applications|
|US6976086||Jul 18, 2001||Dec 13, 2005||Siemens Business Services, Llc||Systems and methods to facilitate a distribution of information via a dynamically loadable component|
|US6993774 *||Nov 30, 1999||Jan 31, 2006||Recursion Software, Inc.||System and method for remote enabling classes without interfaces|
|US7000219||Nov 5, 2001||Feb 14, 2006||Wilde Technologies Limited||Software development process|
|US7017146||Nov 1, 2001||Mar 21, 2006||Massachusetts Institute Of Technology||Computer system and computer implemented process for representing software system descriptions and for generating executable computer programs and computer system configurations from software system descriptions|
|US7043722||Jul 31, 2002||May 9, 2006||Bea Systems, Inc.||Mixed language expression loading and execution methods and apparatuses|
|US7051072||Jul 16, 2001||May 23, 2006||Bea Systems, Inc.||Method for providing real-time conversations among business partners|
|US7051316||Apr 20, 2001||May 23, 2006||Borland Software Corporation||Distributed computing component system with diagrammatic graphical representation of code with separate delineated display area by type|
|US7054858||Aug 1, 2001||May 30, 2006||Oic Acquisition Corporation||System and method for retrieval of objects from object to relational mappings|
|US7062718||Apr 1, 2002||Jun 13, 2006||National Instruments Corporation||Configuration diagram which graphically displays program relationship|
|US7065771 *||Jun 28, 2001||Jun 20, 2006||Microsoft Corporation||Distributed types and proxy refinement|
|US7069507||Sep 29, 2000||Jun 27, 2006||Microsoft Corporation||Event routing model for an extensible editor|
|US7072934||Jan 12, 2001||Jul 4, 2006||Saba Software, Inc.||Method and apparatus for a business applications server management system platform|
|US7073167||Apr 17, 2001||Jul 4, 2006||Fujitsu Limited||Compiler system compiling method, and storage medium for storing compiling program|
|US7076772||Feb 19, 2004||Jul 11, 2006||Bea Systems, Inc.||System and method for multi-language extensible compiler framework|
|US7096422||Feb 28, 2003||Aug 22, 2006||Microsoft Corporation||Markup language visual mapping|
|US7107578||May 10, 2002||Sep 12, 2006||Oracle International Corporation||Techniques for debugging computer programs involving multiple programming languages|
|US7111243||Dec 28, 2001||Sep 19, 2006||Oracle International Corporation||Customization of tab-order functionality in internet applications|
|US7117504||Jul 10, 2001||Oct 3, 2006||Microsoft Corporation||Application program interface that enables communication for a network software platform|
|US7127704||Aug 27, 2001||Oct 24, 2006||Sun Microsystems, Inc.||Interactive software engineering tool with support for embedded lexical contexts|
|US7143186||Feb 16, 2001||Nov 28, 2006||Bea Systems, Inc.||Pluggable hub system for enterprise wide electronic collaboration|
|US7146422||May 1, 2000||Dec 5, 2006||Intel Corporation||Method and apparatus for validating documents based on a validation template|
|US7155705||Nov 26, 2001||Dec 26, 2006||Cisco Technology, Inc.||Techniques for binding an application with a data exchange format based on tags in comments|
|US7165041||May 27, 1999||Jan 16, 2007||Accenture, Llp||Web-based architecture sales tool|
|US7181731||Sep 4, 2001||Feb 20, 2007||Op40, Inc.||Method, system, and structure for distributing and executing software and data on different network and computer devices, platforms, and environments|
|US7184967||Mar 6, 2001||Feb 27, 2007||Microsoft Corporation||System and method utilizing a graphical user interface of a business process workflow scheduling program|
|US7240331||Jan 16, 2002||Jul 3, 2007||Xerox Corporation||Bi-valuation of programming statements|
|US7260599||Mar 7, 2003||Aug 21, 2007||Hyperspace Communications, Inc.||Supporting the exchange of data by distributed applications|
|US20010052111||Mar 8, 2001||Dec 13, 2001||International Business Machines Corporation||Management of application programming interface interoperability|
|US20020004848||Mar 23, 2001||Jan 10, 2002||Krishna Sudarshan||System and method of providing an asynchronous interface between a client system and an enterprise javabeans-enabled server|
|US20020010781||Jan 2, 2001||Jan 24, 2002||Tuatini Jeffrey Taihana||Shared service messaging models|
|US20020010803||May 24, 2001||Jan 24, 2002||Oberstein Brien M.||Method, system and apparatus for establishing, monitoring, and managing connectivity for communication among heterogeneous systems|
|US20020016759||Dec 6, 2000||Feb 7, 2002||Macready William G.||Method and system for discovery of trades between parties|
|US20020035604||Aug 29, 2001||Mar 21, 2002||Cohen Andrew R.||Methods for performing client-hosted application sessions in distributed processing systems|
|US20020049603||Jan 12, 2001||Apr 25, 2002||Gaurav Mehra||Method and apparatus for a business applications server|
|US20020073080||Jan 12, 2001||Jun 13, 2002||Lipkin Daniel S.||Method and apparatus for an information server|
|US20020073396||Jun 1, 2001||Jun 13, 2002||John Crupi||Method and apparatus for developing enterprise applications using design patterns|
|US20020078365||Dec 15, 2000||Jun 20, 2002||International Business Machines Corporation||Method for securely enabling an application to impersonate another user in an external authorization manager|
|US20020083075||Dec 5, 2001||Jun 27, 2002||Tony Brummel||System and method for a seamless user interface for an integrated electronic health care information system|
|US20020111922||Nov 5, 2001||Aug 15, 2002||Terry Bernard Young||Electronic markets business interchange system and method|
|US20020120685||Apr 10, 2002||Aug 29, 2002||Alok Srivastava||System for dynamically invoking remote network services using service descriptions stored in a service registry|
|US20020143960||Dec 4, 2000||Oct 3, 2002||Erez Goren||Virtual network generation system and method|
|US20020152106||Feb 5, 2002||Oct 17, 2002||Paul Stoxen||Electronic acquisition system and method|
|US20020161826||Jan 25, 2001||Oct 31, 2002||Carlos Arteaga||System and method for remote communication transactions|
|US20020165936||Jan 25, 2002||Nov 7, 2002||Victor Alston||Dynamically branded web sites|
|US20020169644||Mar 29, 2002||Nov 14, 2002||Greene William S.||Method and system for implementing a management operations center in a global ecosystem of interrelated services|
|US20020174178||Aug 29, 2001||Nov 21, 2002||Schneider Automation||Communication system for automation equipment based on the WSDL language|
|US20020174241||May 18, 2001||Nov 21, 2002||Gabe Beged-Dov||Trusted internet clipboard|
|US20020174262||Feb 7, 2002||Nov 21, 2002||Apple Computer, Inc.||Method and apparatus for dynamically brokering object messages among object models|
|US20020184610||Jan 18, 2002||Dec 5, 2002||Kelvin Chong||System and method for building multi-modal and multi-channel applications|
|US20020188486||Dec 19, 2001||Dec 12, 2002||World Chain, Inc.||Supply chain management|
|US20020194244||Jun 1, 2001||Dec 19, 2002||Joan Raventos||System and method for enabling transaction-based service utilizing non-transactional resources|
|US20020194267||Jun 22, 2001||Dec 19, 2002||Daniel Flesner||Portal server that provides modification of user interfaces for access to computer networks|
|US20020194495||Jun 14, 2002||Dec 19, 2002||Gladstone Philip J.S.||Stateful distributed event processing and adaptive security|
|US20030004746||Apr 24, 2002||Jan 2, 2003||Ali Kheirolomoom||Scenario based creation and device agnostic deployment of discrete and networked business services using process-centric assembly and visual configuration of web service components|
|US20030005181||Feb 22, 2002||Jan 2, 2003||David Bau||Annotation based development platform for asynchronous web services|
|US20030014439||Jun 20, 2001||Jan 16, 2003||International Business Machines Corporation||Defining a markup language representation for state chart data|
|US20030018661||Jul 18, 2002||Jan 23, 2003||Darugar Parand Tony||XML smart mapping system and method|
|US20030018832||Jan 18, 2002||Jan 23, 2003||Venkat Amirisetty||Metadata-aware enterprise application integration framework for application server environment|
|US20030018963||Oct 25, 2001||Jan 23, 2003||International Business Machines Corporation||Installation of a data processing solution|
|US20030023957||Feb 22, 2002||Jan 30, 2003||David Bau||Annotation based development platform for stateful web services|
|US20030028579||Apr 1, 2002||Feb 6, 2003||Kulkarni Vinay Vasant||Process for component-based application development|
|US20030041198||Aug 23, 2001||Feb 27, 2003||International Business Machines Corporation||Authorization model for administration|
|US20030043191||Aug 17, 2001||Mar 6, 2003||David Tinsley||Systems and methods for displaying a graphical user interface|
|US20030046266||Jan 17, 2002||Mar 6, 2003||Ward Mullins||System, method and software for creating or maintaining distributed transparent persistence of complex data objects and their data relationships|
|US20030046591||Aug 29, 2001||Mar 6, 2003||Nader Asghari-Kamrani||Centralized identification and authentication system and method|
|US20030051066||Sep 4, 2001||Mar 13, 2003||Pace Charles P.||Method and system for deploying an asset over a multi-tiered network|
|US20030055868||Sep 19, 2001||Mar 20, 2003||International Business Machines Corporation||Building distributed software services as aggregations of other services|
|US20030055878||Sep 19, 2001||Mar 20, 2003||International Business Machines Corporation||Programmatic management of software resources in a content framework environment|
|US20030074217||Oct 9, 2002||Apr 17, 2003||International Business Machines Corporation||Resource adapter and integrated development environment|
|US20030079029||Aug 5, 2002||Apr 24, 2003||Sandilya Garimella||Single system user identity|
|US20030084203||Jan 30, 2002||May 1, 2003||Jun Yoshida||Program control method, computer system, control program, and storage medium storing the control program|
|US20030093471 *||Oct 15, 2002||May 15, 2003||Mitch Upton||System and method using asynchronous messaging for application integration|
|US20030110117||Jan 23, 2003||Jun 12, 2003||Saidenberg Steven D.||System and method for providing integrated applications availability in a networked computer system|
|US20030110312 *||Jul 31, 2001||Jun 12, 2003||Mesut Gunduc||System and method for software component plug-in framework|
|US20030110446||Dec 10, 2001||Jun 12, 2003||Sun Microsystems, Inc.||Object class for facilitating conversion between Java and XML|
|US20030126136||Jun 24, 2002||Jul 3, 2003||Nosa Omoigui||System and method for knowledge retrieval, management, delivery and presentation|
|US20030149791||Feb 5, 2002||Aug 7, 2003||International Business Machines Corporation||System and method for routing data by a server|
|US20030167358||Aug 30, 2002||Sep 4, 2003||Marvin Kyle W.||Methods and apparatus for building, customizing and using software abstractions of external entities|
|US20030196168||Apr 10, 2002||Oct 16, 2003||Koninklijke Philips Electronics N.V.||Method and apparatus for modeling extensible markup language (XML) applications using the unified modeling language (UML)|
|US20040019645||Jul 26, 2002||Jan 29, 2004||International Business Machines Corporation||Interactive filtering electronic messages received from a publication/subscription service|
|US20040040011||Nov 9, 2001||Feb 26, 2004||Adam Bosworth||Multi-language execution method|
|US20040078373||May 14, 2003||Apr 22, 2004||Adel Ghoneimy||Workflow system and method|
|US20040133660||Oct 9, 2003||Jul 8, 2004||International Business Machines Corporation||Dynamic portal assembly|
|US20040139018||Jul 13, 2001||Jul 15, 2004||Anderson Ian R||Card system|
|US20040148336||Mar 28, 2003||Jul 29, 2004||Hubbard Edward A||Massively distributed processing system architecture, scheduling, unique device identification and associated methods|
|US20040204976||May 4, 2004||Oct 14, 2004||Hiroaki Oyama||Electronic commerce system for trading operation|
|US20040216086||Jan 22, 2004||Oct 28, 2004||David Bau||XML types in Java|
|US20040225995||Feb 17, 2004||Nov 11, 2004||Kyle Marvin||Reusable software controls|
|US20040260715||Jun 20, 2003||Dec 23, 2004||Mongeon Brad A.||Object mapping across multiple different data stores|
|US20050050068||Aug 29, 2003||Mar 3, 2005||Alexander Vaschillo||Mapping architecture for arbitrary data models|
|US20050278585||Jul 2, 2002||Dec 15, 2005||Microsoft Corporation||Floating debugger|
|US20060206856||Dec 11, 2003||Sep 14, 2006||Timothy Breeden||System and method for software application development in a portal environment|
|US20060234678||Mar 8, 2006||Oct 19, 2006||Bluesocket, Inc.||Method and system for managing data traffic in wireless networks|
|US20070038500||Oct 20, 2006||Feb 15, 2007||ACL International, Inc.,||Ontology-driven information system|
|CA2248634A1||Sep 24, 1998||Mar 24, 2000||Ibm Canada||Common connector framework|
|WO2000029924A||Title not available|
|WO2001090884A2||May 17, 2001||Nov 29, 2001||Sun Microsystems Inc||Modular and portable deployment of a resource adapter in an application server|
|1||Allamaraju, et al., "Professional Java Server Programming J2EE 1.3 Edition", WROX, XP002442953, ISBN: 1-861005-37-7, Sep. 2001, p. 1009-p. 1057.|
|2||Alonso, G., et al., "Advanced Transaction Models in Workflow Contexts", Proceedings of the 12th International Conference on Data Engineering, Feb. 1996, retrieved from: , 8 pages.|
|3||Alonso, G., et al., "Advanced Transaction Models in Workflow Contexts", Proceedings of the 12th International Conference on Data Engineering, Feb. 1996, retrieved from: <http://citeseer.ist.psu.edu/alonso96advanced.html>, 8 pages.|
|4||Altova, "XML-to-XML Mapping", Altova MapForce®, 2007, pp. 1-3.|
|5||BEA, "Transforming Data Using Xquery Mapper", BEA AquaLogic Service Bus. 2.0 Documentation, 2006, pp. 1-19.|
|6||Blake, M. Brian, Rule-Driven Coordination Agents: A Self-Configurable Agent Architecture for Distributed Control, Department of Computer Science, Georgetown University, Washington, DC, © 2001 IEEE, Mar. 2001, pp. 271-277 (7 pages).|
|7||Bogunovic, N., "A Programming Model for Composing Data-Flow Collaborative Applications" , R. Boskovic Institute, Zagreb, 10000, Croatia, IEEE, Mar. 1999, 7 pages, retrieved Apr. 10, 2007.|
|8||Chen, et al., "eCo Architecture for Electronic Commerce Interoperabillity", CommerceNet Framework Project, Jun. 29, 1999, © 1999 by CommerceNet, Inc., pp. 1-107.|
|9||Dahalin, et al., "Workflow Interoperability Using Extensible Markup Language (XML)",School of Information Technology, Universiti Utara Malaysia, Sintok Kedah, Malaysia, Jul. 2002, © 2002 IEEE, pp. 513-516 (4 pages).|
|10||Duvos, Enrique, et al., "An Infrastucture for the Dynamic Distribution of Web Applications and Services", Department of Computer Science, Boston University, Boston MA, Dec. 2000, pp. 4-12 (22 pages).|
|11||Embury, S.M., et al., "Assisting the Comprehension of Legacy Transactions", Proceedings of the Eighth Working Conference on Reverse Engineering, Oct. 2-5, 2001, © 2001 IEEE, pp. 345-354.|
|12||Gamma, Erich, et al., "Design Patterns: Elements of Reusable Object-Oriented Software", Copyright 1995 by Addison-Wesley Publishing Company, 13 pages.|
|13||Hewlett-Packard, "HP Application Server", Technical Guide Version 8.0, 1999-2001 (245 pages).|
|14||International Search Report, PCT/US04/05427, mailed Feb. 10, 2005, 12 pages.|
|15||International Search Report, PCT/US04/05479, mailed Dec. 3, 2004, 8 pages.|
|16||International Search Report, PCT/US04/05488, mailed Mar. 1, 2005, 3 pages.|
|17||International Search Report, PCT/US04/05622, mailed Mar. 15, 2005, 4 pages.|
|18||Jamper, "Jamper-Java XML Mapper", Sourceforge.Net®, Jun. 6, 2007, pp. 1-4; http://jamper.sourceforge.net/xxxxxxxxxxxx.|
|19||JAVA Debug Interface-definition, retrieved from <URL http://java.sun.com/j2se/1.4.2/docs/guide/jpda/jdi/overview-summary.html on Feb. 21, 2007, pp. 1-3.|
|20||Kilgore, R.A., "Multi-Language, Open-Source Modeling Using the Microsoft.Net Architecture", Proceedings of the Winter Simulation Conference, Dec. 8-11, 2002, © 2006, IEEE, pp. 629-633.|
|21||Kunisetty, Sunil, "Workflow Modeling and Simulation Using an Extensible Object-Oriented Knowledge Base Management System", Database Research and Development Center, University of Florida, Gainsville, FL, CiteSeer, 1996, pp. 1-60.|
|22||Lauer, Christopher, "Introducing Microsoft DotNet", Techmetrix Research, Jul. 2, 2002; http://web.archive.org/web/20020702162429/http://www.freevbcode.com/ShowCode.asp?ID=2171, Oct. 22, 2004, 10 pages.|
|23||Liebmann, Erich et al., "Adaptive Data Dissemination and Caching for Edge Service Architectures Built with the J2EE", Distributed Systems Group, Information Systems Institute, Vienna University of Technology, Vienna, Austria, Mar. 2004, © 2004 ACM Press, 2004 ACM Symposium on Applied Computing, pp. 1717-1724 (8 pages).|
|24||Mariucci, Marcello, "Enterprise Application Server Development Environment", Overview, University Stuttgart, Stuttgart, DE, Oct. 10, 2000, pp. 1-30.|
|25||Mays, E., et al., "A Persistent Store for Large Shared Knowledge Bases", IEEE Transactions on Knowledge and Data Engineering, Mar. 1991, vol. 3, Issue 1, © 1991 , pp. 33-41.|
|26||Microsoft, "Microsoft.net Framework", Microsoft Corporation, 2001, 54 pages.|
|27||Mohan, C., et al., "ARIES: A Transaction Recovery Method Supporting Fine-Granularity Locking and Partial Rollbacks Using Write-Ahead Logging", © 1992, ACM Transactions on Database Systems, vol. 17, No. 1, Mar. 1992, pp. 94-162.|
|28||Ort et al., "Java Architecture for XML Binding (JAXB)", Sun Microsystems, Inc., Mar. 2003, retrieved from , pp. 1-14.|
|29||Ort et al., "Java Architecture for XML Binding (JAXB)", Sun Microsystems, Inc., Mar. 2003, retrieved from <http://java.sun.com/developer/technical/articles/WebServices/jaxb>, pp. 1-14.|
|30||Paul, Laura Gibbons, "RosettaNet: Teaching Businesses to Work Together", Oct. 1, 1999; http//www.developer.com/xml/print.php/616641, Jan. 4, 2005, 4 pages.|
|31||Plaindoux, D., "XML Transducers in Java", Proceedings of the 11th International World Wide Web Conference, Sheraton Waikiki Hotel, Honolulu, HI, USA, May 2002, retrieved from: , 6 pages.|
|32||Plaindoux, D., "XML Transducers in Java", Proceedings of the 11th International World Wide Web Conference, Sheraton Waikiki Hotel, Honolulu, HI, USA, May 2002, retrieved from: <http://www2002.org/CDROM/poster/132/index.html>, 6 pages.|
|33||Roman, Ed, et al., "The Technical Benefits of EJB and J2EE Technologies Over COM+ and Windows DNA", the Middleware Company, Dec. 1999, © 1999, The Middleware Company, pp. 3-5, fig. 1 (24 pages).|
|34||Shannon, "Java(TM) 2 Platform Enterprise Edition Specification, v1.3", Sun Microsystems, Inc., Proposed Final Draft Oct. 20, 2000, Chapters 1-11, 170 pages.|
|35||Shannon, "Java™ 2 Platform Enterprise Edition Specification, v1.3", Sun Microsystems, Inc., Proposed Final Draft Oct. 20, 2000, Chapters 1-11, 170 pages.|
|36||Silva, Antonio Rito, et al., "Distributed Proxy: A Design Pattern for Distributed Object Communication", INESC/IST Technical University of Lisbon, Rua Alves Redol No. 9, 1000 Lisboa, Portual, Sep. 1997, pp. 1-8.|
|37||Smith, M., et al., "Marching Towards a Software Reuse Future", ACM Ada Letters, vol. XIV, No. 6, Nov./Dec. 1994, pp. 62-72, retrieved Apr. 10, 2007.|
|38||Sosnoski, "XML and Java Technologies: Data Binding, Part 1: Code Generation Approaches-JAXB and More", IBM, Jan. 1, 2003, pp. 1-11; http://www-128.ibm.com/developerworks/library/x-databdopt/index.html.|
|39||Sosnoski, "XML and Java Technologies: Data Binding, Part 1: Code Generation Approaches—JAXB and More", IBM, Jan. 1, 2003, pp. 1-11; http://www-128.ibm.com/developerworks/library/x-databdopt/index.html.|
|40||Stylus Studio, "Xquery Mapper", Stylus Studio®, Jun. 5, 2007, pp. 1-6; http://www.stylusstudio.com/xquery-mapper.html.|
|41||Stylus Studio, "Xquery Mapper", Stylus Studio®, Jun. 5, 2007, pp. 1-6; http://www.stylusstudio.com/xquery—mapper.html.|
|42||Sun Microsystems, "Iplanet Application Server 6.0 White Paper", Technical Reference Guide, May 25, 2000, 106 pages.|
|43||Sun Microsystems: "J2EE(TM) Connector Architecture 1.0", XP-002442954, Aug. 2001; retrieved from: , 188 pages.|
|44||Sun Microsystems: "J2EE™ Connector Architecture 1.0", XP-002442954, Aug. 2001; retrieved from: <http://java.sun.com/j2ee/connector/download.html>, 188 pages.|
|45||Sung, S.Y., et al., "A Multimedia Authoring Tool for the Internet", © 1997 IEEE, pp. 304-308, retrieved Apr. 10, 2007.|
|46||Supplementary European Search Report, EP02784131.1-1243-PCT/US/0233098, dated Aug. 8, 2007, 4 pages.|
|47||Supplementary European Search Report, EP02784131.1—1243—PCT/US/0233098, dated Aug. 8, 2007, 4 pages.|
|48||Tang, C., et al., "Integrating Remote Invocation and Distributed Shared State", Proceedings of the 18th International Parallel and Distributed Processing Symposium, (IPDPS '04), © 2004 IEEE, Apr. 26-30, 2004, 10 pages.|
|49||Van Der Allst, et al., Verification of XRL: An XML-Based Workflow Language, Faculty of Technology and Management, Eindhoven University of Technology, Eindhoven, The Netherlands, Computer Supported Cooperative Work in Design, The Sixth International Conference, IEEE, Jul. 2001, pp. 427-432 (6 pages).|
|50||Van Der Alst, WMP, et al., "XML Based Schema Definition for Support of Inter-organizational Workflow", University of Colorado and University of Eindhoven report, 2000, retrieved from: , 39 pages.|
|51||Van Der Alst, WMP, et al., "XML Based Schema Definition for Support of Inter-organizational Workflow", University of Colorado and University of Eindhoven report, 2000, retrieved from: <http://citeseer.ist.psu.edu/vanderaalst00xml.html>, 39 pages.|
|52||Wikipedia (redirected from JAXB), "Java Architecture for XML Binding (JAXB)", Oct. 12, 2007, pp. 1-3.|
|53||Willink, "Meta-Compilation for C ++", University of Surrey, Jan. 4, 2000, 379 pages.|
|U.S. Classification||719/320, 726/12, 719/330|
|International Classification||G06F3/00, G06F9/45, G06F9/46, G06F15/16|
|Cooperative Classification||G06F2209/461, G06F9/542, G06F9/541, G06F9/465|
|European Classification||G06F9/46M, G06F9/54B, G06F9/54A|
|Oct 1, 2010||AS||Assignment|
Owner name: ORACLE INTERNATIONAL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BEA SYSTEMS, INC.;REEL/FRAME:025084/0470
Effective date: 20100929
|Feb 18, 2015||FPAY||Fee payment|
Year of fee payment: 4