"The Big Picture" provides quite a bit of information in addition to JSPs and servlets explanation. In addition to explanations of EJBs, EJB and Web containers, services like connection pooling and security, Web services, and the benefits of J2EE, we discuss when J2EE might or might not be a good choice, as well as things to consider when creating the architecture.
The chapter titled "Does a Cup of J2EE in the Morning Always Smell Like Victory" addresses application characteristics that would indicate usage of J2EE. http://www.bigpicture-books.com/bigpicturetoc.pdf Lots of applications might or might not be good choices; there are considerations in addition to the application itself, such as the skillset of the development team.
Any reasons for not providing code samples? :roll:
Primary target audience doesn't need no steenkin' code examples. There are a few but just to see the general outline of how the code works. We wanted to make sure this book was not intimidating, and that it was clearly a Different Kind of Technical Book.