That 500 error will be fixed in FDS 2.5 and ColdFusion 8, and yes, I'd share your concerns with the ColdFusion team about the gateway mapping name (that said, you can change this servlet mapping in /WEB-INF/web.xml to be anything you want, however... it's just a default though I imagine many users don't want to get into the nitty-gritty of J2EE web application configuration).
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of rchadgray Sent: Wednesday, March 21, 2007 5:06 PM To: [email protected] Subject: [flexcoders] Re: flash remoting AH HA! after playing around some i found you need the trailing slash after flex2gateway. So now it works with this line: <mx:RemoteObject id="cfc_ro" destination="ColdFusion" source="remotingExample" showBusyCursor="true" endpoint="http://demo.dev/flex2gateway/ <http://demo.dev/flex2gateway/> "> Thanks again Clint and Pete for all of the help! Adobe -- PS. isnt it a bad idea to use use flex2gateway? What happens when Flex 3 comes out? --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "rchadgray" <[EMAIL PROTECTED]> wrote: > > hmmmm If i hit http://demo.dev/flex2gateway <http://demo.dev/flex2gateway> with a web browser i get > a 500 Internal Server error in my browser. > > The apollo app spews a huge error if i set > endpoint="http://demo.dev/flex2gateway <http://demo.dev/flex2gateway> " > > here is a part of it: > > fault = (mx.rpc::Fault)#14 > errorID = 0 > faultCode = "Client.Error.MessageSend" > faultDetail = "Channel.Connect.Failed error > NetConnection.Call.Failed: HTTP: Status 500: > url: 'http://demo.dev/flex2gateway <http://demo.dev/flex2gateway> '" > faultString = "Send failed" > message = "faultCode:Client.Error.MessageSend faultString:'Send > failed' faultDetail:'Channel.Connect.Failed error > NetConnection.Call.Failed: HTTP: Status 500: > url: 'http://demo.dev/flex2gateway <http://demo.dev/flex2gateway> ''" > name = "Error" > rootCause = (Object)#15 > code = "NetConnection.Call.Failed" > description = "HTTP: Status 500" > details = "http://demo.dev/flex2gateway <http://demo.dev/flex2gateway> " > level = "error" > > > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Peter Farland" <pfarland@> > wrote: > > > > There are two "remoting" technologies available in ColdFusion. > > > > There is Macromedia Flash Remoting which was also included in > ColdFusion > > MX. This is retained today in CF for backwards compatibility for > older > > Flash Remoting clients and Flex 1.0 and Flex 1.5 applications, > although > > Flex 2 does not target this technology. In CF, the old Flash > Remoting > > gateway is typically configured on the CF server at > > /flashservices/gateway. > > > > Adobe Flex Data Services 2 includes a Remoting Service that is also > > available in ColdFusion 7. Flex 2's RemoteObject is designed to > talk to > > this new service and includes support for new data types made > available > > in ActionScript 3.0. Flex Data Services is built on top of a > messaging > > framework so it sends messages back and forth between the client and > > server. The remoting service is provided by a message broker and is > > typically configured on the CF server at /flex2gateway. I imagine > that > > you've contacted a legacy endpoint such as the old Flash Remoting > > gateway and did not receive a message (but perhaps a raw result)... > > hence the failure. > > > > Pete
