This is really not convenient in cases where remote objects come from different dev teams or third party librairies. I would expect BlaseDS to discover at runtime its remoting configuration.
So I wrote a simple BlaseDS service that discover any "META-INF/remoting-confg.xml" file in the classpath and register any declared remote object with the remoting service. I basically created a new Flex service that inherits from 'flex.messaging.services.AbstractBootstrapService'.
The simplified procedure is :
- look up remoting service from broker.
- list any existing 'META-INF/remoting-config.xml' file.
- parse config files and create destinations (using 'flex.messaging.services.Service.createDestination(String)').
- register created destination with flex remoting service (using 'flex.messaging.services.Service.addDestination(String)').
You can download implementation.