| This table lists the enhancements and fixes in interim fix version 6.1.0.1_IF01. |
| Enhancements |
| There are no enhancements in this interim fix. |
| Fixes |
| 1 | 95827 | Internal | 'fileContentEncoding' value is not considered for Japanese characters. |
| Symptom: FlatFile adapter is not using 'fileContentEncoding' value in the outbound create scenario.This was found when testing with Japanese encoding value. |
| Resolution: This has been fixed. FlatFile adapter uses the 'fileContentEncoding' value specified. |
|
| 2 | 96384 | JR29022 | Interaction spec setting of 'CreateFileIfNotExists' is not usable |
| Symptom: If a wrapper xsd exists for an input type, boolean values set on the interaction spec are never taken into consideration. It will always take whatever value is set on the wrapper -- false, if no value is set. Only if the wrapper did not exist, the interaction spec values were considered. |
| Resolution: This has been resolve. If no values are set for boolean properties in the wrapper, the adapter will take the value for that property from the interaction spec. |
|
| 3 | 96252 | JR29166 | The WebSphere adapter for Flat Files does not convert escape sequences in the end BO delimiter. |
| Symptom: When we use escape sequences like \r etc in the end BO delimiter while doing a outbound, the adapter does not convert the sequence to its equivalent control character. The exact text is appended instead of the control character. |
| Resolution: This has been fixed. |
|
| 4 | 75676 | Internal | Working with binary files during inbound processing. |
| Symptom: Earlier, there was no way the adapter could process binary files during inbound processing. The fix provided for CR 95676 did provide a way to deal with binary files but it was not backward compatible. |
| Resolution: In the valid values for the fileContentEncoding activation spec property, a new value namely, 'BINARY' has been added. Users need to choose this value for the fileContentEncoding property for processing binary files. If no value is set for this property, by way of removing the value from the admin console, UTF-8 would be used as the default value. |
|
| This table lists the enhancements and fixes in fix pack version 6.1.0.1. |
| Enhancements |
| 1 | 75294 | Internal | Support for recursive polling of subdirectories within the event directory |
| Symptom: The adapter does not poll files in subdirectories within the event directory. |
| Resolution: With this enhancement, the adapter can recursively poll files in subdirectories within the event directory. To enable recursive polling, you must enable the activation specification property 'Poll subdirectories' in event directory. |
|
| Fixes |
| 1 | 95432 | Internal | Access to sequence file does not appear to be thread safe |
| Symptom: When multiple requests are sent for creating files with sequence, exceptions occur due to a file that already exists or to multiple entries for same file in the sequence file. |
| Resolution: The access to the sequence file was not synchronized. This has been fixed. |
|
| 2 | 95360 | Internal | NullPointer exception is generated when the 'Split file content based on size' property is deselected using the pattern wizard. |
| Symptom: If you deselect the 'Split file content based on size' property in the pattern wizard, the 'Split function class name' property is not disabled and a NullPointer exception is generated. |
| Resolution: The 'Split function class name' property is now disabled when the 'Split file content based on size' property is deselected. |
|
| 3 | 95356 | Internal | DuplicateRecordException exception occurs when using sequence file |
| Symptom: When sequencing is enabled, Adapter for Flat Files throws a DuplicateRecordException exception in the second attempt to write the sequence file. |
| Resolution: The access to the sequence file was not synchronized. This has been fixed. |
|
| 4 | 95357 | Internal | When used in inbound mode, the adapter generates a Failed to transform Record to a DataObject instance error |
| Symptom: When running Adapter for Flat Files in inbound mode using an adapter pattern, the following error occurs: Failed to transform Record to a DataObject instance. |
| Resolution: This problem has been fixed. |
|
| 5 | 91346 | Internal | The value of 'Retrieve files in sorted order' should not be globalized |
| Symptom: In the External Service Wizard window in inbound mode, the value of the property 'Retrieve files in sorted order' is displayed as a globalized value. During the runtime processing, the adapter compares 'Retrieve files in sorted order' property values with predefined constant values. However, when it finds the globalized value, it cannot continue because the globalized value does not match any of the predefined constant English values. |
| Resolution: This has been fixed and now only the predefined constant values, not the globalized value, are shown in the enterprise service wizard window. |
|
| 6 | 95834 | JR28548 | A java.lang.NegativeArraySizeException exception is generated when processing large files |
| Symptom: When an event file with a size of 2 GB or more is processed with the SplitBySize option, a java.lang.NegativeArraySizeException exception is generated. |
| Resolution: The problem with the adapter not handling file sizes correctly using the appropriate primitive types has been resolved. |
|
| 7 | 96147 | JR29022 | Assured once delivery does not work as expected |
| Symptom: If an error occurs after an event is delivered to the endpoint, the event stays in the event table with status of 1. When the adapter is restarted, the event is processed again and is resent to the endpoint. |
| Resolution: After events have been delivered to the endpoint, the entries are deleted from the event table even if an error occurs after the event is delivered. |
|
| 8 | 75390 | JR28713 | When custom file splitting is implemented, setSplitCriteria method returns NULL |
| Symptom: The adapter does not forward the Split Criteria attribute to the setSplitCriteria method because it is not hardcoded in the custom file splitter implementation. |
| Resolution: This problem has been fixed. |
|
| 9 | 75391 | JR28668 | On AIX(R), the adapter cannot extract event files in mounted folder by CIFS (Common Internet File System). |
| Symptom: The adapter cannot extract XML files from the local folder that mounts the remote shared Windows folder with the CIFS (Common Internet File System) mechanism. |
| Resolution: Fixed. |
|
| 10 | 95547 | Internal | Outbound performance regression issue due to CR 95432 changes |
| Symptom: The big lock, which covers a large piece of the Create method in the FlatFileBridge file, is causing worker threads to spin while waiting their turn to run. |
| Resolution: This problem has been fixed. |
|
| 11 | 91770 | Internal | No error is generated for the Exists operation when the file name is set to null |
| Symptom: The adapter does not generate an error for the Exists operation when the file name is set to null. |
| Resolution: The adapter generates a MissingDataException exception for the Exists operation when the file name is set to null. |
|
| 12 | 75392 | Internal | Assured Once Delivery not functioning after loss of connection to the event directory |
| Symptom: After losing its connection to the event directory, the adapter not only picks up events marked with -1 for a second and third time, but it also picks up events that were already delivered. |
| Resolution: This problem has been fixed. |
|
| 13 | 74626 | Internal | GlobalizationUtil class not being used for string manipulation |
| Symptom: The adapter does not use the GlobalizationUtil class provided by the Adapter Foundation Classes, which ensures a uniform and efficient way to use the icu4j APIs for string manipulation. |
| Resolution: This problem has been fixed. |
|
| 14 | 91564 | Internal | Interaction property target file name should take precedence over managed connection factory properties. |
| Symptom: During a Retrieve operation, the interaction spec property value does not take precedence over the managed connection factory property value for the output file name. |
| Resolution: This problem has been fixed. |
|
| 15 | 91584 | Internal | 'Type of delivery' property should not have ORDEREDBYKEY option |
| Symptom: The Inbound enterprise service discovery wizard property 'Type of delivery' has 'ORDEREDBYKEY' as one of the values; however, because technology adapters do not use this value, it should be removed from the list. |
| Resolution: The value ORDEREDBYKEY has been removed from the list. |
|
| 16 | 91594 | Internal | Error in getBaseInputStreamRecord method of FlatFileBaseDataBinding |
| Symptom: The element names does not match the UnstructuredContent object attributes. 'asText' needs to be changed to 'AsText', and 'asBinary' needs to be changed to 'AsBinary'. |
| Resolution: This problem has been fixed. |
|
| 17 | 90947 | Internal | Message text is misleading |
| Symptom: The message text for error message CWYFF0022F incorrectly states that the specified values for SortEventFiles are Filename, Timestamp, and BLANK. |
| Resolution: This has been fixed. The valid values for SortEventFiles are File name, Time stamp, and No Sort. |
|