System and method for component-based software development
First Claim
1. A messaging platform for a component-based software system, the platform comprising:
- a connection assembler for at least one of creating, managing and manipulating a first messaging platform connection;
a protocol management framework for implementation of a predetermined transport protocol over the first messaging platform connection;
a schema generator for, responsive to a request for service received over a second messaging platform connection, creating a document according to a predetermined format, the document containing information to be provided to another system over the first messaging platform connection;
an encoding component for converting a document in the predetermined format into a first encoded object that can be understood and used by the other system, the first encoded object being encoded according to a default encoding protocol; and
a translation component for encoding a document in the predetermined format into a second encoded object that can be understood and used by the other system, the second encoded object being encoded according to an encoding protocol different from the default encoding protocol.
5 Assignments
0 Petitions
Accused Products
Abstract
An enterprise component-based software development system includes a component platform with a number of development tools and services that enable rapid and straightforward development of component-based systems. The component platform describes a middle tier architecture for a multi-tier, multi-user application. It defines the services and facilities as well as the structure in which components can execute. It helps to provide an extensible platform for the construction, management and execution of component-based software. A messaging platform facilitates communication between different computers. When a component requests a service from another component, the request is serialized and encoded into a platform-independent language such as XML. The XML-encoded message is transmitted over the Internet using an HTTP protocol to a receiving computer, which validates the message and delivers it to the component providing the requested service. Since XML is a platform and architecture independent language, requests processed in this way can be used by a wide variety of disparate systems.
153 Citations
23 Claims
-
1. A messaging platform for a component-based software system, the platform comprising:
-
a connection assembler for at least one of creating, managing and manipulating a first messaging platform connection; a protocol management framework for implementation of a predetermined transport protocol over the first messaging platform connection; a schema generator for, responsive to a request for service received over a second messaging platform connection, creating a document according to a predetermined format, the document containing information to be provided to another system over the first messaging platform connection; an encoding component for converting a document in the predetermined format into a first encoded object that can be understood and used by the other system, the first encoded object being encoded according to a default encoding protocol; and a translation component for encoding a document in the predetermined format into a second encoded object that can be understood and used by the other system, the second encoded object being encoded according to an encoding protocol different from the default encoding protocol. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. An apparatus comprising:
logic instructions operable to; receive a service request from a sender, wherein the service request invokes a service component and provides parameters required by the service component; determine whether the service component invoked by the service request is available; determine the parameters in the service request that are required by the service component; create a request document that includes the parameters required by the service component based on at least some of the parameters in the service request; create an encoder object upon receipt of the service request, wherein the encoder object identifies a handler that translates the request document to a document format required by the service component; and transmit the encoder object and the request document to a system hosting the service component. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23)
Specification