EJB outdated?

[vinoth ar]

hi friends,
I heard that the EJB is an outdated technology. I planning to set my carrier In Bussiness Component Developer. Advice me.
thanks

[Freddy Wong]

That depends on how you define outdated. EJB 1.x and EJB 2.x are, but EJB 3x. isn't. And no Spring versus EJB flame war, please

[Reza Rahman]

LOL - amen for the desire to steer clear of flame wars :-)

I would ask the folks that you are talking to why they believe EJB is outdated. In essense, EJB provides a number of services geared towards Java server-side business component development - transactions, persistence, dependency injection, component registry, lookup, remoting, web services, interceptors, scheduling, security, messaging, etc. I think those are mainstays of any middleware technology, not just EJB, Spring or .NET. Additionally, EJB 3 provides these services with minimal configuration on your part and via 100% annotations (or XML or a mix of both, if you prefer).

Hope this helps,
Reza

[Jack Dwaltz]

vinoth ar wrote:hi friends,
I heard that the EJB is an outdated technology

The answer is not.
But it depends on what you are going to work on/with.
For sure in many cases other approaches could be more to the point.
There are tons of frameworks in the Java world and plenty of solutions based on different languages, like dynamic languages (Ruby/Python/Perl), or C# or the dear ol C/C++.

The point is that EJB is a simple tecnology to work with in the 3rd version, so if you know Java, it should not take to much time to you to learn a bit on how it works. And later you will have an extra tool in your pocket.

If you want to work with componenets you might consider to study OSGI as well. (I don't think there is need to name SOA as I guess you hear already to much about it).