Hey Paul,
but I'm afraid that's not how Cairngorm deals with remoteobjects, the remoteobject is only configured for a specific server endpoint/source/destination, the method is defined in your business delegate.
So in a Caingorm situation you don't need to define the method in your MXML, nor in your SpringAS config.
If you insist on configuring a remoteobject directly with a method, I suspect you need to add it to its operations collection.
Something like:
Code:
<object id="loginService" class="mx.rpc.remoting.mxml.RemoteObject">
<property name="destination" value="zend" />
<property name="source" value="LoginService" />
<property name="showBusyCursor" value="true" />
<property name="operations">
<value>
<array>
<value><object class="mx.rpc.remoting.Operation"/>...further config comes here</value>
<array>
</value>
</property>
</object>
This is not really a SpringAS issue however, just a matter of figuring out how the RemoteObject works internally.
Right now I'm afraid I don't have time to look into this, so for now you're on your own 
Maybe someone else on the forum here can offer some insight?
cheers,
Roland