Unless the following line is a typo and not what is actually in your 
config file, it could be part of the problem.

<amf-https-gateway>http://steve.mybox.com/amfgateway</amf-gateway>

The closing tag should be "</amf-https-gateway>".


--- In [email protected], "stevenkeys2003" <[EMAIL PROTECTED]> 
wrote:
>
> Hey guys, 
> I'm in the process of converting my existing ro's to named ro's.
> (We're   running from multiple servers, each with it's own flex
> server. Each server obviously having it's own gateway and endpoint
> paths. Because of this it's been a real hassle pushing stuff with 
all
> hardcoded ro's in mxml) We're a CF shop and running coldfusion 
cfcs on
> the bakend. Before I had everything specified in the ro, endpoint,
> protocol, etc. Now that I've split it out to a named ro, I can't 
get
> things working. I am compiling from cmd line with mxmlc on 
commercial
> flex 1.5.
> 
> Error:
> Warning: Could not set protocol to https.  You must set https-url 
to a
> non-relative https value for RemoteObject in flex-config.xml or set
> gatewayHttpsUrl to a non-relative https value when using mxmlc.
> 
> I don't understand this error as flex-config doesn't allow https-
url
> in the remote-objects section.
> 
> Example of mxml I'm using:
> <mx:RemoteObject id="roGetAllDiscounts" named="roGetAllDiscounts"
> protocol="https" showBusyCursor="true">
>       <mx:method name="getDiscount"
> fault="mx.controls.Alert.show(event.fault.faultstring, 'Alert');"
> result="roGetAllDiscountsHandler(event.result)"/>
> </mx:RemoteObject>
> 
> Example of named call in ro whitelist:
> <object name="roGetAllDiscounts">                          
> <source>app.machii.model.flexOnlineSignup</source>
> </object>
> 
> 
> Gateways for this instance:
> (local dev box)
> 
>  <amf-gateway>http://steve.mybox.com/amfgateway</amf-gateway>
>  <amf-https-gateway>http://steve.mybox.com/amfgateway</amf-gateway>
> 
> The domain I typed above is fake, as it's something similar that
> points to my local machine from our company's dns. I'm trying to 
cheat
> in the https gatway line because I technically don't have a cert 
on my
> local dev box, where as the production server does. With the idea 
of
> being able to leave in procol="https" in the actual mxml for every
> version. (both local and production).
> 
> So my question is.. how do I make a named remote object call work 
over
> https? AND can I legally use a http url for an <amf-https-gateway>?
> 
> Before the example above was this in mxml:
> 
> <mx:RemoteObject id="roGetAllDiscounts" protocol="https"
> endpoint="https://secure.xxx.com/flashservices/gateway";
> source="app.machii.model.flexOnlineSignup" showBusyCursor="true">
>       <mx:method name="getDiscount"
> fault="mx.controls.Alert.show(event.fault.faultstring, 'Alert');"
> result="roGetAllDiscountsHandler(event.result)"/>
> </mx:RemoteObject>
> 
> Thx
> -Steve
>






------------------------ Yahoo! Groups Sponsor --------------------~--> 
Great things are happening at Yahoo! Groups.  See the new email design.
http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~-> 

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
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/
 



Reply via email to