Skip to content

Releases: phax/phase4

phase4 1.3.6

01 Apr 23:21
Compare
Choose a tag to compare
  • Moved all the documentation into a Wiki for better structuring of information
  • Added new submodule phase4-profile-bpc to support the BPC market pilot
  • Added support for a CEF two-corner profile. See issue #79. Thx @Nagendra-Naidu1629
  • Increased the debug logging for the sample Peppol Server application
  • The data type of PModeReceptionAwareness.RetryIntervalMS was changed from int to long
  • The SMP Endpoint ServiceActivationDate and ServiceExpirationDate values are considered properly (see peppol-commons 8.7.3 release)

Dependencies required:

phase4 1.3.5

21 Dec 12:16
Compare
Choose a tag to compare

phase4 1.3.4

14 Dec 23:44
Compare
Choose a tag to compare

phase4 1.3.3

10 Dec 14:04
Compare
Choose a tag to compare
  • Updated to Log4J2 2.15.0
  • Updated to WSS4J 2.4.0
  • Updated to xmlsec 2.3.0
  • Fixed a typo in method name of class AbstractPeppolUserMessageBuilder (missing p of endpoint)
  • Fixed the interface name from IPhase4PeppolValidatonResultHandler to IPhase4PeppolValidationResultHandler (see issue #68)
  • Updated the Maven JAXB2 plugin so that it also build with Java 17

Dependencies required:

phase4 1.3.2

27 Sep 13:56
Compare
Choose a tag to compare
  • Updated to ph-web 9.6.1
  • Updated to phive-rules 2.1.7
  • Updated to xmlsec 2.2.3 (security fix)
  • Allowing to set the "RefToMessageId" in the client sender builders
  • Improved the error handling of ISOAPHeaderElementProcessor invocations (see issue #52)

Dependencies required:

phase4 1.3.1

21 May 18:21
Compare
Choose a tag to compare
  • Updated to xmlsec 2.2.2
  • Added the possibility to provide the content ID in the Peppol AS4 sender
  • Changed the layout of the default, random Content-IDs to match RFC 822
  • The error handling of the SPI invocations was improved
  • AS4MessageProcessorResult.createFailure now also takes empty arguments
  • Extended the internal API of AS4XServletHandler to make calls from the outside simpler
  • Added a new class AS4DumpReader that can be helpful in reading dumped ".as4in" messages at a later point in time

Dependencies required:

phase4 1.3.0

03 May 14:27
Compare
Choose a tag to compare
  • Updated to ph-commons 10.1
  • Moved the classes AS4IncomingDumperFileBased, AS4OutgoingDumperFileBased and AS4RawResponseConsumerWriteToFile from package com.helger.phase4.servlet.dump to package com.helger.phase4.dump. The old classes remain there, but deprecated.
  • IAS4IncomingDumper.onEndRequest is only called if onNewRequest returned a non-null stream
  • Improved logging in case of failed sending prerequisites
  • Changed from Offset(Date|Time|DateTime) to XMLOffset(Date|Time|DateTime) where the message exchange is affected
  • The JAXB implementation must now explicitly be added to an application pom.xml e.g. like this:
<dependency>
  <groupId>com.sun.xml.bind</groupId>
  <artifactId>jaxb-impl</artifactId>
</dependency>

phase4 1.2.0

28 Mar 20:16
Compare
Choose a tag to compare
  • Added the response AS4 Message ID as parameter to IAS4ServletMessageProcessorSPI.processAS4ResponseMessage
  • Renamed class EAS4IncomingMessageMode to EAS4MessageMode
  • Extended IAS4OutgoingDumper API with an EAS4MessageMode param
  • Extended the IAS4MessageState with "ref to message ID" and "message timestamp"

phase4 1.1.1

23 Mar 13:07
Compare
Choose a tag to compare
  • Made the AS4 message ID suffix customizable (see issue #50)

phase4 1.1.0

23 Mar 09:22
Compare
Choose a tag to compare
  • Updated to ph-commons 10
  • Changed from Local(Date|Time|DateTime) to Offset(Date|Time|DateTime) where the message exchange is affected