Semantics aside, I think what was being suggested is not so much abandonment of JEE (irrespective of what the article said), but utilizing "lighter" app servers that support only a subset of the JEE spec, such as Tomcat, over the likes of JBoss. Valid point, IMO.
Alexey ________________________________ From: Augusto Sellhorn <[email protected]> To: The Java Posse <[email protected]> Sent: Wed, January 19, 2011 2:03:26 PM Subject: [The Java Posse] Re: Integration Watch: Java EE: The dead man walking On Jan 19, 12:29 pm, Blanford <[email protected]> wrote: > I have heard this from many well known environments. > I personally have never worked in an environment where a JEE solution > was necessary. Perhaps this is the problem, it doesn't seem that you're that familiar with what JEE is and what it aims to solve. As has been pointed out, some of the technologies you mentioned are part of the JEE spec; http://www.oracle.com/technetwork/java/javaee/tech/index.html Just look at the list, note that it even includes an API for REST services. So again, saying using a JEE servlet container (tomcat, jetty, etc) doesn't mean JEE is dead. I think your rant is really against EJBs, but maybe you want to be a bit more specific. I will say one thing, I've seen the opposite of what you mentioned happen, people hosting applications on tomcat with a servlet front end when the app would have been better served with EJBs at its core instead. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
