APAR PK40102 includes the following fixes. PK41931 ======== Problem 1 Description: When the inputMode attribute is set to inputMode="hiragana" within the xftextinput tag, it is not converted to the attribute istyle="2" within the input tag during runtime. This only happens when it is set to inputMode=" hiragana", it works fine for other values for inputMode. Problem 1 Solution: Code Fix PK40102 ======== Problem 2 Description: When Using emoji in xdime pages and portlets causes java.lang.ArrayIndexOutOfBoundsException. Problem 2 Solution: Code Fix Additional fixes included with this update. =========================================== Problem 3 Description: Field validation not working properly a) one is with XDIME code (logon.jsp) b) two is the file translated to the XHTML by (logon.html). The information about the Validation property from the Infocenter does not work. Problem 3 Solution: Code Fix Problem 4 Description: Request a page with the following e.g wget http://localhost/8080/pageName.xdime -U 'N'

simple test page

 Problem 4 Solution: Code Fix Problem 5 Description: If xftextinput is used with maxLength="2" and validate="n:*#" MCS generates HTML where in the section there is a link to missing scripts/validate.js file. (Even if the file were present somewhere, the link is relative to the current page which could be something like /wps/myportal/!ut/p/wml/Rw!! and the browser will look for file /wps/myportal/!ut/p/wml/scripts/validate.js which does not seem correct.) Problem 5 Solution: Code Fix Affected Users: Mobile users Pre-Requisite(s): WebSphere Everyplace Mobile Portal Version: 5.1 or 5.1.0.1 WebSphere Everyplace Mobile Portal Fixes: None WebSphere Portal Fixes: None Installation: NOTE: YOU MUST FIRST DOWNLOAD THE WEBSPHERE PORTAL UPDATE INSTALLER TOOL FOR VERSION 5.0.x IN ORDER TO INSTALL A FIX. The Portal Update Installer can be downloaded from the following link: http://www.ibm.com/software/genservers/portal/support 1. Create temporary "fix" directory to store the jar file. 2. Copy jar file to this directory. 3. Shutdown WebSphere Portal. 4. Follow the fix installation instructions that are packaged with the Portal Update Installer on how to install the fix. 5. Restart WebSphere Portal. 6. The temporary directory may be removed. NOTE: FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED FIX. 1. Shutdown WebSphere Portal. 2. Follow the instructions that are packaged with the Portal Update Installer on how to uninstall the fix. 3. Restart WebSphere Portal.