Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
8.0.200.04 [10/07/10] – General | X | X | X | X | X | |
8.0.100.07 [03/09/10] – General | X | X | X | X | X | |
8.0.000.05 [07/24/09] – General | X | X | X | X | X |
This release note applies to all 8.0 releases of the Web Media Platform SDK for Java. For a list of other Java Platform SDK subcomponents, or to read general notes about this release of the Java Platform SDK, see the Platform SDK & Application Blocks for Java Release Note.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of the Web Media Platform SDK for Java.
This component has been updated to accommodate changes in the underlying libraries.
EspEmail Protocol — The Web Media Platform SDK now includes the EspEmail Protocol, which provides an improved way to handle the submission of web-based e-mail (including user data) to E-Mail Server Java using the RequestCreateWebEmailIn
and EventCreateWebEmailIn
messages.
When submitting content to E-mail Server Java, invalid characters can be removed according to the definition described at http://www.w3.org/TR/2000/REC-xml-20001006#NT-Char. Previously, such characters were transformed into invalid HTML characters that would prevent messages from being deserialized.
To enable this optional feature, do one of the following:
Update your code to configure the protocol connection based on this code snippet:
EmailProtocol protocol = new EmailProtocol(new Endpoint("emailServer", HOST, PORT));
PropertyConfiguration conf = new PropertyConfiguration();
conf.setBoolean(WebmediaChannel.OPTION_NAME_REPLACE_ILLEGAL_UNICODE_CHARS, true);
// "replacement" value is optional: if it is not specified - illegal characters will be removed
conf.setOption(WebmediaChannel.OPTION_NAME_ILLEGAL_UNICODE_CHARS_REPLACEMENT, "?");
protocol.configure(conf);
protocol.open();
Set the specific JVM property shown below for client applications using webmediaprotocol.jar
:
"-Dcom.genesyslab.platform.WebMedia.Email.replace-illegal-unicode-chars=true"
"-Dcom.genesyslab.platform.WebMedia.Email.replace-illegal-unicode-chars=true -Dcom.genesyslab.platform.WebMedia.Email.illegal-unicode-chars-replacement=?"
Setting JVM system properties will affect all WebMedia protocol connections, while values initialized with the configuration details programmatically take priority and only affect a single protocol instance.
Note 1: If no replacement character (string) is specified then characters will be replaced with an empty string.
Note 2: Values for the options pair are extracted independently. If you programmatically enable replacement without specifying a character, then the JVM system property will be checked for a replacement value. If the JVM value is also set, then characters will be replaced using that value instead of removed, without verifying that the option is enabled in the JVM properties. Genesys recommends using the two options together while writing connection configuration code, to prevent any unexpected behavior.
This release also includes the following corrections and modifications:
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of the Web Media Platform SDK for Java.
New chat requests and transcript events were added to the FlexChat and BasicChat protocols - allowing parties in a chat session to exchange special notifications such as typing on/off, push URL command, or custom and system notifications. These requests and events are different from regular messages; they use a separate Notice
node in the chat transcript, and make it possible to hide this activity from chat session participants. (ER# 232887025)
The PartyId
attribute is now supported in EventStatus
for the FlexChat protocol. (ER# 244544244)
This release also includes the following corrections and modifications:
There are no corrections or modifications in this release.
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of the Web Media Platform SDK for Java.
This release includes the following corrections and modifications that were made between Release 7.6 or earlier releases and the initial 8.0 release:
There are no corrections or modifications in this initial release.
This section provides the latest information on known issues and recommendations associated with this product.
There are no known issues in this release.