I like the idea of loading in config properties from an XML file, but I am still looking for a while to externalize the server information without requiring any changes to config files.  That is, I am trying to keep it such that clients, etc. can just drop in the WAR file and go.I found this snippet...

OK - to summarize:1) you must have a service-config.xml in the WEB-INF/flex directory2) you can create your channel set and channels on the client in mxml and actionscript and not compile against the server's service-config.xml3) they need to line up correctlyThis is all cool and I found sample code...

Thanks for the help!  Are you saying that the service-config.xml file in the WEB-INF/flex directory was only ever for the client to compile with?  How does the server "know" what channels to "listen" on?Perhaps I am missing something important here about how all this works.  I thought that AMF binar...

Newbie here trying to get my first Flex/BlazeDS app up and running.   I'm using the Spring-Flex integration and believe I have properly configured my servet and remoting destinations.  My only remaining questions relate to how to configure the channels.The use of the Spring/BlazeDS integration means...

Thanks a lot Rohit -- that is a huge help.

I've seem to have read the Spring/Blaze integration document about 10 times, but I can't figure out where to put all of my <flex:remoting-destination ref="yaddayaddaService" /> tags.  I don't want to use annotation to define these remoting destinations.Should it go into the Spring configuration file...