Remember, any value that can be converted to a TimeSpan works! For instance, to set the message time-to-live, specify a property with the duration. Header values can be specified in the anonymous object using a double-underscore (pronounced 'dunder' apparently) property name. Nested objects are also supported, for instance, if a property was of type Address and another anonymous object was created (or any type whose property names match the names of the properties on the message contract), those properties would be set on the message contract. For instance, a dictionary of (int,decimal) could be converted on the fly to (long, string) using the default format conversions. Most numeric, string, and date/time conversions are supported, as well as several advanced conversions (including variables, and asynchronous Task results).Ĭollections, including arrays, lists, and dictionaries, are broadly supported, including the conversion of list elements, as well as dictionary keys and values. The anonymous object is loosely typed, the properties are matched by name, and there is an extensive set of type conversions that may occur to obtain match the types defined by the interface. If you need to do this, keep using the GetSendEndpoint method. A potential downside here that you will not be able to send messages of the same type to different endpoints by using conventions. Usually, addresses are kept in the configuration and accessing the configuration from all over the application is not a good practice.Įndpoint conventions solve this issue by allowing you to configure the mapping between message types and endpoint addresses. Using send endpoints might seem too verbose, because before sending any message, you need to get the send endpoint and to do that you need to have an endpoint address. # Supported Address Schemes Short Address This short syntax eliminates the need to know the scheme, host, port, and virtual host of the broker, only the queue and/or exchange details are required.Įach transport has a specific set of supported short addresses.
Both the exchange and the queue would be created if either did not exist. This would return a send endpoint for the input-queue exchange, which would be bound to the input-queue queue. GetSendEndpoint(new Uri("queue:input-queue"))
#MASSTRANSIT SET RESPONSE ADDRESS SERIES#
Once the Send method has been called (only once or repeatedly to send a series of messages), the ISendEndpoint reference should fall out of scope. The last resort, and should only be used for messages that are being sent by an initiator - a process that is initiating a business process. This may be passed as an argument, but is typically specified on the constructor of an object that is resolved using a dependency injection container. This ensures that the correlation headers, message headers, and trace information is propagated to the sent message. The ConsumeContext of the message being consumed An ISendEndpoint is obtained from one of the following objects: One of the Send method overloads on the ISendEndpoint interface is called, which will then send the message to the transport. To send a message, the DestinationAddress is used to deliver the message to an endpoint - such as a queue. In 'Program.cs' let's register 'MassTransit' and 'RabbitMQ' services.Learn about Send in this short video (opens new window).
Inside of this method, our logic to store the message data has been implemented.
Public async Task Consume(ConsumeContext context)Īwait _salesBusinessContext.SaveChangesAsync() _salesBusinessContext = salesBusinessContext Public ProductCreatedConsumer(SalesBusinessContext salesBusinessContext) Private readonly SalesBusinessContext _salesBusinessContext Public class ProductCreatedConsumer : IConsumer SalesBusiness.API/Consumer/ProductCreatedConsumer.cs: using MassTransit
0 kommentar(er)
