System and method for consolidating middleware functionality
A method for marshalling data from multiple middleware applications to an implementation includes receiving first data from a first middleware application, the first data having a first format of multiple available formats. A first path is selected from multiple paths based on the first format, the multiple paths corresponding to the multiple available formats. The first data is converted from the first format to a common format, which is compatible with the implementation, based on the selected first path. The method may further include receiving second data from a second middleware application, the second data have a second format of the multiple available formats; selecting a second path from the multiple paths based on the second format; and converting the second data from the second format to the common format based on the selected second path.
1. A method for marshalling data from a plurality of middleware applications to an implementation, the method comprising:
receiving data from a middleware application from the plurality of middleware applications;
determining, by a server, whether the received data has a text-based format or a binary-based format,
wherein when the received data has the text-based format, the server further determining a type of text data from a plurality of text data types, and processing the received data based on the determined text data type, and
wherein when the received data has the binary-based format, the server further determining an appropriate binary marshalling method from a plurality of binary marshalling methods, and processing the received data based on the determined appropriate binary marshalling method; and
converting the processed received data to a common format, the common format being compatible with the implementation,
wherein the implementation comprises a consolidated middleware management function that initializes a main middleware thread that subsequently initializes designated slave threads, and that permits each initialized slave thread to function independently of the main middleware thread, until such time that the main middleware thread assumes control over each of the initialized slave threads and shuts down each of the initialized slave threads, after which the main middleware thread shuts down.
2. The method according to claim 1 , in which the plurality of middleware applications comprise at least one of a Java Message Service (JMS) application and a Common Object Request Broker Application (CORBA) application.
3. The method according to claim 2 , in which the middleware application comprises the JMS application, and the text-based format comprises one of an XML format and a Simple Object Access Protocol (SOAP) format.
4. The method according to claim 2 , in which the middleware application comprises the CORBA application, and the binary-based format comprises one of an XDR format and a CDR format.
5. The method according to claim 1 , in which the common format comprises a Java format.
6. The method according to claim 5 , in which the implementation comprises one of a business logic and a delegate.
7. The method according to claim 1 , wherein the designated slave threads comprise different types of middleware.
8. The method according to claim 1 , wherein the common format comprises Java objects that are used to call the implementation.
9. A computer readable storage device that stores a program for marshalling data from a plurality of middleware applications to an implementation, the computer readable storage device comprising:
a receiving code segment for receiving data from a first middleware application from the plurality of middleware applications;
a determining code segment for determining, by a server, whether the received data has a text-based format or a binary-based format,
wherein when the received data has the text-based format, the server further determining a type of text data from a plurality of text data types, and processing the received data based on the determined text data type, and
wherein when the received data has the binary-based format, the server further determining an appropriate binary marshalling method from a plurality of binary marshalling methods, and processing the received data based on the determined appropriate binary marshalling method; and
a converting code segment for converting the processed received data to a common format, the common format being compatible with the implementation,
wherein the implementation comprises a consolidated middleware management function that initializes a main middleware thread that subsequently initializes designated slave threads, and that permits each initialized slave thread to function independently of the main middleware thread, until such time that the main middleware thread assumes control over each of the initialized slave threads and shuts down each of the initialized slave threads, after which the main middleware thread shuts down.
10. The computer readable storage device according to claim 9 , in which the plurality of middleware applications comprise at least one of a Java Message Service (JMS) application and a Common Object Request Broker Application (CORBA) application.
11. The computer readable storage device according to claim 10 , in which the middleware application comprises the JMS application, and the text-based format comprises one of an XML format and a Simple Object Access Protocol (SOAP) format.
12. The computer readable storage device according to claim 10 , in which the middleware application comprises the CORBA application, and the binary-based format comprises one of an XDR format and a CDR format.
13. The computer readable storage device according to claim 9 , in which the common format comprises a Java format.
14. The computer readable storage device according to claim 13 , in which the implementation comprises one of a business logic and a delegate.
15. The computer readable storage device according to claim 9 , wherein the designated slave threads comprise different types of middleware.
16. The computer readable storage device according to claim 9 , wherein the common format comprises Java objects that are used to call the implementation.
17. A computer server for marshalling data from a plurality of middleware applications to an implementation, the computer server comprising:
a receiver for receiving data from a middleware application from the plurality of middleware applications;
a computer processor for determining whether the received data has a text-based format or a binary-based format,
wherein when the received data has the text-based format, the processor further determining a type of text data from a plurality of text data types, and processing the received data based on the determined text data type, and
wherein when the received data has the binary-based format, the processor further determining an appropriate binary marshalling method from a plurality of binary marshalling methods, and processing the received data based on the determined appropriate binary marshalling method; and
a converter for converting the processed received data to a common format, the common format being compatible with the implementation,
wherein the implementation comprises a consolidated middleware management function that initializes a main middleware thread that subsequently initializes designated slave threads, and that permits each initialized slave thread to function independently of the main middleware thread, until such time that the main middleware thread assumes control over each of the initialized slave threads and shuts down each of the initialized slave threads, after which the main middleware thread shuts down.
18. The computer server according to claim 17 , wherein the common format comprises Java objects that are used to call the implementation.