Frinje implements the Model component of the MVC architecture as an ActionScript proxy class and associated data objects. The proxy class handles communication with Java services that run on the vSphere Web Client Virgo server framework, as part of the vSphere Web Client service layer.

For most data view extensions that you create, you do not need to implement the proxy class yourself. The vSphere Web Client SDK provides a Flex library called the Data Access Manager, which handles all communications tasks with the Java services running in the vSphere Web Client service layer. For more information about the Data Access Manager library, see Using the Data Access Manager Library.

You only need to implement the proxy class if you created your own custom Java service and added that service to the vSphere Web Client service layer. Any proxy class you create must extend the com.vmware.flexutil.proxies.BaseProxy class in the vSphere Web Client SDK.

The following sample proxy class calls the simple EchoService service in the vSphere Web Client service layer.

public class EchoServiceProxy extends BaseProxy {
    private static const SERVICE_NAME:String = "EchoService";
 
    // channelUri uses the Web-ContextPath define in MANIFEST.MF (globalview-ui)
    private static const CHANNEL_URI:String = ServiceUtil.getDefaultChannelUri(GlobalviewModule.contextPath);
 
    /**
    * Create a EchoServiceProxy with a secure channel.
    */
    public function EchoServiceProxy() {
      super(SERVICE_NAME, CHANNEL_URI);
    }
 
    /**
    * Call the "echo" method of the EchoService java service.
    *
    * @param message Single argument to the echo method
    * @param callback Callback in the form <code>function(result:Object,
    * error:Error, callContext:Object)</code>
    * @param context Optional context object passed back with the result
    */
    public function echo(message:String, callback:Function = null, context:Object = null):void {
      callService("echo", [message], callback, context);
    }
}