Announcement Announcement Module
No announcement yet.
Advantages of RemotingExporter over SpringFactory? Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Advantages of RemotingExporter over SpringFactory?

    We are using Spring-Flex integration (yet the outdated M1) and use a modified (for DataServices) version of the RemotingExporter classes to reveal the beans to the Flex application. But I just recently discovered a major disadvantage. When defining the destination only inside the applicationContext there is no chance of porting the Flex application to AIR and implement offline functionality for the DataServices, because the service config could not be retrieved from the server (the user is offline) so no destinations can be reached.

    Because I don't want 2 different service configs at 2 different places I implemented the good old SpringFactory (just for the lookup stuff) from Jeff Vroom, and it seems to work well with the rest of the Spring-Flex integration. I just wanted to know what are the differences between these to exporting methods and which one is better?
    Last edited by Peacemaker2000; Apr 30th, 2009, 08:29 AM.