Solved: Encoding UTF-8 WebEx XML API (java)

stephane.mathieu · ‎11-21-2017

Hello,

Have you ever faced any issues with the UTF8 encoding? Probably I am missing something but I've tried to create a meeting with some special characters (French characters) in the conference title. The encoding type has been specified in both XML message and Http connection; however WebEx displays strange characters in the web interface.

urlConnectionXMLServer.setRequestProperty("Accept-Charset", "UTF-8");
urlConnectionXMLServer.setRequestProperty("Content-Type", "application/xml; charset=UTF-8");

<?xml version="1.0" encoding="UTF-8"?>

<serv:message xmlns:serv="http://www.webex.com/schemas/2002/06/service" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.webex.com/schemas/2002/06/service">

</securityContext>

</header>

<body>

</accessControl>

...

The java environment (JVM + editor) has been set up to use UTF-8, and when enabling the debug options(-Djavax.net.debug=all) I can see that the characters are correctly encoded (é --> C3A9)?

Many thanks in advance for any help ;-)

nmorrow · ‎11-21-2017

Hello,

UTF-8 is the preferred encoding method for XML API and WebEx does support localization. The issue may involve a missing language pack in your OS or an English only WebEx site. You should be able to confirm the XML API capability by calling GetMeeting on the scheduled meeting and compare the confName returned to the value that you set when scheduling. You may also try manually scheduling a meeting with the same name directly on the site through your browser to see if it is set properly. Finally, there may be some remaining issue in the JAVA environment that causes a different encoding to be used at some stage in the process.

View solution in original post

nmorrow · ‎11-21-2017

Hello,

UTF-8 is the preferred encoding method for XML API and WebEx does support localization. The issue may involve a missing language pack in your OS or an English only WebEx site. You should be able to confirm the XML API capability by calling GetMeeting on the scheduled meeting and compare the confName returned to the value that you set when scheduling. You may also try manually scheduling a meeting with the same name directly on the site through your browser to see if it is set properly. Finally, there may be some remaining issue in the JAVA environment that causes a different encoding to be used at some stage in the process.