IMPLEMENTING A MIDDLEWARE COMPONENT USING FACTORY PATTERNS

• US 20110126212A1
• Filed: 11/23/2009
• Published: 05/26/2011
• Est. Priority Date: 11/23/2009
• Status: Active Grant

• Current Assignee: Raytheon Company (Rtx Corporation)
• Original Assignee: Raytheon Company (Rtx Corporation)
• Inventors: Sedlmeyer, Robert, Schilling, Scott A., Lipasek, John J.
• Granted Patent: US 8,752,066 B2
• Time in Patent Office: Days
• US Class Current: 719/313
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

In one aspect, a method to use a middleware component includes receiving a request from an application to interact with a platform using a service and using an abstract factory pattern corresponding to the service. The abstract factory pattern is associated with a first factory pattern stored in the middleware component. The method also includes determining if the first factory pattern is associated with the platform and invoking the service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

Claims

1. A method to use a middleware component, comprising:

receiving a request from an application to interact with a platform using a service;

using an abstract factory pattern corresponding to the service, the abstract factory pattern being associated with a first factory pattern stored in the middleware component;

determining if the first factory pattern is associated with the platform; and

invoking the service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

2. The method of claim 1 wherein receiving a request from an application to interact with a platform using a service comprises receiving a request from an application to interact with a platform using a messaging service.

3. The method of claim 1 wherein receiving a request from an application to interact with a platform using a service comprises receiving a request from an application to interact with a platform using an invocation service.

4. The method of claim 1 wherein receiving a request from an application to interact with a platform using a service comprises receiving a request from an application to interact with a platform using a logging service.

5. The method of claim 1 wherein receiving a request from an application to interact with a platform using a service comprises receiving a request from an application to interact with a platform using a persistence data service.

6. The method of claim 1 wherein receiving a request from an application to interact with a platform comprises receiving a request from an application to interact with one of JAVA®

2, Enterprise Edition (J2EE®

), MICROSOFT®

WINDOWS®

, Common Object Request Broker Architecture (CORBA®

), Sun Solaris, Linux, HP Solaris, Mac OS, and System of Systems Common Operation Environment (SOSCOE) platforms.

7. The method of claim 1 wherein the platform is a first platform, the request is a first request and the abstract factory pattern is associated with a second factory pattern and further comprising:

receiving a second request from the application to interact with a second platform using the service;

determining if the second factory pattern is associated with the second platform; and

using the service with the second platform if the second factory pattern is associated with the second platform.

8. The method of claim 1 wherein the service is a first service, the abstract factory pattern is a first abstract factory pattern and the request is a first request and further comprising:

receiving a second request from the application to interact with the platform using a second service;

using a second abstract factory pattern corresponding to the second service, the second abstract factory pattern associated with a second factory pattern stored in the middleware component;

determining if the second factory pattern is associated with the platform; and

using the second service with the platform if the second factory pattern is associated with the platform.

9. An article comprising a machine-readable medium that stores executable instructions to invoke a service on a platform, the instructions causing a machine to:

receive a request from an application to interact with the platform using the service;

use an abstract factory pattern corresponding to the service, the abstract factory pattern being associated with a first factory pattern stored in a middleware component;

determine if the first factory pattern is associated with the platform; and

invoke the service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

10. The article of claim 9 wherein the instructions to receive a request from an application to interact with a platform using a service comprises instructions to receive a request from an application to interact with a platform using one of a messaging service, an invocation service, a logging service and a persistence data service.

11. The article of claim 9 wherein the instructions to receive a request from an application to interact with a platform comprises instructions to receive a request from an application to interact with one of JAVA®

2, Enterprise Edition (J2EE®

), MICROSOFT®

WINDOWS®

, Common Object Request Broker Architecture (CORBA®

), Sun Solaris, Linux, HP Solaris, Mac OS, and System of Systems Common Operation Environment (SOSCOE) platforms.

12. The article of claim 9 wherein the platform is a first platform, the request is a first request and the abstract factory pattern is associated with a second factory pattern and further comprising instructions causing the machine to:

receive a second request from the application to interact with a second platform using the service;

determine if the second factory pattern is associated with the second platform; and

use the service with the second platform if the second factory pattern is associated with the second platform.

13. The article of claim 9 wherein the service is a first service, the abstract factory pattern is a first abstract factory pattern and the request is a first request and further comprising instructions causing a machine to:

receive a second request from the application to interact with the platform using a second service;

use a second abstract factory pattern corresponding to the second service, the second abstract factory pattern associated with a second factory pattern stored in the middleware component;

determine if the second factory pattern is associated with the platform; and

use the second service with the platform if the second factory pattern is associated with the platform.

14. An apparatus to invoke a service on a platform, comprising:

circuitry to;

receive a request from an application to interact with the platform using the service;

use an abstract factory pattern corresponding to the service, the abstract factory pattern being associated with a first factory pattern stored in a middleware component;

determine if the first factory pattern is associated with the platform; and

invoke the service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

15. The apparatus of claim 14 wherein the circuitry comprises at least one of a processor, a memory, programmable logic and logic gates.

16. The apparatus of claim 14 wherein the circuitry to receive a request from an application to interact with a platform using a service comprises circuitry to receive a request from an application to interact with a platform using one of a messaging service, an invocation service, a logging service and a persistence data service.

17. The apparatus of claim 14 wherein the circuitry to receive a request from an application to interact with a platform comprises circuitry to receive a request from an application to interact with one of JAVA®

2, Enterprise Edition (J2EE®

), MICROSOFT®

WINDOWS®

, Common Object Request Broker Architecture (CORBA®

), Sun Solaris, Linux, HP Solaris, Mac OS, and System of Systems Common Operation Environment (SOSCOE) platforms.

18. The apparatus of claim 14 wherein the platform is a first platform, the request is a first request and the abstract factory pattern is associated with a second factory pattern and further comprising circuitry to:

receive a second request from the application to interact with a second platform using the service;

determine if the second factory pattern is associated with the second platform; and

use the service with the second platform if the second factory pattern is associated with the second platform.

19. The apparatus of claim 14 wherein the service is a first service, the abstract factory pattern is a first abstract factory pattern and the request is a first request and further comprising circuitry to:

receive a second request from the application to interact with the platform using a second service;

use a second abstract factory pattern corresponding to the second service, the second abstract factory pattern associated with a second factory pattern stored in the middleware component;

determine if the second factory pattern is associated with the platform; and

use the second service with the platform if the second factory pattern is associated with the platform.