|
|
This chapter describes how you invoke a service from a Flex client application and handle service results. To learn about the methods and properties of the services you want to invoke, see the LiveCycle ES API References.A service invocation can take zero or more input parameters and return zero or more output parameters. A Flex client application passes input parameters wrapped in an ActionScript object with fields that correspond to property names on the service. Any class that is remotely mapped to a Java class is passed to a LiveCycle ES operation as an instance of that Java class; for more information on mapping classes, see Explicitly mapping ActionScript and Java objects.If an ActionScript parameter is not remotely mapped, LiveCycle Remoting looks up the intended parameter type from the operation signature and attempts to coerce a flex.messaging.io.amf.ASObject instance on the Java side to the appropriate Java type. The ASObject object has a type property that contains the string name of the expected Java class. Other datatypes are also used, for example, process variables.A service result from the LiveCycle ES server is deserialized into an ActionScript object from which the Flex client application extracts specific output parameters by name.
Send me an e-mail when comments are added to this page | Comment Report
Current page: http://livedocs.adobe.com/livecycle/es/sdkHelp/programmer/sdkHelp/invokingLCRemoting.25.9.html