From my interactions with the community and from discussions with Adobe's developers about feedback from their community, our feel is that the current approach (i.e., the SpringFactory dependency lookup approach) is not as simple as it should be and is at odds with the programming model to which a Spring developer (i.e., someone who uses Spring but is completely new to BlazeDS and Flex) is accustomed.
But with that said, the larger point is definitely that the foundation in place with M1 opens up the door for many more integration opportunities and makes them simpler to implement. Spring Security integration is the top priority for M2. I think I am familiar with your posts on the matter, but could you re-post the links here for the benefit of the rest of the community?
Are there particular pain points you have encountered with handling exceptions in conjunction with remoting?
Thanks for the feedback.
Staff Engineer, Web Products Team