First, look at your organization. Depending on the experience and capacity to learn new things, Spring XML abstracts logic and functionality by removing the visual dependency chain from your Java files. If your development team is not accustomed to this type of development model, it can be a steep learning curve. Don't underestimate this point. I made this mistake with a group of very sharp developers and was surprised by the amount of overhead it added to the team.
I have found that using Spring Annotations, or any Java Annotations for that matter, offered significant development overhead reductions. This was due to the direct visual link they provided and seamless integration with your favorite IDEs. Having the ability to use current day-to-day tools in your development cycle like drilling down into source code, setting debugging break points, Javadoc tool-tips, etc, is not something to take for granted.
Now I know you can get a Spring Tool set for Eclipse, not sure of the others, but you are again adding a another layer of learning on your team.