As vSphere 6.0 is about to go GA here are two important reminders that will ensure that your Web Client plugin built with SDK 5.5 works correctly with 6.0. Failure to do so will generate errors such as "Unable to load resource module from /myplugin-ui/locales/myplugin-ui-en_US.swf", or invalid proxy calls, because of the reverse-proxy used in vSphere 6.0.
This information has been included in the SDK Release Notes since the 5.5 version. Be sure to read the full SDK 6.0 Release-Notes.html when you download the new SDK.
1) All UI plugins Web-ContextPath must use the format vsphere-client/plugin-name in MANIFEST.MF, i.e. be prefixed with vsphere-client, in anticipation of the 6.0 release where this will be required.
2) Plugins using java proxies must have two default channels in war/src/main/webapp/WEB-INF/flex/remote-config.xml and war/src/main/webapp/WEB-INF/flex/services-config.xml, "amf" and "secure-amf" as shown below:
<service id="remoting-service"
class="flex.messaging.services.RemotingService">
<adapters>
<adapter-definition id="java-object"
class="com.vmware.vise.messaging.remoting.JavaAdapterEx"
default="true"/>
</adapters>
<default-channels>
<channel ref="secure-amf"/>
<channel ref="amf"/>
</default-channels>
</service>
<services-config>
<services>
<service-include file-path="remoting-config.xml" />
<default-channels>
<channel ref="secure-amf"/>
<channel ref="amf"/>
</default-channels>
</services>
<channels>
<channel-definition id="secure-amf" class="mx.messaging.channels.SecureAMFChannel">
<endpoint url="https://{server.name}:{server.port}/{context.root}/messagebroker/amfsecure"
class="com.vmware.vise.messaging.endpoints.SecureAMFEndpoint" />
</channel-definition>
<channel-definition id="amf" class="mx.messaging.channels.AMFChannel">
<endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf"
class="com.vmware.vise.messaging.endpoints.AMFEndpoint" />
</channel-definition>
</channels>
...