Flex Remoting and WebORB Mysterious Error Messages
- July 1st, 2009
- Write comment
If you work with Flex remoting and WebORB, you are probably familiar with the following errors:
- NetConnection.Call.Failed: HTTP: Status 500
- Channel Disconnected
You may have tried directing your browser to weborb.php only to get this message: “WebORB v3.5.0 Fatal error: Call to a member function getServiceURI()”
The getServiceURI message is actually a red herring error message. This simply occurs because weborb.php is expecting the raw headers to contain Flash remoting AMF message data. Your browser is just making a normal HTTP GET and doesn’t know anything about AMF. So weborb.php winds up with a null object on which it tries to call getServiceURI(). I wouldn’t be surprised to see a future release of WebORB that catches this error, even though it isn’t the purpose of this particular file to run inside a browser.