Releases: OxalisCommunity/oxalis-ng
Releases · OxalisCommunity/oxalis-ng
Oxalis-NG v1.2.0-RC2
- NAPTR Lookup Support (PFUOI 4.4.0): In this release, NAPTR lookup is now the default lookup method.
Users who prefer to continue using CNAME lookup may do so until T2 (01.11.2025). To maintain CNAME lookup with this version, set the following property in oxalis.conf:
lookup.locator.class=network.oxalis.vefa.peppol.lookup.locator.BusdoxLocator
- Peppol Wildcard Change (PFUOI 4.3.0)
To support the Peppol PINT wildcard migration, a new mandatory parameter has been introduced: oxalis.pint.wildcard.migration.phase
In this release, the default value is set to 1. However, you can configure this value in oxalis.conf as and when needed as per timeframe:
# For T1 (May 15th, 2025, onward): - Set value to 1 on/after May 15th, 2025 ) - Default value in this version
oxalis.pint.wildcard.migration.phase=1
# For T2 (~September 03, 2025/TBD): - "busdox scheme exact match" in PINT messages will be removed in T2. You will start getting error message with phrase "...or SMP registration is not valid" when you continue trying to send PINT message with "busdox scheme"
oxalis.pint.wildcard.migration.phase=2
For PINT documents. always use "peppol-doctype-wildcard" as Document Type Identifier Scheme in SBDH otherwise default "busdox-docid-qns" value will be considered. This can lead to SMP lookup error if SMP registration is only available with "peppol-doctype-wildcard" and you are Not providing Document Type Identifier Scheme in SBDH. For details, refer "PINT Wildcard Migration Plan"
- Bump httpclient to 5.4.4
- Bump vefa.peppol to 4.1.1
- Bump commons-certvalidator to 4.6.0
- Bump peppol-specifications to 2.5.0
- Bump cxf to 4.0.8
- Bump jetty to 11.0.25
- Bump jaxb-impl to 4.0.5
- Bump guava to 33.4.8-jre
- Bump joda-time to 2.14.0
- Bump commons-dbcp2 to 2.13.0
- Bump commons-io to 2.19.0
- Bump mariadb-java-client to 3.5.3
- Bump hsqldb to 2.7.4
- Bump logback to 1.5.18
- Bump opentelemetry.apache.httpclient to 2.16.0-alpha
- Bump opentelemetry to 1.50.0
- Bump testng to 7.11.0
- Bump mockito-core to 5.17.0
- Bump lombok to 1.18.38
- Bump metainf-services to 1.11
Full Changelog: v1.1.0...v1.2.0-RC2
Oxalis-NG v1.2.0-RC1
- NAPTR Lookup Support (PFUOI 4.4.0): In this release, NAPTR lookup is now the default lookup method.
Users who prefer to continue using CNAME lookup may do so until T2 (01.11.2025). To maintain CNAME lookup with this version, set the following property in oxalis.conf:
lookup.locator.class=network.oxalis.vefa.peppol.lookup.locator.BusdoxLocator
- Peppol Wildcard Change (PFUOI 4.3.0)
To support the Peppol PINT wildcard migration, a new mandatory parameter has been introduced: oxalis.pint.wildcard.migration.phase
In this release, the default value is set to 1. However, you can configure this value in oxalis.conf as and when needed as per timeframe:
# For T1 (May 15th, 2025, onward): - Set value to 1 on/after May 15th, 2025 ) - Default value in this version
oxalis.pint.wildcard.migration.phase=1
# For T2 (~September 03, 2025/TBD): - "busdox scheme exact match" in PINT messages will be removed in T2. You will start getting error message with phrase "...or SMP registration is not valid" when you continue trying to send PINT message with "busdox scheme"
oxalis.pint.wildcard.migration.phase=2
For PINT documents. always use "peppol-doctype-wildcard" as Document Type Identifier Scheme in SBDH otherwise default "busdox-docid-qns" value will be considered. This can lead to SMP lookup error if SMP registration is only available with "peppol-doctype-wildcard" and you are Not providing Document Type Identifier Scheme in SBDH. For details, refer "PINT Wildcard Migration Plan"
- Bump httpclient to 5.4.4
- Bump vefa.peppol to 4.1.0
- Bump commons-certvalidator to 4.6.0
- Bump peppol-specifications to 2.5.0
- Bump cxf to 4.0.8
- Bump jetty to 11.0.25
- Bump jaxb-impl to 4.0.5
- Bump guava to 33.4.8-jre
- Bump joda-time to 2.14.0
- Bump commons-dbcp2 to 2.13.0
- Bump commons-io to 2.19.0
- Bump mariadb-java-client to 3.5.3
- Bump hsqldb to 2.7.4
- Bump logback to 1.5.18
- Bump opentelemetry.apache.httpclient to 2.16.0-alpha
- Bump opentelemetry to 1.50.0
- Bump testng to 7.11.0
- Bump mockito-core to 5.17.0
- Bump lombok to 1.18.38
- Bump metainf-services to 1.11
Full Changelog: v1.1.0...v1.2.0-RC1
Oxalis-NG v1.1.0
What's Changed
- eDEC CodeList Support: Added support for eDEC CodeList version 9.1.
- NAPTR Lookup Support (PFUOI 4.4.0): Users who wish to enable NAPTR lookup can do so by configuring the following property in oxalis.conf:
lookup.locator.class=network.oxalis.vefa.peppol.lookup.locator.BdxlLocator
- Peppol Wildcard Change (PFUOI 4.3.0): A new mandatory parameter has been introduced to support Peppol PINT wildcard handling. It must be set in oxalis.conf as shown:
# For T0 status (before 15 May) - Default value
oxalis.pint.wildcard.migration.phase=0
# For T1 (May 15th, 2025, onward): - Set value to 1 on/after May 15th, 2025
oxalis.pint.wildcard.migration.phase=1
# For T2 (~August 27th, 2025/TBD): - "busdox scheme exact match" in PINT messages will be removed in T2. You will start getting error message with phrase "...or SMP registration is not valid" when trying to send PINT message with "busdox scheme"
oxalis.pint.wildcard.migration.phase=2
For PINT documents. always use "peppol-doctype-wildcard" as Document Type Identifier Scheme in SBDH otherwise default "busdox-docid-qns" value will be considered. This can lead to SMP lookup error if SMP registration is only available with "peppol-doctype-wildcard" and you are Not providing Document Type Identifier Scheme in SBDH. Additionally, the new exact match identifier option in the wildcard scheme is introduced but cannot be used before T1 i.e. no capability registrations with that scheme may be made before T1. For details, refer "PINT Wildcard Migration Plan"
- Added code to set HTTP version with default value '1.1'. You can also configure [OPTIONAL] it in oxalis.conf as:
oxalis.http.version=1.1
- Removed outdated FRPOC support
- Fixed expired dummy AP certificates
- Bump peppol-specifications from 2.3.0 to 2.4.0
- Bump vefa-peppol version from 3.8.0 to 4.0.0
- Bump bouncycastle from 1.78.1 to 1.80
- Bump guava from 33.3.1-jre to 33.4.0-jre
- Bump joda-time from 2.12.2 to 2.13.0
- Bump slf4j from 2.0.6 to 2.0.17
- Bump logback from 1.5.6 to 1.5.16
- Bump lombok from 1.18.24 to 1.18.32
- Bump httpclient, from 4.5.13 to 4.5.14
- Bump typesafe from 1.4.2 to 1.4.3
- Corrected jakarta.servlet-api.version
- Get rid of possibly unnecessary exclusion from POM dependencies
NOTE: Please note that this release contains a known issue that may occur in multi-threaded environments. A new version, Oxalis-NG 1.2.0, addressing this issue will be released soon
Full Changelog: v1.0.0...v1.1.0
Oxalis-NG v1.0.0
What's Changed
- Major version i.e. incompatible with previous version due to package name change & major restructuring
- Built on top of Oxalis/Oxalis-AS4 7.0.0, so everything which is there in Oxalis/Oxalis-AS4 7.0.0 is also in "Oxalis-NG"
- Require upgrade to Tomcat 10.1.x
- Run with all Java versions starting 11 to 21
- Removed support for AS2 protocol, which is No longer supported by Peppol since 2020
- Merged "Oxalis-AS4" with Oxalis Core and these are now maintained in one single repository - "Oxalis-NG"
- Added check in inbound component to verify whether incoming message belong to your AP
# Configure below properties in oxalis.conf in production environment (access.point.isReceiverCheckEnabled=true), if you as receiving AP want to verify whether incoming messages belong to you as per your SMP registration. For Point-to-Point/simulated environment, set access.point.isReceiverCheckEnabled=false
access.point.isReceiverCheckEnabled=false
my.access.point.url="http://api.example.com/oxalis-ng/as4"- Additionally, you can now add your AP logo and AP name in Home page by configuring below properties in oxalis.conf
access.point.name="YOUR_AP_NAME_HERE"
access.point.logo="YOUR_AP_LOGO_HTTPS_URL_HERE"- Bump CXF version to 4.0.6
- Bump wss4j version to 3.0.4
- Bump neethi version to 3.2.1
- Bump commons-io version to 2.18.0
- This version still contains legacy components/modules like "Oxalis Statistics", "Oxalis Persistence " and "Oxalis Document Sniffer"
- Until 31st December 2025, both Oxalis 7.x.x. & Oxalis-NG will be maintained. After that only Oxalis-NG will be maintained
- Documentation is now moved to https://github.com/OxalisCommunity/oxalis-ng/wiki
Oxalis-NG v1.0.0-RC1
What's Changed
- Major version i.e. incompatible with previous version due to package name change & major restructuring
- Built on top of Oxalis/Oxalis-AS4 7.0.0, so everything which is there in Oxalis/Oxalis-AS4 7.0.0 is also in "Oxalis-NG"
- Removed support for AS2 protocol, which is No longer supported by Peppol since 2020
- Merged "Oxalis-AS4" with Oxalis Core and these are now maintained in one single repository - "Oxalis-NG"
- Added check in inbound component to verify whether incoming message belong to your AP
# Configure below properties in oxalis.conf in production environment (access.point.isReceiverCheckEnabled=true),
# if you as receiving AP want to verify whether incoming messages belong to you as per your SMP registration.
# For Point-to-Point/simulated environment, set access.point.isReceiverCheckEnabled=false
access.point.isReceiverCheckEnabled=false
my.access.point.url="http://api.example.com/oxalis-ng/as4"
- Additionally, you can now add your AP logo and AP name in Home page by configuring below properties in oxalis.conf
access.point.name="YOUR_AP_NAME_HERE"
access.point.logo="YOUR_AP_LOGO_HTTPS_URL_HERE"
- Bump CXF version to 4.0.6
- Bump wss4j version to 3.0.4
- Bump neethi version to 3.2.1
- Bump commons-io version to 2.18.0
- Current RC version still contains legacy components/modules like "Oxalis Statistics", "Oxalis Persistence " and "Oxalis Document Sniffer".
- Until 31st December 2025, both Oxalis 7.x.x. & Oxalis-NG will be maintained. After that only Oxalis-NG will be maintained
Full Changelog: v0.2.0-beta...v1.0.0-RC1
Oxalis-NG v0.2.0-beta
What's Changed
- Major version i.e. incompatible with previous version due to package name change & major restructuring
- Built on top of Oxalis/Oxalis-AS4 7.x, so everything which is there in Oxalis/Oxalis-AS4 is also in "Oxalis-NG"
- Removed support for AS2 protocol, which is No longer supported by Peppol since 2020
- Merged "Oxalis-AS4" with Oxalis Core and these are now maintained in one single repository - "Oxalis-NG"
- Current beta version still contains legacy components/modules like "Oxalis Statistics", "Oxalis Persistence " and "Oxalis Document Sniffer".
- Until 31st December 2025, both Oxalis 7.x.x. & Oxalis-NG will be maintained. After that only Oxalis-NG will be maintained
Full Changelog: v0.1.0-alpha...v0.2.0-beta
Oxalis-NG v0.1.0-alpha
What's Changed
- Major version i.e. incompatible with previous version due to package name change & major restructuring
- Built on top of Oxalis/Oxalis-AS4 7.x, so everything which is there in Oxalis/Oxalis-AS4 is also in "Oxalis-NG"
- Removed support for AS2 protocol, which is No longer supported by Peppol since 2020
- Merged "Oxalis-AS4" with Oxalis Core and these are now maintained in one single repository - "Oxalis-NG"
- Current alpha version still contains legacy components/modules like "Oxalis Statistics", "Oxalis Persistence " and "Oxalis Document Sniffer". But these legacy components/modules will be removed (TBC).
- For some time both Oxalis 7.x.x. & Oxalis-NG will be maintained together. But after 31st December 2025, only "Oxalis-NG" will be maintained for Peppol.