I’ve just added far better error handling for this condition. You can read all about it here:

http://swxformat.org/44

I am going to be releasing the new version of the SWX Service Explorer today with SWX Beta 1.2.

The version of the SWX Service Explorer in the SWX MAMP Bundle 1.2 will come with the correctly-configured URL.

For all other users, the Service Explorer should bring up the Preferences window the first time it is used so that you can set the correct Gateway URL for your server. This may not have happened for you if you had already used the AMFPHP service browser (as they were using the same shared object). I’ve now changed that too so that the SWX Service Explorer uses its own shared object (so there won’t be a conflict with the AMFPHP service browser).

Thanks so much again for reporting this and please do let me know if you continue to have issues with this or have any other problems.

Crap, I didn’t read the error message fully. The problem’s here:

details = “http://swxformat.org/php/gateway.php”

I only recently got the source for the service browser (it’s the same one in Amfphp but the source wasn’t in the tree) and only this week got round to actually updating it.

The problem is that it defaulted to the Amfphp default gateway (gateway.php). Since there are several gateways in SWX, including the SWX gateway (swx.php), JSON gateway (json.php), etc., I thought it made more sense to call the amf gateway amf.php. So the configuration URL for the service browser is pointing at the wrong gateway.

You can change this yourself by clicking the preferences/configuration button and changing gateway.php to amf.php.

In the latest version in SVN (http://svn1.cvsdude.com/osflash/swx/trunk), the default gateway is set to http://localhost:8888/php/amf.php (so that it works out of the box with the SWX MAMP Bundle without configuration).

Today, I’m going to capture the error you received and have the service browser (now SWX Service Explorer), handle it in a friendly manner.

Thanks again for letting me know about this. Please do update me as to whether you were able to get it to work by changing the gateway URL in the service browser.

Sorry - slow response cos I didn’t see your question…

Yeah, the error happens immediately I log on. Still happening now… Do you know of another remoting powered site I can try to see if it is the firewall here?

Very cool!

If you want help with the Jaiku API, check the devku channel at Jaiku.

Thanks for sharing

It might just be a firewall issue. The Service Browser uses flash remoting to connect to the service… hmm… I haven’t run into this and not sure how to recreate it.

Do you get the error the moment you log on?

Thanks!

I keep getting this error when I hit the service browser page:

(mx.rpc::Fault)#0
errorID = 0
faultCode = “Client.Error.MessageSend”
faultDetail = “Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed”
faultString = “Send failed”
message = “faultCode:Client.Error.MessageSend faultString:’Send failed’ faultDetail:’Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed’”
name = “Error”
rootCause = (Object)#1
code = “NetConnection.Call.Failed”
description = “HTTP: Failed”
details = “http://swxformat.org/php/gateway.php”
level = “error”

Not sure if it’s a firewall issue or something but I had the same problem yesterday. The internet in general seems to be working fine so not sure what’s causing the problem…