MESSAGE CONTRACT PROGRAMMING MODEL
First Claim
1. In a distributed messaging system, a method of formatting a layout of a message object using a message contract that maps elements to various portions thereof, the method comprising:
- receiving a request to create a message object in accordance with a message contract, which includes one or more attributes corresponding to one or more elements of a message class;
parsing the message contract for identifying the one or more attributes that define what elements of the message class map to one or more portions of the message object; and
populating the one or more portions of the message object with the one or more elements in accordance with the one or more attributes defined within the message contract.
2 Assignments
0 Petitions
Accused Products
Abstract
Embodiments described herein provide for a message contract programming model, which is a mechanism for service developers to control the processing, layout, and creation of messages (e.g., SOAP) without losing the benefits of a strongly-typed data contract model. Such programming model is based on attributes, which can be used to define the action or operations, headers, and body parts components of a message. These attributes may be used on a type annotated with message contract or on a service operation to control the manner in which the message (e.g., SOAP) is constructed from a service process, process parameters, and/or return values. The use of the message contract in conjunction with a message formatter as defined herein provides for many advantageous features and embodiments described herein.
103 Citations
15 Claims
-
1. In a distributed messaging system, a method of formatting a layout of a message object using a message contract that maps elements to various portions thereof, the method comprising:
-
receiving a request to create a message object in accordance with a message contract, which includes one or more attributes corresponding to one or more elements of a message class; parsing the message contract for identifying the one or more attributes that define what elements of the message class map to one or more portions of the message object; and populating the one or more portions of the message object with the one or more elements in accordance with the one or more attributes defined within the message contract. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. In a distributed messaging system, a message contract used in creating message objects, instances, and NPDL contracts used to communicate with a service, the message contract including:
-
one or more elements of a message class that correspond to one or more operations of a service; and one or more attributes annotated to the one or more elements, which map the one or more elements to one or more portions of a message object. - View Dependent Claims (9, 10)
-
-
11. In a distributed messaging system, a method of automatically creating one or more portions of an NPDL contract used by clients in communicating with a service, the method comprising:
-
receiving a request to create a NPDL contract, which defines how a client is to communicate with a service; receiving a message contract, which includes one or more attributes corresponding to one or more elements of a message class; based on the received message contract, creating at least a portion of the NPDL contract by specifying where and what elements should be included in a message object or instance thereof when communicating with the service. - View Dependent Claims (12, 13, 14, 15)
-
Specification