MACROMEDIA COLDFUSION MX 7.0.2-USING COLDFUSION MX WITH FLEX 2 Guida Utente Pagina 75

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 256
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 74
About the development environment 75
Using RPC service components with the Flex 2 SDK
only
You can use Flex 2 SDK without Flex Data Services to create applications that call HTTP
services or web services directly without going through a server-side proxy service. You cannot
use RemoteObject components without Flex Data Services. By default, Flash Player does not
allow an application to receive data from a domain other than the domain from which the
application was served. Therefore, an RPC service must either be in the same domain as the
server hosting your application, or the remote server that hosts the RPC service must define a
crossdomain.xml file.
A crossdomain.xml file is an XML file that provides a way for a server to indicate that its data
and documents are available to SWF files served from certain domains, or from all domains.
The crossdomain.xml file must be in the web root of the server that the Flex application is
contacting.
Using RPC service components with Flex Data
Services
Use Flex Data Services when you want to provide enterprise functionality, such as proxying of
service traffic from different domains, client authentication, whitelists of permitted RPC
service URLs, server-side logging, localization support, and centralized management of RPC
services. Flex Data Services also lets you use RemoteObject components to access remote Java
objects without configuring them as SOAP-compliant web services.
When you use Flex Data Services, instead of contacting services directly, RPC service
components contact destinations. Destinations are manageable service endpoints that you
manage through a server-side XML-based configuration file.
About the development environment
You store Flex Data Services server-side code and application files in the directory structure of
a standard web application on a J2EE-compliant application server or servlet container. The
MXML deployment model is similar to that of JavaServer Pages (JSPs). You create an MXML
file in the text editor of your choice, and place it in a web application directory that is
accessible from a web browser. For example, you can place MXML files in the web application
root directory or a subdirectory other than the reserved WEB-INF directory.
Vedere la pagina 74
1 2 ... 70 71 72 73 74 75 76 77 78 79 80 ... 255 256

Commenti su questo manuale

Nessun commento