Over the last five years, a lot has been written about J2EE best practices. There now are probably 10 or more books, along with dozens of articles that provide insight into how J2EE applications should be written. In fact, there are so many resources, often with contradictory recommendations, navigating the maze has become an obstacle to adopting J2EE itself. To provide some simple guidance for developers entering this J2EE Jumble, this article sets out to compile the following "top 10"(actualy 12) list of what are the most important best practices for J2EE.