Hi Dave,
to setup named remote objects with CF you'll need to
1) modify Flex's flex-config.xml file and CF's gateway-config.xml file (I
wondered to which file you are referring to when you say "CF FlexConfig.xml" as
there isn't such a thing)
2) adjust the structure of CF's gateway-config.xml file a bit to define your
named objects.
To point to the CF AMF gateway you can either use the endpoint on the
RemoteObject tag (the way you did) or chnage the <amf-gateway> setting in your
Flex's flex-config.xml (however, this changes the gateway for *all*
applications in your Flex server)
Then, you'll need to add a dummy named object entry in the flex-config.xml to
get the MXML compiled.
Next, you'll have to add the named object definition to the CF
gateway-config.xml file. In your case something like this:
...
<whitelist>
<unnamed>
<source></source>
</unnamed>
<named>
<object name="Echo">
<source>wwwroot.MYDOMAIN.model.user.User</source>
</object>
</named>
</whitelist>
...
restart your Flex and your CF server and you should be ready to go. Again, this
is described in detail here:
http://www.richinternet.de/blog/index.cfm?entry=831FE26E-0D70-9C2D-2549E1D1978CF1B0
Dirk.
-----Original Message-----
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] Behalf Of dave buhler
Sent: Thursday, June 02, 2005 7:57 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Cairngorm .99 + Flex-Config + Services.mxml
ooops..
Meant to post this WORKING code with the source inline.
Works
Services.mxml
<mx:RemoteObject id="loginService"
endpoint="http://localhost:8300/flashservices/gateway";
source="wwwroot.MYDOMAIN.model.user.User"
protocol="http"
showBusyCursor="true"
result="event.call.resultHandler( event )"
fault="event.call.faultHandler( event )">
</mx:RemoteObject>
Flex FlexConfig.xml
<object>
<source>*</source>
</object>
CF GatewayConfig.xml
Standard Setup
<whitelist>
<source>*</source>
</whitelist>
CF FlexConfig.xml
Standard Setup
Fails
Services.mxml
<mx:RemoteObject id="loginService" named="usersService"
endpoint="http://localhost:8300/flashservices/gateway";
protocol="http"
showBusyCursor="true"
result="event.call.resultHandler( event )"
fault="event.call.faultHandler( event )">
</mx:RemoteObject>
FlexConfig.xml
<object name="usersService">
<source>wwwroot.MYDOMAIN.model.user.usersService</source>
</object>
GatewayConfig.xml
Standard Setup
<whitelist>
<source>*</source>
</whitelist>
CF FlexConfig.xml
<remote-objects>
<amf-gateway>{context.root}/amfgateway</amf-gateway>
<amf-https-gateway>{context.root}/amfgateway</amf-https-gateway>
<allow-url-override>false</allow-url-override>
<whitelist>
<unnamed>
<source>*</source>
</unnamed>
<named>
<object name="usersService">
<source>*</source>
<!-- the type of the source being accessed - e.g.
stateful-class or stateless-class -->
<!-- <type>stateless-class</type> -->
<!-- instructs the gateway to only allow authenticated
users to invoke this service
this is required when using normal J2EE Basic
authentication -->
<!--
<use-basic-authentication>true</use-basic-authentication> -->
<!-- informs the gateway that is should attempt to use its
own custom authentication mechansim
as configured in the login-command section of
gateway-config.xml -->
<!--
<use-custom-authentication>true</use-custom-authentication> -->
<!-- Adds the service's source to the unnamed whitelist.
If false, these can never be used as unnamed sources -->
<!-- This will be forced to false if this named object
requires authentication -->
<!-- <allow-unnamed-access>true</allow-unnamed-access> -->
<!-- custom authorization roles can be specified when using
custom authentication -->
<!--
<roles>
<role></role>
</roles>
-->
<!-- </object> -->
</object>
<!-- </named> -->
</named>
</whitelist>
</remote-objects>
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
