Mustangproject version 2.16.4, released April 22nd, 2025, features 16 small corrections, two of which may be potentially security sensitive and fixes a small resource leak.
There is a known issue (#764),
which may be addressed in 2.17.0, potentially in May, maybe along with an update to support ZF 2.3.3 (i.e. Codelist version 15): The question being if absolute, i.e. non-percentual, item based discounts/charges are not to be multiplied by the quantity, as they currently are in Mustang. If that is true I will need to correct not only the calculation, but also some tests, and you may see different invoice amounts in some cases.
New features in 2.16.4
- #818 need to be able to specify filenames as exceptions from files validated recursively with validateExpectValid
- #741 read position accountingReference
- #809 invoice reader to support multiple charges per item
- #812 fileattachment relation should have a default
Fixes
- #774 disable XML parsing entities (potentially security sensitive, potentially partially revoked after merge due to failing tests)
- #778 Added XEE Protection features (potentially security sensitive, potentially partially revoked after merge due to failing tests)
- #742/#753 “Adresszusatz 1” (LineTwo) showing up as “Postfach” in HTML visualization
- #614, #770 Exemption reason text should not be reused
- #728 Invoice setCorrection causes duplicate XML output
- #776 Fix potential resource leaks in core file processing classes
- #782/771 prevent NullPointerException on Product Description
- #772 TradeParty Name should be optional for ShipToTradeParty
- #775 not deleted tmp files
- #802 fix: capital letter for ID in listID
Refactorings
- #759 Use the dedicated class instead of var type
- #722 extend ValidationLogVisualizer to not use only file system