Link Details

>The worst thing is that the principle that at least JBoss follows is the “principle of most surprise”. Things just don’t work the way one expects them to.

Maybe those things don't work the way -you- expect them? To me they actually do work they way I expect them to be. Sure, occasionally things don't work, but that's true for Spring too. On the whole I would say the amount of quirks in both these great platforms is fairly equal.

Of course, there are also things that are plain bugs. JBoss Hibernate for instance has quite a lot of them really, but let's not forget that Spring applications depend just as much on Hibernate as most Java EE applications do.

I have to agree with Henk -

">The worst thing is that the principle that at least JBoss follows is the “principle of most surprise”. Things just don’t work the way one expects them to.

Maybe those things don't work the way -you- expect them? To me they actually do work they way I expect them to be. Sure, occasionally things don't work, but that's true for Spring too. On the whole I would say the amount of quirks in both these great platforms is fairly equal.

Of course, there are also things that are plain bugs. JBoss Hibernate for instance has quite a lot of them really, but let's not forget that Spring applications depend just as much on Hibernate as most Java EE applications do."

Also, be aware this article was written about Java EE 5 - which is over 4 years ago, since it was released on May 16, 2006. This article is not written about current state technology.

PS. When I said I agreed with Henk, this was not meant to be a slight on you. The state of documentation (or lack thereof) is the biggest failing of Java EE, and leads to tons of confusion with "how am I supposed to do this?" or "this is too hard!"

It's not your fault, it's our fault. I will always push for more centralized, portable EE documentation.