[ http://issues.apache.org/jira/browse/BEEHIVE-1029?page=all ] Alejandro Ramirez closed BEEHIVE-1029: --------------------------------------
Verifed fixed with build synched to svn revision 365756. Executed repro steps and now I'm able to see the correct japanese UTF-8 character displayed. (Using both tomcat and wls) > Multibyte characters not supported correctly with the retrievePopupOutput for > NetUI tag. > ---------------------------------------------------------------------------------------- > > Key: BEEHIVE-1029 > URL: http://issues.apache.org/jira/browse/BEEHIVE-1029 > Project: Beehive > Type: Bug > Components: NetUI > Versions: V1, 1.1 > Reporter: Carlin Rogers > Assignee: Alejandro Ramirez > Fix For: 1.1 > Attachments: j1029-repro.zip > > Multibyte characters are not displayed correctly when the retrievePopupOutput > NetUI tag is used to configure a popup window and flow. The JavaSrcipt > written out to the popup window to close the window and pass the map back to > the opener window does not have correctly encoded Strings. > The problem is in the ReturnActionViewRenderer class which writes out the > Javascript for the map that is passed back to the opener window. The > response.getCharacterEncoding() needs to be set correctly to support the > unicode Java String that is to be written out as a value for the map. > The response for the popup window request in this case is strictly JavaScript > to pass a map back to the opener window, and then close the popup window. > There is now HTML to display to the user. I think it would be OK in this case > to call response.setContentType("text/html; charset=UTF-8") setting the > response character encoding to "UTF-8" before we begin writing the javascript > and map values. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
