The release of this document for JText connector version
4.2.x contains the following new or corrected information:
- Support has been added for dynamic child meta-objects. The
connector can now be configured to use wrapper objects or dynamic child
meta-objects for dynamic file specification. See Using a dynamic child meta-object for details.
- The EventDataHandler and OutputDataHandler
meta-object attributes have been added to allow the connector to directly
invoke data handlers rather than invoke them via the
DataHandlerFormatter. You may use these attributes to directly specify
a data handler in the JText connector meta-object rather than indirectly
within the DataHandlerFormatter's meta-object. See Table 13 for details.
- The new user option None has been added for configuring the
EndBODelimiter meta-object attribute when outputting business
objects to a file without any EndBODelimiter or newline
character. See Table 15 for details.
- The DataEncoding meta-object attribute has been added to allow users to
specify the UTF8 encoding instead of the default UTF7. See Table 13 for details.
The release of the document for JText connector version 4.1.x
contained the following new information:
- The connector's archiving feature has been redesigned.
- The naming convention for formatter meta-objects has changed.
- Important:
- It is recommended that you use only data handlers and not formatters for
business-object processing.
- The CwJTFormatter.jar file is no longer
distributed.
- The format and use of the event.log file has
changed.
- The process of specifying a data handler has been clarified and
corrected.
- The descriptions of event notification and data handler processing have
been clarified and corrected.
- A new section on creating custom meta-objects has been added.
- The sections Problem with event triggering and JText failure handling have been clarified and corrected.
