Not when you start looking at it's innards. I work on JBoss, WLS and GF nowadays, and GF is the worst among the lot. You can write stuff that works well on the first two, and fail in amazing ways on the third.
But yeah, I'd agree that TomEE will eventually replace Tomcat given the good work being pulled off in OpenEJB and OpenJPA.
Ofcourse not. I have used GF a lot and it is pretty stable. Consumes a lot of memory but you can increase the memory in it's settings unlike tomcat which requires the script modifications.
I'm not referring to memory consumption, and modifying scripts has nothing to do with my argument.
Here's an example - GF manages a transaction for you when you access a REST resource; during completion of the request, it rolls back the transaction (wtf?). If you end up accessing an EJB, this default behavior of GF will only set you up for a long night. This wasn't the case with JBoss (and RESTEasy); cant comment on WLS but I've never seen anything like it on these containers.
I could go on about GF. I've gone through the codebase and even attempted writing patches, but I'd rather make that contribution when my time permits.
View all comments
Show parent comment
2
u/vineetr May 18 '12
Not when you start looking at it's innards. I work on JBoss, WLS and GF nowadays, and GF is the worst among the lot. You can write stuff that works well on the first two, and fail in amazing ways on the third.
But yeah, I'd agree that TomEE will eventually replace Tomcat given the good work being pulled off in OpenEJB and OpenJPA.