I would guess the best thing to do when you see that error is to verify that your Flex and Java back end can communicate. I would do this by setting up a really simple bean in your beans descriptor file, for example something that just echos a string back to flex. For that to work, as you pointed out you will need to add a services argument to the mxmlc call, something of the form below should do the trick!
-services “[local path to your java project]/WEB-INF/flex/services-config.xml”

once you are confident that the connection to the simple bean is working, then move to setting up the required connections for your application.

Hope this helps!!

Sam

I found this post very interesting, as I’m moving a Flex app to Remoting + Spring. While testing a bean of my own, I keep getting the error “[MessagingError message='Destination 'SomeBean' either does not exist or the destination has no channels defined (and the application does not define any default channels.)']“. The bean I’m invoking is not directly on the deployed WAR, but in the containing EAR instead, and deployed by Spring on its start.

Second issue (derived): I read that MXML files using BlazeDS should be compiled using the -services argument, pointing to the services-config.xml file on the server. Is this right?

Thanks and great work!

The page you are requesting cannot be served due to the Multipurpose Internet Mail Extensions (MIME) map policy that is configured on the Web server. The page you requested has a file name extension that is not recognised, and is therefore not allowed.