Merged PR 3982: Set versionnr to 4.0.1.0- Set the AssemblyVersion and AssemblyFileVersion to 4.0.1.0
- Refer to the correct assembly-version in the setting files
Merged PR 3962: Select the correct PMode when receiving AS4 MessagesMake sure that the correct receiving- and sending pmodes are determined when an AS4 Message is received.
Related work items: #11174
Corrected DeterminePMode step for bundled messagesMake sure that a Receiving PMode is determined when receiving a bundled AS4 Message. (When the first message-unit is a signalmessage and one of the bundled message-units is a usermessage, we should determine a receiving pmode as well).
Make sure that DeterminePModeStep correctly identifies the Send and Receive PMode informationMake sure that the correct PModes are retrieved when the MSH is acting as an Intermediary or if PiggyBacking is used.
PR-SUG: add extra SendingPMode check for MepBinding = Push before retrieving the PushConfiguration.Protocol.Url in the OutMessageService.InsertAS4MessageAsync
Removed the retry functionality when creating a DatabaseSpyWhen instantiating a DatabaseSpy, it is not the responsability of the DatabaseSpy to wait of being instantiated until the Db is completely migrated.
Drop SQL Server databases before starting component-testsBy dropping all SQL Server database that are used by the component-tests, we can be sure that the databases that are used by the test are compatible with the version of AS4.NET that is being tested.
Merged PR 3897: Bugfix: Enable send-RetryFunctionality when configured in PMode and Multihop == trueSend Retry functionality must be enabled, even if MultiHop is enabled in the sending pmode. It should not be enabled however when the AS4.NET MSH is in a forwarding role for the message that is being sent (forwarded).
Related work items: #11370
Bugfix: Enable send-RetryFunctionality when configured in PMode and Multihop == trueSend Retry functionality must be enabled, even if MultiHop is enabled in the sending pmode. It should not be enabled however when the AS4.NET MSH is in a forwarding role for the message that is being sent (forwarded).
Merged PR 3842: Specific DynamicDiscovery settings are no longer case-sensitiveSpecific DynamicDiscovery settings are no longer case-sensitive
The specific settings that are configured for a DynamicDiscovery profile should not be case-sensitive. A case-insensitive comparer is used to retrieve the settings.
Related work items: #11180
Specific DynamicDiscovery settings are no longer case-sensitiveThe specific settings that are configured for a DynamicDiscovery profile should not be case-sensitive. A case-insensitive comparer is used to retrieve the settings.
Merged PR 3599: Set VersionNr for v4.0.0- Modified AssemblyInfo.cs files so that the version is set to 4.0.0.0
- settings files refer to version 4.0.0.0 of the AS4.NET assemblies
Merged PR 3535: BUG: reliability failed to store in SQL Server because of multiple UNIQUE indexes for nullable collumnsBecause of the indexes set on the 'RetryReliability' table for the
referenced entities (In/Out Message/Exception) were UNIQUE indexes; we
had problems inserting multiple entries into a SQL Server instance since
it has duplicate entries for 'NULL' values.
Merged PR 3588: BUG: encrypted & signed message with IsserSerial or KeyIdentifier adapts wrong KeyInfoBUG: encrypted & signed message with IsserSerial or KeyIdentifier adapts wrong KeyInfo
Because of the wide XPath selection in both the
`KeyIdentifierSecurityTokenReference` and
`IssuerSerialSecurityTokenReference` the `<KeyInfo/>` element of the
encryption information was adapted (adding a `Id` attribute) and not the
`<KeyInfo/>` element in the `<Signature/>`.
This resulted in an decryption f...
Frederik Gheysels
Stijn Moreels
Stijn Moreels