It does not send mandatory by default whereas before it did. I thought we had decided that this was how the Java is to do it too? If not I can change it back.
Reason I changed it was because the error handling in the .Net is broken (bug introduced when I fixed fail-over), and returned messages cause it to break. I should really fix that properly too. Rupert On 31/12/2007, Martin Ritchie <[EMAIL PROTECTED]> wrote: > > Just catching up with all the goings on over the Festive period. > > Rupert, why are we making the .NET not send Mandatory messages? Is > there are similar change to be done to the other clients? > > On 19/12/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Author: rupertlssmith > > Date: Wed Dec 19 05:40:05 2007 > > New Revision: 605536 > > > > URL: http://svn.apache.org/viewvc?rev=605536&view=rev > > Log: > > Messages were being sent mandatory by default, set to false. > > > > Modified: > > > incubator/qpid/branches/M2.1.1/dotnet/Qpid.Messaging/MessagePublisherBuilder.cs > > > > Modified: > incubator/qpid/branches/M2.1.1/dotnet/Qpid.Messaging/MessagePublisherBuilder.cs > > URL: > http://svn.apache.org/viewvc/incubator/qpid/branches/M2.1.1/dotnet/Qpid.Messaging/MessagePublisherBuilder.cs?rev=605536&r1=605535&r2=605536&view=diff > > > ============================================================================== > > --- > incubator/qpid/branches/M2.1.1/dotnet/Qpid.Messaging/MessagePublisherBuilder.cs > (original) > > +++ > incubator/qpid/branches/M2.1.1/dotnet/Qpid.Messaging/MessagePublisherBuilder.cs > Wed Dec 19 05:40:05 2007 > > @@ -31,7 +31,7 @@ > > /// Default value for mandatory flag is true, i.e. server will > not silently drop messages where no queue is > > /// connected to the exchange for the message > > /// </summary> > > - const bool DEFAULT_MANDATORY = true; > > + const bool DEFAULT_MANDATORY = false; > > > > IChannel _channel; > > string _exchangeName = null; > > > > > > > > > -- > Martin Ritchie >
