These are the release notes:
Modifications and changes:
*Localization options extended: In addition to the language, you can also define a region. Starting with Java 9, weekday calculations depend not only on the language, but also on the set region. In the client, this had an effect on the date selection of the client - here, Sun was always displayed as the first day of the week - but this is not the case in Europe, for example. In the client this can be set directly in the settings, the server now has the option -region
*Dark mode support of the client: The client can be switched into dark mode. This must be done manually, the software does not recognize whether the operating system is in dark mode. The option for client and also server is -mode DARK, default setting is -mode LIGHT. The dark mode was realized with the help of FlatLaf (https://www.formdev.com/flatlaf/)
*The whole client was reworked - the elements seemed small and crowded - here most of the line spacing was increased and all icons were adapted.
*HiDPI Icons: All icons of the client were redesigned and are now scalable, they are no longer bitmaps but vector graphics. So there should be no problems at this point if the output is scaled via the operating system. Not only multiples of the native resolution are supported (Mac OS), but also any intermediate values (Windows)
*Automatic contrast adjustment of some colors of the client: Some output of the client was directly in certain colors, for example red or green. Depending on the operating system or dark mode, this could lead to problems with visibility. Now there is an automatic contrast adjustment for each output, so there should be no more problems with the contrast of certain colors.
*In the certificate management it is now possible to export a public key in SSH2 format. This has no direct function for AS4 operation, but allows a better integration with SSH products
*Certificate manager: There is now a display of the OID of the signature algorithm of each certificate
*Key Generator: The key lengths have been set to 2048 bit by default, in addition self signed RSASSA_PSS signed keys are now supported
*Certificate management: "Cancel" button added to authentication dialog
*Certificate management: It was possible to delete a certificate by simply closing the corresponding dialog in the dialog for renaming an alias
3rd party software updates:
*Update from HSQLDB 2.41 to 2.5.0 (DB system)
*Update of commons pool from 2.4.2 to 2.6.2
*Update of commons io from 2.5 to 2.6
*Update of commons dbcp from 2.1.1 to 2.6.0
*Update from jaxen 1.1.3 to 1.2
*Update from javamail 1.5.6 to 1.6.2
*Update to Bouncycastle v1.64 (Crypto API)
*Update from Lucene 7.7.2 to Lucene 8.2 (Indexing of system events)
*Update to MINA 2.1.2 (Client-Server Interface)
Your mendelson dev team
On attempting to send a Peppol AS4 message containing the following collaboration info
we receive a SignalMessage as such:
<SignalMessage xmlns:ns6="http://www.w3.org/2003/05/soap-envelope" xmlns:ns5="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns7="http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/" xmlns:ns2="http://docs.oasis-open.org/ebxml-bp/ebbp-signals-2.0" xmlns:ns4="http://www.w3.org/1999/xlink" xmlns:ns3="http://www.w3.org/2000/09/xmldsig#">
<ns7:Error category="Content" errorCode="EBMS:0003" origin="ebms" severity="FAILURE" shortDescription="ValueInconsistent">
<ns7:Description xml:lang="en">Although the message document is well formed and schema valid, some element/attribute value is inconsistent either with the content of other element/attribute, or with the processing mode of the MSH, or with the normative requirements of the ebMS specification.
<ns7:ErrorDetail>[SOAP Validation] If the AgreementRef/@type attribute is not present, the content of the AgreementRef element MUST be a URI.
If we send UBL/SBD documents via Mendelson AS4 to our Peppol AS4 endpoint the SOAP-XML Mendelson generates does set the collaboration info the same way. In order to receive the AS4 message successfully via Mendelson AS4 we have to disable the validation of the SOAP-XML first.
According to the EBMS XSD AgreementRef is defined as such:
<xsd:attribute name="type" type="tns:non-empty-string" use="optional"/>
<xsd:attribute name="pmode" type="tns:non-empty-string" use="optional"/>
hence I think this is a bug in the b27 version of Mendelson AS4
closing elements such as </eb:AgreementRef> are swallowed by your forum-software ...
sounds interesting. Please contact the mendelson support via mail, then we can clarify this via mail.