US2010211961A1PendingUtilityA1

Data bus between middleware layers

Assignee: IONA TECHNOLOGIES LTDPriority: Jan 19, 2005Filed: Apr 28, 2010Published: Aug 19, 2010
Est. expiryJan 19, 2025(expired)· nominal 20-yr term from priority
H04L 67/63H04L 69/18
35
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A system/method is introduced that integrates middleware components without canonicalization of data at runtime, where the system/method receives inputs identifying at least a first and second middleware to be made interoperative (via a communication path between an in-port corresponding to the first middleware and an out-port corresponding to the second middleware), receives an incoming message at the in-port, handles the received message as a plurality of parts and where, for each part, a data-object is created based on an identified type factory, with the in-port populating the data-object with values from corresponding part of the message and passing the populated data object from the in-port corresponding to the first middleware to the out-port corresponding to the second middleware.

Claims

exact text as granted — not AI-modified
1 . A method to integrate a plurality of middleware without canonicalization of data at runtime, said method implemented using in-ports and out-ports, each in-port facilitating communication between a specific middleware and a first interface and each out-port facilitating communication between another specific middleware and said first interface, said method comprising the steps of:
 (a) receiving inputs identifying at least a first and second middleware to be made interoperative, said interoperation implemented via at least one communication path between an in-port corresponding to said first middleware and an out-port corresponding to said second middleware;   (b) receiving an incoming message at said in-port;   (c) handling said received message as a plurality of parts and, for each part:
 identifying an associated data type; 
 identifying a type factory for said identified data type; 
 creating at least one data-object based on said identified type factory; 
 passing said created data-object to said in-port; 
 said in-port populating said data-object with values from corresponding part of said message; 
 passing said populated data object from the in-port corresponding to said first middleware to said out-port corresponding to the second middleware; and 
   (d) iteratively repeating step (c) for each part of said message.   
   
   
       2 . The method of  claim 1 , wherein said method further comprises the step of creating said type factory according to said associated data type. 
   
   
       3 . A method to integrate a plurality of middleware without canonicalization of data at runtime, said method implemented using in-ports and out-ports, each in-port facilitating communication between a specific middleware and a first interface and each out-port facilitating communication between another specific middleware and said first interface, said method comprising the steps of:
 (a) receiving inputs identifying at least a first and second middleware to be made interoperative, said interoperation implemented via at least one communication path between an in-port corresponding to said first middleware and an out-port corresponding to said second middleware;   (b) receiving an incoming message at said in-port;   (c) handling said received message as a plurality of parts and, for each part:
 identifying an associated data type; 
 identifying a type factory for said identified data type; 
 creating at least one data-object based on said identified type factory; 
 passing said created data-object to said in-port; and 
 said in-port populating said data-object with values from corresponding part of said message; 
   (d) iteratively repeating step (c) for each part of said message and populating a plurality of data-objects; and   (e) passing said plurality of populated data objects from the in-port corresponding to said first middleware to said out-port corresponding to the second middleware.   
   
   
       4 . The method of  claim 3 , wherein said method further comprises the step of creating said type factory according to said associated data type. 
   
   
       5 . An article of manufacture comprising computer storage medium having computer readable program code that is executable by a computer to implement a method to integrate a plurality of middleware without canonicalization of data at runtime, said method implemented using in-ports and out-ports, each in-port facilitating communication between a specific middleware and a first interface and each out-port facilitating communication between another specific middleware and said first interface, said medium comprising:
 (a) computer readable program code receiving inputs identifying at least a first and second middleware to be made interoperative, said interoperation implemented via at least one communication path between an in-port corresponding to said first middleware and an out-port corresponding to said second middleware;   (b) computer readable program code receiving an incoming message at said in-port;   (c) computer readable program code handling said received message as a plurality of parts and, for each part:
 computer readable program code identifying an associated data type; 
 computer readable program code identifying a type factory for said identified data type; 
 computer readable program code creating at least one data-object based on said identified type factory; 
 computer readable program code passing said created data-object to said in-port; 
 computer readable program code populating said data-object with values from corresponding part of said message; 
 computer readable program code passing said populated data object from the in-port corresponding to said first middleware to said out-port corresponding to the second middleware; and 
   (d) computer readable program code iteratively repeating step (c) for each part of said message.   
   
   
       6 . An article of manufacture comprising computer storage medium having computer readable program code that is executable by a computer to implement a method to integrate a plurality of middleware without canonicalization of data at runtime, said method implemented using in-ports and out-ports, each in-port facilitating communication between a specific middleware and a first interface and each out-port facilitating communication between another specific middleware and said first interface, said medium comprising:
 (a) computer readable program code receiving inputs identifying at least a first and second middleware to be made interoperative, said interoperation implemented via at least one communication path between an in-port corresponding to said first middleware and an out-port corresponding to said second middleware;   (b) computer readable program code receiving an incoming message at said in-port;   (c) computer readable program code handling said received message as a plurality of parts and, for each part:
 computer readable program code identifying an associated data type; 
 computer readable program code identifying a type factory for said identified data type; 
 computer readable program code creating at least one data-object based on said identified type factory; 
 computer readable program code passing said created data-object to said in-port; and 
 computer readable program code populating said data-object with values from corresponding part of said message; 
   (d) computer readable program code iteratively repeating step (c) for each part of said message and populating a plurality of data-objects; and   (e) computer readable program code passing said plurality of populated data objects from the in-port corresponding to said first middleware to said out-port corresponding to the second middleware.

Join the waitlist — get patent alerts

Track US2010211961A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.