Originally posted by Nicholas Cheung: [QB]I would like to know how in depth the book did cover J2EE, mainly Servlets, JSP, EJB, stuffs? or even Web Services, Security, Transactions? or even it includes advanced topics? QB]
I'm going to assume this is re "J2EE: The Big Picture," though I didn't see a big intro to that effect from a sheriff person. So, I'll just go for it!
J2EE: The Big Picture covers all those topics: servlets, ejbs, jsps, web services, security, transactions. We cover insight into how it works and why it exists,though, rather than the detailed code. This is for people who don't want to and don't need to understand the code.
Originally posted by Pradeep Bhat: Should I say that the book is for architects, who are new to J2EE? :roll:
Sure. One of my coauthors, Mark Cade, is an architect/big Java guy in general in Sun PS. There's a chapter about architectural considerations, qualities of service, and we had architect reviewers who said it would be a good refresher/intro book for a non J2EE architect.
Originally posted by Nicholas Cheung: Thus, this is a high level introductory book?
If this is the case, what is the target readers? Top management, or junior people with less J2EE experiences?
In addition, are there any advanced topics?
Hi, yep, it's a high level introductory book. It should serve for anyone from an "HTML programmer" who doesn't know what a container is, on up to a plain Java programmer who wants a quick easy read on what EJBs and JSPs are before diving into somethign like Head First EJBs or the spec or C) other.
Target readers do also include top management.
The book has a lot of advanced topics, just not an intensely techy take on them. I show the code for very simple session and entity beans, but just to show examples of the home interface, etc. There are a couple architecture chapters raising different opinions about the technologies, and higher level considerations than how to write code. There's stuff on JAXP, Web services, transactions, security, UML and patterns, etc. But all just, you know, the big picture. Nothing that will make anyone's head hurt, but enough to both understand, and make insightful comments in, meetings.