> Do I still need to worry about the services-config.xml and > remote-config.xml files? If not, how do the destinations and their > properties (i.e. the source property that specifies which Java service > gets called) get set up? The various *-config.xml file in the WEB-INF directory are used by the server to determine how to map an incoming request to a piece of server side code. Your remote object calls will specify one of the destinations listed in the config file (remoting-config.xml, perhaps, I don't have an FDS install to hand at the moment I'm afraid), when Flex sends the request this is sent along with it, at the server the' gateway', which is a servlet the url of which you specify as the remote object 'endpoint'', receives the call and uses the information in the config files to figure out which method to call on which object - remoting-config.xml essentially just maps the 'destination' name that flex sends to a class on the server.
So, as a Flex developer you just have to make sure the server is running and that the any java class or jar files can be found by the server, and that you know the correct destination names to use in your RemoteObjects. What can cause confusion is that if in Flex Builder you specify a data services server when create the project then Flex Builder uses the config information on the server to automatically set endpoints on remote objects (IIRC you can specify a server-config file to mxmlc to achieve the same thing). This creates a dependency on the server against which you are building 'against' in flex builder, so when you come to deploy in another environment you find you're stuck as endpoint information has been baked into your swf by Flex Builder. You then have to go into your Flex code and add all the endpoints you thought you'd got away without having to worry about : \ Stephen.
