uhhhh, make that "EJB 3.0 dependency injection annotations only works in EJB objects -- not generic POJOs" oh well, I have to take it all back... no, seriously, I got that wrong, but it's still cool. Some automation is better than none and, last time I checked, SpringFramework (et. al.) plays nicely with the A/S and servlet containers.
What is the difference between adding a @Entity on a class and adding an xml declaration for this class in some Spring file?