Though the remoting support in Spring BlazeDS Integration removes the need to define individual remoting destinations in the BlazeDS remoting-config.xml, it currently still requires a minimal setup for the BlazeDS RemotingService. The minimal setup for remoting-config.xml is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<service id="remoting-service"
    class="flex.messaging.services.RemotingService">

    <adapters>
        <adapter-definition id="java-object" class="flex.messaging.services.remoting.adapters.JavaAdapter" default="true"/>
    </adapters>

    <default-channels>
        <channel ref="my-amf"/>
    </default-channels>
    
</service>    	
    	

The requirement to have this minimal remoting-config.xml will be removed in a future milestone release of Spring BlazeDS Integration.

If you have an existing remoting-config.xml for a legacy BlazeDS application, the FlexRemotingServiceExporter will be able to work transparently with it, allowing you to gradually migrate to all Spring-managed remoting destinations.