Hi Mike & Merrick !!! I am planning a certification for EJB's. Since EJB 3.0 is also launched i now have an option of getting certified in EJB3.0 but the question is "How many organisations actually are using EJB3.0 "?
Would it not make more sense to get certified in a technology which is rampantly used across organisations?With EJB3.0 certification i can boast about being master of a technology which no one is using !!!
On the other hand , if i get certified in EJB 3.0 i will be certified in a niche technology which very few people even know about !!!
I agree with Anthony that many companies are currently using EJB 2.x. So lot of work will be done in 2.x. If companies plan to migrate to EJB 3.0 developers will have to have 2.x knowledge to migrate. So learning 2.x will not be a waste of time.
In fact, most existing systems will likely never be migrated until such a time as the application servers they run on go out of support (if then) and no replacement can be found that can run them.
JEE5 will slowly start to become used over the next year or so for new projects, first mainly in small companies and experimental groups (which are usually made up of senior people, not groups you can get hired into in most companies) and later (maybe late 2007, early 2008) larger companies may start creating projects making use of JEE5 for distribution in life environments. These too will be prestigious projects mainly (or exclusively) made up of more senior employees and maybe some outside consultants.
New hirees with large companies I think will not make largescale use of JEE5 until mid-late 2008 at the soonest.
Just to disagree slightly, but not entirely with some of the points made by others in this thread....
I do think that most larger companies have a longer up-take time with new technologies. It's a matter of inertia and of not wanting to use something that's untested in the marketplace. I think we will see, in the coming months, smaller firms moving to adopt EJB 3.0 as there are increasing numbers of appservers that support the technologies, with the larger firms following suit next year - after all, Sun's been trying to get out a new version of the language every 18-24 months, and by 2008, Java EE 6 will probably be at least in Beta.
That said, I think the firms that will be sticking with EJB 2.x for the moment are ones with an installed base of code using that technology - companies that are just now starting to adopt EJBs might very likely begin with the easier paradigm of EJB 3.0 since it's not a shift in how they do business.
I could be wrong, but that's just my $0.02.
Theodore Jonathan Casser
SCJP/SCSNI/SCBCD/SCWCD/SCDJWS/SCMAD/SCEA/MCTS/MCPD... and so many more letters than you can shake a stick at!
Just wanted to mention a couple of things: first is that the EJB 3.0 spec still includes all of the material in the EJB 2.1 and earlier specifications. The only deprecated (not removed) portion is CMP 1.1 entity beans. If you want to pursue certification, you need to know EJB 2.1 plus the new and changed material introduced in EJB 3.0.
Second, there will be several commercial EJB 3.0 products on the market before the end of the year. As customers move to these new versions, the opportunity exists to start incorporating EJB 3.0 features into legacy applications. It's important to remember that most existing customers will approach this in a careful, incremental fashion. Adopt the new simple style of session bean, for example, but leave CMP in place. So I expect there will be long transition period for existing customers that are still actively developing their applications. It will start this year and continue on for many to come.
Hopefully new application development will focus on EJB 3.0 from the beginning.
The project that I am currently working on is using EJB 2.0 to the maximum extent possible, we have about 120 entity beans. This project is about 2 years old now, our customer found it very difficult to port the application in various platforms, though we have the application running now in Weblogic, JBoss and Websphere, it took them a lot of money to do the porting. It is because of this they decided to remove EJB's from the application and move to Hibernate which does not depend any application server. With EJB3 now is it possible to have the application "App Server Independant" atleast from the Entity Beans point of view.
Well, we still have to support J2SE 1.3 in our client libraries because some of our largest customer refuse to upgrade to even 1.4... Of course with 1.5 on the market (and in use on many of our internal applications) and 1.6 on the horizon (which I likely will advise we not use because of the inevitable compatibillity problems with a plethora of 3rd party implementations that will soon flood the market, plus the idiocy of all the crap Sun's putting into it) that's seriously old.
Given that (and previous experience working in large companies), I seriously doubt whether most financials will move to JEE5 before at least JEE6 and maybe JEE7 are available (if then).
there will always be exceptions. I worked for a multi billion Euro bank in 2001 who at the time were still running NT 3.5 on many systems because they didn't trust the stabillity and security of NT 4 (and many other systems were using OS/2 3.0). They were using Java 1.1.6 for most Java development. Web applications were limited to the first Servlet and JSP versions publicly released back in 1998/99. From what I see now (they're now a customer) they've moved on to Windows 2000 for their client platform, J2EE 1.2 or 1.3, and J2SE 1.3.