The 2nd object never loads. Here is the code as it is now: <mx:RemoteObject id="salesRepDelegate" result="event.call.resultHandler( event.result )" fault="mx.core.Application.alert( event.fault.faultstring )" named="salesRepDelegate" showBusyCursor="true" concurrency="multiple" type="stateless-class"> </mx:RemoteObject> <mx:RemoteObject id="expeditedDelegate" result="event.call.resultHandler( event.result )" fault="mx.core.Application.alert( event.fault.faultstring )" named="expeditedDelegate" showBusyCursor="true" concurrency="multiple" type="stateless-class"> </mx:RemoteObject>
With the above code salesRepDelegate will load but if I reverse the order, then only expeditedDelegate will load. Rich On Wed, 16 Feb 2005 13:16:01 -0000, Steven Webster <[EMAIL PROTECTED]> wrote: > > > Is there a problem with having 2 remote object tags ? In my > > testing, only the 1st remote object is getting loaded. Any ideas ? > > You can declare as many as you like, with different ids. > > What is your source ? How does the error manifest itself (at > compile time, run-time, what is the error message you get, etc) > > Steven > > > Yahoo! Groups Links > > > > >
