Listen the facts: "EJB 3.0 Early Draft Review Released" " With this draft out, I don't see anyone doing any new EJB development. Why would I start any development with EJB 2.0 now when Servlet/RPC/Hibernate solution seems to be much closer and easier to port to EJB 3.0 then 2.0 -> 3.0? And if I develop a solution sans EJB, will I really have incentive to port it? Anyone else doing it, but Sun itself, I'd call this spreading FUD. (otoh, some would say that it's not possible to spread more FUD about EJBs, as it's already so covered in it, no one would ever notice )" etc,etc... http://www.theserverside.com/news/thread.tss?thread_id=27005
Sorry, but I disagree and I thik a lot of other people would too. I've been at JavaOne all week and I don't hear of anyone abandoning EJB. In fact, I talked to someone who went to a session by Gavin King (who is on the spec team for EJB 3.0) who is really high on EJB 3.0 - and he is the Hibernate king (sorry, bad pun).
In fact, I'm encouraged by what I hear - I went to Linda DeMichiel's session on Tuesday and what they are doing is great, albeit it should have been this way in the first place. The DTO anti-pattern is going away and the simplification is wonderful - no more messy, needless implementations of interfaces except in specific cases.
We are going to do a rewrite in the next year and we'll certainly keep an eye on the 3.0 deployment.
I had a chance to meet Kathy Sierra and Bert Bert Bates at the author table and in talking to Bert briefly about the HFEJB book, I told him the book will probably be cut half, but we both speculate 3.0 won't be available for implementation probably until mid to late next year some time - I see no need to abandon EJB devlopment until then.
But you basicly agree with me... "it should have been this way in the first place..." So why invest so much effort in the old-present way? "no more messy, needless implementations of interfaces except in specific cases.." so..I think the natural conclusion to this is my post...isn't it? Regards Igor
My point is that EJB 2.X is still around and will be for some time, plus the new spec will be backward compatible, so EJB 2.X implementations are going to be around for sometime.
Just because 3.0 is coming doesn't mean that everyone is going to spend oodles of cash rewriting EJB 2.X - there's still a mountain of COBOL code out there still running - just because Java came along didn't mean a rewrite of COBOL code.
Same thing here. So basically, no, I don't agree with you.
(Having also been at JavaOne this week), the new EJB is going to be great... but I'd bet it will be a couple of years before many people are using it in production. So I guess if you can wait for a couple of years, go ahead and wait. Technology moves ahead, and it won't hurt to learn something even if you "only" use it for 2 years.
Spot false dilemmas now, ask me how!
(If you're not on the edge, you're taking up too much room.)
OK guys, I'm closing this thread as this topic has already been beaten to death. Please check out the following discussion Advice to those planning to take the SCBCD and please think a little about it before bragging non-sense. The EJB 3.0 egg has just been fertilized and it is gonna take time until it matures and becomes a full-blown entity (no pun intended)... Let it grow in peace and focus on what we have now...