Quantcast
Channel: VMware Communities: Message List - VMware vCloud Director
Viewing all articles
Browse latest Browse all 7719

Re: vCloud 5.1 SDK i18n

$
0
0

Hello,

 

After a investigating this in more detail, I've came to the following conclusion:

 

The vCloud Java SDK 5.1 uses the default JVM encoding when it builds the request xml.

 

I have tested the following code:

             AdminOrganization aOrg = getAdminOrganization(organizationName)

            AdminCatalogType catalogType = new AdminCatalogType();
            catalogType.setName(catalogName);
            catalogType.setDescription(desc);
            catalogType.setIsPublished(isPublished);

 

            aOrg.createCatalog(catalogType)

 

If it executed in a JVM with default encoding "UTF-8" - the code works just fine with japaneese characters.

If the same code is executed in a JVM with default encoding "windows-1252" - the request body is built wrong.(the string "カタログ" is transformed in "カタログ").

 

The default character set of the JVM is that of the system it's running on.

So, after this investigation, my assumption is that the Java SDK is dependent on the system it is running on.

 

Is there a way i can force the sdk not to use the default JVM charset?

 

Thank you,

Corneliu


Viewing all articles
Browse latest Browse all 7719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>