Jeff, thanks for the reply. Couple of questions:
1) I tried stepping into the remote object call but I can't figure out the source path for the following which is where the first step takes me mx.rpc::AbstractService/http://www.adobe.com/2006/actionscript/flash/proxy::callProperty 2) If my error is happening as the message gets created is that not AMF serialization rather than de-serialization? Do I have that the wrong way up? I don't see why a set method would be called when serializing, but I can understand if it were deserializing. Either way this is an interesting new line of investigation, I'll check all my setters. Simon --- In [email protected], "Jeff Vroom" <[EMAIL PROTECTED]> wrote: > > I've seen this before when an error occurs in a "set" method being > invoked during AMF deserialization. In FB, you should be able to stop > in those methods and/or add your own trace statements to find the > problem. This all happens before the FDS code is executed which is why > TraceTarget is showing anything. > > > > Jeff > > > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of simonjpalmer > Sent: Monday, December 10, 2007 11:53 PM > To: [email protected] > Subject: [flexcoders] RemoteObject silently throwing #1009 null object > error > > > > Hi, > > FB2 + FDS. > > I have a RemoteObject silently throwing the following error when I > call a remote method: > > TypeError: Error #1009: Cannot access a property or method of a null > object reference. > > Does anyone know of a way I can track down what exactly is causing the > error to be thrown? I have been using TraceTarget in my app to try > and see what is going on but no message ever gets created (I guess > this error is thrown while the message is being created). Ideally I > want to be able to step through the framework code in the debugger so > I can examine my value object graph at the point the error gets thrown. > > It is clearly data related because some objects succeed via the same > method and others do not. There is nothing obvious in my data or code > that would cause a null to occur and I have spent days looking for > possible culprits and found and fixed quite a few with no effect. > > What I really need is to be able to see what the framework is > objecting to. > > Anyone else come across this? Anyone have any suggestions? > > tia > Simon >
