Samanthi perera wrote:anyway can you tell me what are the API use in J2SE and J2EE ?
Pat Farrell wrote:I believe that the whole old-style J2EE design has fallen out of favor. It was never needed, and its not clear that it made things better.
Ulf Dittmer wrote:Let's be precise: Old-style EJB (2.x) have fallen out of favor, and it's not clear that new-style EJBs (3.x) add much that can't be had by other means (like using JPA directly, without needing an actual EJB container).
Ulf Dittmer wrote: But JEE also defines lots of other APIs -like JavaMail, JMS, Servlets etc.- and those are still very much en vogue.
John Todd wrote:EJB isn't bad idea. If you say EJBs are complex, well that is mainly because it is trying to solve complex problems. I agree that EJB 2.x are really pain in the *** to develop with but this isn't the situation with EJB 3. I don't know what is the current state of EJB (is it used these days?) but to me, EJBs are noble creatures.
Pat Farrell wrote:
I do not know anything about EJB3 or any possible later versions. I was *so* traumatized by trying to use EJB six or more years ago that I still have nightmares.
Samanthi perera wrote:
can we do any EJB 3.0 application using Spring ?
Pat Farrell wrote:I may not be "typical" but every professional Java application that I've written in the past decade has used servlets, and used them heavily. So for me, having them outside the standard JDK seems silly.