I think Rod Johnson might have a vested interest in saying such a thing. Personally, I see nothing wrong with using/investigating EJB3/3.1. It's majorly improved over the 2.x stuff.
I believe the real issue is: by default most people have gone to Spring and think DI is the bee's knees. It's not that EJB3 is bad or unusable or doesn't have the right features -- it's that most people have moved to Spring and aren't interested. I haven't had to use Spring and therefore I have no investment of time and effort in learning it. If I were starting on a project requiring stuff like that, I'm just as likely to look at EJB3 as Spring. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
