5 years is eternity in this world. It was called J2EE back then. Look at Java EE 6 and make up your mind. Some did : http://blogs.sun.com/stories/entry/mollom Like anything else, don't expect it to be the solution to every problem you face. -Alexis
On 19 janv. 2011, at 18:29, Blanford wrote: > > Just because the podcast is old does not mean its content is not > relevant. > Actually I think JEE is less relevant today than when the podcast was > recorded. > > Next, how about in industry? > > Amazon engineers I know say that their infrastructure is hosted on an > in house branch of Tomcat (Catalina servlet container needed > adjustment for their environment). > I have heard this from many well known environments. > I personally have never worked in an environment where a JEE solution > was necessary. > > Most of the time when you hear people claim they need JEE, they > usually are not aware that all of the features are available much > cheaper and with lower maintenance. > > From what I gather JEE has been ignored by most of the large web > businesses in favor of Java SE, LAMP, Rails etc. > Read this article on Netflix, I am not as familiar with their > environment but from what I gather Java SE has been good enough for > most of what they do if not all. > http://blogs.computerworlduk.com/open-enterprise/2010/12/netflix-opens-up-about-open-source/index.htm > > -- > 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.
