What's new in WIFE 7.3
Apr 15, 2014
- removed log4j.properties
- New API
- com.prowidesoftware.swift.model.field.Field.isAnyOf(String...)
- many methods in SwiftTagListBlock in resemblance to String manipulation API
- SwiftTagListBlock
- Added
- getTagsByNumber(int)
- SwiftTagListBlock removeAfterFirst(String, boolean)
- Tag.startsWith
- Tag.contains
- com.prowidesoftware.swift.io.PPCFileReader iterator to read and split pc connect files
New in WIFE 7.2 (Apr 15, 2014)
- New API
- Field.letterOption
- SwiftTagListBlock.getSubBlockBeforeFirst
- SwiftTagListBlock.filterByName
- Fixes:
- Field.appendInLines that was causing the getValue of several fields (ex 35B) to start with unexpected EOL
- NPE in XMLParser with null value in tags
- Avoid usage of double in amount resolver
New in WIFE 7.0 (Apr 15, 2014)
- ENHACENMENTS:
- Enhanced messages model with base support for MX messages.
- New messages meta-data model to handle additional information
- Status history
- User notes
- Properties list.
- Useful API to SwiftMessage to get: direction, PDE, PDM, UUID, MIR, MUR and getTypeInt
- Complete FieldNN implementation classes
- Complete MT helper classes, covering all message types
- Added model and API to handle Sequences at MT classes, covering all sequences based on 16R/16S boundaries.
- New API to handle sub blocks
- SwiftTagListBlock.removeUntilFirst
- SwiftTagListBlock.containsAnyOf
- Ensuring of SWIFT EOL at ConversionService.getFIN
- FIXES:
- Fixed getValue of several fields to prevent printing of null
- Fixed getValue of several fields with missing slash separator on optional components
- Added missing field getters for MT classes with fieldsets: for example 93B at MT564.
- getValue for Field35B. Thanks to Raghu [email protected]
- getCalendar bug related to unused format parameter
- Changed Field26C parser and subfields structure to split the string before the VAR-SEQU into independent components
- OTHERS:
- Removed deprecated net.sourceforge classes
- Removed unimplemented method amounts() in AmountContainer
New in WIFE 6.4.1 (Apr 27, 2013)
- FIXES:
- Bugfix: getCalendar bug related to unused format parameter
- Changed Field26C parser and subfields structure to split the string before the VAR-SEQU into independent components
New in WIFE 6.4 (Apr 27, 2013)
- Added visitor API on tag list block
- New interface to identify and use generic fields (notice DSS methods are not part of non-generic fields)
- Added API on MT classes to simplify messages creation
- Comprehensive getters and setter API for field classes using functional names
- Added PatternContainer interface and implemented in field
- Better CurrencyContainer API
- Added API to SwiftFormatUtils to get String components from Calendar using different SWIFT date/time formats
- Implemented API for CurrencyContainer for all Fields
- Added MT helper classes for MTs: 518, 549, 800, 801, 802, 824, 600, 601, 604, 605, 606, 607, 608, 609
- Added Field implementations for 33G, 35U, 86B, 68A, 68B, 68C, 94C, 31F, 37a, 34J, 35H, 31X
- Added API to simplify messages creation; defaults for header blocks attributes, addField to Block4, setSender at Block1
New in WIFE 6.3 (Apr 27, 2013)
- Added MT helper classes for MTs: 500, 501, 502, 503, 504, 505, 506, 507, 508, 509, 510, 565
- Fixed getAsCalendar for year component of field 77H
- Fixed parsing of field 50F
- Added field class for: 26C
- Support to identify which sequence a tag belongs to
- Added API to FieldNN classes to get the DSS field
- Added API to FieldNN classes to get the qualifier and conditional qualifier components
- Added API to FieldNN classes to determine if field is generic or non generic
- Field class made abstract
- FieldNN isOptional: method to check if a given component is optional for the field
- Field getLabel: support for label exceptions per mt and sequence
- SwiftParser changes to distinguish the presence of brackets when they are block boundaries or part of an invalid field value
- Improved parsing of Field35B, first and second components are set only if "ISIN " is present
- SR2012 update: deprecated fields 23C, 23F. Updated MT300, MT304, MT305 with field changes.
- Added serialization for: 20E, 29G, 31G, 36E, 50G, 50H, 69B, 69D, 69F, 77H, 90F, 90J, 90K, 92D, 92L, 92M, 92N, 94D, 94G, 95T, 98F
- Fixed serialization of field 59A
New in WIFE 6.2 (Apr 27, 2013)
- Purged and some tunning of parser log
- Added getField* API con block4
- Added Tag API: public boolean contains(String ... values)
- Added more API to get subblocks based on tag number boundaries regardless of letter options
- Fixed Tag.isNumber to consider the whole number and not just the prefix, isNumber(58) returns true to 58A but not to 5
- Added Tag.getNumber() API
- Fixed build to include MTs and FieldNN source codes in the package
- Fixed parser for fields: 94D, 50H, 50G and 52G
- Added MT helper classes for MTs: 567, 900, 910, 920, 935, 941, 970, 971, 972, 973, 985, 986
- Added API for getLabel at Field objects, to retrieve business oriented names from resource bundles
New in WIFE 6.1 (Apr 20, 2012)
- Added API for getLabel at Field objects, to retrieve business oriented names from resource bundles
- Added BICContainer interface
- Added MT helper classes for MTs: 360, 361, 362, 364, 365, 381, n90, n92, n95, n96, n98, 420, 422, 430, 450, 455, 456, 701, 705, 711, 720, 721, 732, 734, 740, 742, 747, 750, 752, 754, 756, 768
- Added getValue for Field13E
- Fixed getValue for Field31R (2nd component is optional)