example-of

The idea of lots of examples and some solved problems is an excellent way of learning anything. However, to really teach well a book should have a strong logical underpinning and lots of solved problems to initiate a very gradual and fundamental understanding of the subject. I did not think that this book took that extra step. Consequently, I would recommend it as one of the books you buy to learn Java, but do not rely on it for your full Java education.

I took a programming class in the late 1970s, but never programmed anything outside the classroom. In '97, after being system administrator for 7 years, my employer asked me to take over the administration of our web site. So I picked up 4 different books on JAVA. After reading through 3 of the books, I felt either they were too advanced for my grasp or weren't well written. JAVA By Example took me through the basics in a very short time. After reading this book, I later went through the other 3 books a second time and determined that they were poorly written. Great Job, Clayton Walnum.

Java was (believe it or not) the FIRST programming language that I attempted to learn. After buying several books that basically relied on the reader having a C/C++ background, I found this book. The absolute best thing about this book is that after each progamming example, a line-by-line explanation of how the program works is given. This to me was the core reason I learned Java. I have found no other book that takes the beginner step-by-step in this same manner. Once you finish this book you will easily move on to more complex Java topics because you will have gained a thorough understanding of the language.

I can save you money on the purchase of this book. If you can answer "yes" to the questions below, there is no need to buy this book:

* Do you know what JSP and servlets are?
* Do you know how to separate presentation and business logic with JavaBeans and custom tags?
* Are you familiar with MVC?

If so, no need for the book. I was expecting much more. It's less best practice, and more typical web app development. What disappointed me further was various comments in the text that displayed poor practices in areas outside of JSP web development, e.g. "the first step in developing a jsp web application is designing the user interface."

My one-star rating can be summarized as follows:

* Poor typesetting and book formatting: -1
* Very few "best practices" -2
* Below average writing, low content-to-price tag ratio -1

This book will probably be most useful to someone who knows JSPs and servlets and has worked with them, and is looking for better or alternative ways of writing JSP applications.

The first two chapters provide a review of JSPs and an overview of web deployment. They include a nice JSP/MySQL example, with
instructions indicating how to build the MySQL database and incorporate into the JSP example using JDBC.

Chapters 3 and 4 include discussions and examples of how to use JavaBeans and custom tags. The JavaBean example shows how to handle the display of a large amount of data retrieved from a database.

The use of J2EE patterns is discussed in the next several chapters, as befitting a book with "best practices" in its title. The four patterns covered are the Decorating Filter, Front Controller, View Helper, and Dispatcher View.

The remainder of the book covers some topics that are not directly connected to JSPs, but may be useful in a wide range of software applications. These include regression testing, and the use of JUnit and JMeter; deployment, and Ant and CVS, as well as precompiling JSP pages; and application frameworks, including an example.

In short, the book includes a collection of topics not often found in a JSP book.

I noticed some minor quibbles, such as use of single-character variables and older break tags (rather than
),
but generally speaking I find the book to be quite informative and practical, especially in the discussions and use of open source software such as MySQL, JUnit, JMeter, and Ant, with JSPs.

This book draws a clear picture on JSP web application development. If you are a JSP beginner, this book is a must read. It teaches you the right way to do things from the beginning.

I really enjoyed its step by step approach that leads to the framework based application development, makes a lot of sense to me.

First off, the first half of this book talks about working with ADO in VB6, scared me at first but the second half talks about ADO for VB .NET. So, right off the bat 1/2 of this book is most likely useless to you depending on what you use or want. Goes into great detail about gotcha's, speed, interesting methods like using stored procedures and how the dataset is handled and what to watch out for. My problems, he does not mention how to bind a control through code. For example, have a form that has a grid/listbox and when the user clicks on an element have it display more detailed info about that record in labels & textboxes which are bound to the record... won't find it here and that's like basic 101 stuff. Maybe you want a parent child record, with the parent in text boxes and labels, and the child to be a grid (sort of like the tutorial but a little more advanced since it too does not show textboxes/labels). No help here. Also, all his examples appear to be just single-form based. I wanted to know more about how to program connecting to a database across multiple forms. Why, I even wanted to create a single connection object and use it across multiple forms... or have a database application on multiple forms... another basic database example. No help found in the book, after 18 hours I finally crawled my way and found how to do it myself and how darn simple! But, if you don't know where to begin (this book was no help) it's difficult and tedious. Now that I know I'm kicking myself.

In the end this book fulfilled me half way. I wanted to know how to program an application across multiple forms that connect to a database, how best to use the same connection object across those forms, and how to bind textboxes/labels through code and how to update, delete, and insert records that way. This book has left me in near utter darkness on how to do that. I wanted to know about parent/child relations and this book had very little to offer as far as I'm concerned in respect to examples (there's one). However I have a complete understanding of how to connect to a datasource, access columns, set up parameters, access stored procedures, and some knowledge of parent/child relations, some gotcha's of using the fill method, how to set filters, and sorts on the returned recordsets, and a good understanding of updating/deleting/inserting and how to intervene with those operations... also foreign constraints so that's why I give it an average rating.

The first half of the book is old technology (VB6), I was nervous when I ripped it open and began reading the first couple chapters... then I saw the second half is about ADO .NET or database programming for VB .NET (phew!). So, depending on what you're using 1/2 of the book will be useless for you. I happen to be going from VB6 to VB .NET. He explains through great detail and with surgical precision what things are, how to connect to stored procedures, all sorts but it's all based on datasets. For example, like most people my program has multiple forms. This book was useless on helping me re-use a connection. I began programming each form needing to open a connection when necessary each and every time. I figured out myself (after about 18 hours) how to use a connection from another form and had to scoff at how easy... but it's one of those things that takes forever until you get it. Another is binding controls in VB .NET. If in code I create the connections and dataset and I want a textbox to display the customer name, you won't find the answer in this book and I think that's basic stuff. The thought of having an example where you select a customer from a grid and display the info of that customer on labels or textboxes bound to the record is no where to be found in this book. I'd like to know how to update/delete them as well from those textboxes but as said previously the only control used in the entire VB .NET section is a datagrid, you'll know more about datagrids than you'll know what to do with and I think he should've branched it a little to other controls. Now, I'm searching on my own again on how to bind a dataset to a textbox.

Like all of Bill's work, this book kicks butt. If you do anything more than lightweigth ADO.NET programming, make sure you add this to your library

Being a beginner with ASP I bought this book as a tutorial to learn ASP. I have access to ASP professional Developers so I was able to ask a lot of questions in learning ASP. The code and explainations that are in the book are not clear and are hard to understand. I had to ask many questions. The code seemed to be hard to follow. The Developers that I have access to felt that the Author used too many 'functions' when they were not needed (this made the code hard to follow.) I am going to have to buy another book to learn from. This book may be good for refrence, but not learning from.

Good book, good samples and good programming techniques, The author is very clear and the concept is explained very nicely, he just fails short in the implementation of the component in the ASP pages, he explained very good but the componet was already prepare for that tutorial, I would like the author develop the component throught the tutorial and then implemented, at last that is the way it is!!! , as a web developer I am interested to in the creation of the COM, but I gues that is a diferent subject from the point of view of the author. A very understandable book.

I am very pleased with this purchase. Although I have passed the InterDev exam, I never really understood a lot of it until I read Reselman's book. He really has a knack of explaining complex concepts. The book starts off quite basic, but by the end you have built a quite useful interactive web site. All the source code is on-line and so far it all seems to work fine. At a manageable 575 pages, it only half the size of some of the big ASP tomes, but then it is only about half the price.

The current "WWJD" (What Would Jesus Do") phenomenon is not the Biblical understanding of how we are to determine right and wrong. While this book did not start that pop phenomenon, some may read this mistakenly. What Jesus would do would be different that you or I because He was fully man AND fully God, second Person of the Trinity. He was sinless, and although tempted in every way as we are, He did not sin. His purpose was to fulfill the Law in order to be the spotless sacrificial lamb of God, the atonement and substitute for our sins. He was the omniscient God incarnate, so He knew what was in each heart and what was the perfectly appropriate thing to say and do in each situation in order to accomplish His mission. In that sense, what He would do in a situation as God is a hypothetical we cannot know as finite creatures. What He might have done is a speculation. We are, however, TOLD in Scripture what we are to do, how as Christians we are to act and live.

I'd recommend reading Charles Sheldon's "In His Steps" before reading this. Then you decide who is the better writer and has a real handle on the concept.

This is a great retelling - in a contemporary setting - of "In His Steps." This book helps you see the blessings and the sacrifices involved in truly following Jesus. This book challenges the reader to strive for a better walk with Christ - something all of us should hope for.

I have read this book in different settings a number of times in the past, but I am now going to have our church youth group read through it. I expect it will challenge each of them to not just be a Christian, but to "do" Christianity.

We are called to not just be hearers of the word, but doers. (James 1) This book helps challenge you to be a doer.

This outstanding book is focused on leadership and management for the single most important leadership role, title, or position in life-a parent.

The book is an in-depth exploration of one of my all-time favorite poems that goes by the same title. For readers unfamiliar with Dorothy Law Nolte's 1954 classic poem, it is included in the front of the book along with Nolte's introduction, "The Story of "Children Learn What They Live,"" in which she shares her thought processes and experiences that led to her wonderful creation.

If there were any doubts about the unbelievably powerful influence that parents have on their children, this book will erase any such doubts. I found it a delightful and insightful, easy-to-read book filled with many realistic, common family situations that reflected my own beliefs, experiences, and personal parental goals and expectations. The stories and examples were very effective in helping me to understand and visualize the authors' main points and insights.

The most important theme throughout the book for me was that parents have conscious choices to make when it comes to responding to their children. Often, those choices are between good, helpful, thoughtful, and objective proactive responses, and bad, hurtful, thoughtless, and emotional reactive responses. Children are sponges to their parents' words, emotions, and behaviors.

Just as the old adage says that leaders lead by example, parents parent by example. As a father, reading this book reminded me of the closing to another of my all-time favorite poems, "Little Eyes Upon You:" "You are setting an example/every day in all you do,/For the little boy who's waiting/to grow up to be like you."

This great book should not be read just by parents for raising children, it should be read by everyone for building character and stronger relationships.

As a third grade teacher and an expectant mother, I think this book is a great way to begin a parenting philosophy. I was given the poem this book was based on as an undergrad and always wondered how this could be applied to everyday, real life. The brief essay like chapters neatly spell out how to relate the poem's message to raising and understanding children. I agree with other reviewers that not everything is as black and white as the author might have us think, but this book gives a solid basis to raising children in a very confusing time.
I really liked the way the book was set up - in short easy to read chapters (even my husband didn't mind reading it), and I liked the real life examples that every parent can relate to. While I don't believe this book to be the answer to every parenting problem that might arise, I think it gives both new and seasoned parents a wonderful way to shape thier thinking on how to raise healthy and happy children.

I am a second year college student taking Early childhood Education. We had to do a book report and my mother bought me this book. I began to read it and could not put it down. It touched base on all the information that we are taking in class. Every word is so true. I recommended it to my teachers and classmates. The words touched me in a way that i can not describe. When i have chidlren i am going to re-read this book and take notes down, because i know that it will help my parenting skills in so many ways. Already with my nephews i take the information that was in the book and hold it in the back of my mind when dealing with situations. I apply the knowledge in class, in placement, and with chiildren i love dearly. I believe that children are our future and we must support and fosture their learning in every way possible. Every parent should know about this book adn read it, and really think about what is written in it.I have a copy of the poem hanging on my wall and everyday before i go to class or placement i read it, as i think everyone should. The book was a great insparation that i ill forever keep and turn to.

The book along with the poem is great

Cassie

The late John Howard Yoder was one of the most influential Mennonite theologians of his time. This book argues the case that Jesus believed in a "Christian Pacifism." This is in contrast to the common view of many Protestants in "Christian Realism." In Yoder's view Jesus' opinions are not to be dismissed and downgraded under the general fact of his atonement for the world's sins. Nor are his views to be (tactfully) dismissed as representing a rustic world-view based on personal relationships which does not really grasp the complex world of institutions and power relationships. Jesus cannot simply be dismissed as someone who did not recognize the necessity of power, nor can his view be that of an apocalyptic enthusiast who believed that the world was fated to end. By examining the Gospel of Luke Yoder argues we can see allusions to the Jubilee and its demands for social justice for the poor. Yoder traces a pattern in the bible in which "God will Fight For Us" after the reign of King David, and he points out successful instances of non-violent resistance to the Romans in Jesus' time.

Such are Yoder's views. However sympathetic one may be to pacifism, Yoder's argument is clearly flawed. His work contains two flaws that are common to books of this type. First, his historical knowledge is limited. Second, he fails to fully appreciate opposing passages in the bibles.

Let's look at the historical problems. (1) Much of Yoder's discussion of Jesus is based on the idea that there was a revolutionary Zealot movement contemporary with him. Therefore, Jesus' view of power can be seen as a principled pacifist rejection of their violent tactics. Unfortunately for Yoder's argument it is clear that there was no such movement. One can see this clearly in volume three of John Meier's A Marginal Jew. The "Zealot" in Simon Zealot is an adjective, the faction per se did not arise for another three decades until the Great Jewish rebellion. (2) Yoder has to defend the "Haustafalen" passages where Saint Paul states "Wives, be subject to your husbands...Children, obey your parents, etc..." This passage has historically been viewed as an apology for misogyny and slavery. In defense Yoder argues that these passages were unprecedented in viewing slaves and women as moral agents, and in counselling husbands to love their wives. Yoder is wrong: slaves were commonly viewed as moral agents (i.e. Seneca) and stoics such as the first century Musonious Rufus supported mutual love between spouses.

Now on to the problem of tendentiousness. (1) Yoder's book concentrates on the Gospel of Luke. There is only cursory discussion of why he uses this Gospel, when it is generally believed that Mark is the earliest one. Yoder completely ignores the whole problem of Jesus scholarship, trying to find out what he said as opposed to what the gospel writers composed four to seven decades after his death. (2) Yoder discusses the Jubilee and power. But what about the demons Jesus cast out, or the miracles he performed? What about the statements in which Jesus said the Kingdom of God is now amongst us, and its final triumph within our lifetimes? (3) In the chapter "God will Fight for Us," Yoder argues for a tradition that after King David, God, not men will fight Israel's battles for her. But what about Jehu's coup against Jezebel, or the execution of Athaliah and Haman, or the struggles of the Maccabees? (4) Yoder consistently ignores or downplays the eschatological view of the early church. Consider his long discussion of Romans, chapter 13, which he argues is not a blank cheque for state power. But he ignores Romans 13:11-12: "...for now is our salvatio nearer than we believed. The night is far spent, the day is at hand..." How can one build a politics on the bedrock of people who believed the world was going to end? There may be a good case for pacifism and rejecting power. But Yoder does not provide it and it is not clear that it can be based on the New Testament.

I am borrowing a term from my youth and the Viet Nam conflct when people were labeled Hawks or Doves by their reaction to war.

Yoder makes a case that Jesus was VERY political. He was not uninterested in world events around him. He was involved, but not in the way that much of the religious right is today. More likely, he made the footsteps that Gandhi, Martin Luther King Jr., and Mother Theresa later walked in. This is a book on politics, power, and pacifism. At least that is the way that Yoder sees it.

Many Christians do not agree with Yoder, but he is not easily dismissed. This book is well written and each chapter of this revised edition contains an epilogue that helps to update it with new information since the days of the first edition.

In The Politics of Jesus, John H. Yoder argues that mainline ethicists have falsely assumed that the Jesus in the gospels fails to present us with a normative social ethic. In his careful study of the gospel of Luke and other scriptures; Yoder shows us that Jesus not only showed us a social ethic, but also that Jesus' ethic was accepted as normative by the early church. In this book, Yoder touches on topics such as peace and justice, Government authority, Paul and subordination, as well as Revelation and an Eschatological theology. Yoder convincingly argues that the Power of God is given as gift, through cross and resurrection, and that the 'handles of history' are not controlled in a cause and effect relationship as is often assumed by so-called 'realist' theologies.
Jesus, the slain Lamb, has conquered... him let us follow.
A truly magnificient account of faithful theology.

If you absolutely have no idea what's going on in Crim, or you attend a 3rd tier school, go ahead and get this book. If you want clarity in subjects you've learned (which is the point of this book) or if you're a fan of Glannon, DO NOT BUY THIS BOOK!!

This book is very well organized. It's chapters are categorized with clarity. A law student usually looks at the table of contents and briefly skims the pages to say "ah this book is good." And in this case, yes, it would seem good. Upon closer examination, we realize it isn't.

Let us not forget the sole purpose of this book: To help us UNDERSTAND the material already in our case books, not to regurgitate it. All this book does is repeat in different words what we have read in class, and are struggling to understand. This book does not EXPLAIN the rules it sets forth. If you know books by the brilliant Joseph Glannon from the same Examples & Explanaions series, you know that he'll tell you a rule, explain it with clarity, and give you a real easy made-up hypothetical in which that rule would apply. Not this book, it's explanations of the books are cited to Cases that we READ!! Let's think about this: If we can't understand the case and thus we turn to this book to seek an explanation, how does it help to rearticulate what we don't understand?

Secondly,
Criminal law is difficult because it involves both common law and the model penal code. I don't think these authors know the difference, or don't realize students would get confused if they mixed up terms that would differentiate the two types. For example on pages 255-258, this book attempts to compare common law v. model penal code and their respective levels of culpability. The four specific terms from the MPC are Purpose, Knowledge, Reckless, Negligent. On page 255, they attribute two of these specific words (not inaccurate but confusing) to the common law, yet on page 258 they don't even use the word "knowledge" to describe MPC instead use "purpose" generally and "belief" What's the big idea?!

Last rant: as an example of confusion check out page 265 bottom of the page. "If he attempts to do something that he thinks is a crime but is not, then he is not guilty of attempt. Thus, legal impossibility is not a true defense..." What?! the first sentence would suggest that it IS a defense, but do they try to explain this apparent contradiction? nope.

I plan to return this book to amazon after I finish typing this.

I think that the "Examples and Explanations" series is the best for exam preparation - this particular book relies a lot on the Model Penal Code. Since my CrimLaw professor doesn't really use the MPC, it hasn't been as useful as it could have been - but it's still helpful.

Excellent book. Grade-saving discussion on larceny. Highly recommend this (Crim Law) and the Contracts E&E.

I bought this book because I found the E & E Civil Procedure book extremely helpful. This one was good, but didn't have as many concrete problems as the civ pro book did. Because I needed help drawing out doctrine (my course was policy-heavy), I would have liked more of that. However, the summaries of various issues in Con Law were clear and concise, and it did a nice job of placing various cases within the different strands of the law and explaining what they had accomplished.

Also, the book is organized very differently from how my professor taught it - if you're covering separation of powers as its own unit later in the course, you might have the same problem, because the authors put some separation of powers stuff (but not all) in the section on Justiciability. You just have to kind of skip around it, but the section headings are clear, so it should be easy to recognize when you've fallen into uncovered material.

This book has helped me understand and make sense of [sometimes] the convoluted Constitutional Law cases. Con Law can be quite intimidating for first year students [like many things on campus] and having only the casebook does not help.

The "Examples and Explanations" series helped me gain another perspective on the ideas from the casebook; also, the problems and explanations after and during each chapter actually engage the reader in applying the material into problems, hoping the exam question will be similar (year, right!).

This study aide was extremely helpful for exam review. This book provides the student who has kept up in class with a succinct overview of the topic. When you are reading case after case during the semester, it is easy to miss the overall course ideology, unless you have a good professor who will tie it all together for you. This book is good at providing the appropriate level of detail to the student for a comprehensive review of the critical points in Con Law I.

I bought the book and started to read: Page 3 says: "To see the code for this book, go to ...and type ..." Apparently, the link is broken.

And I turned to Page 0 and found author's e-mail... Well, the message was bounced back after seconds.

What can I say more?

This book does not go into much detail, but provides a well rounded introduction to many Linux programming concepts.
Consider this book a nice transition from basic C to Linux programming, before hitting the advanced material.

Overall, this book is a good book. It is a good start for the beginner. The examples are good and provide simple explanations of how to use Linux features.

There are some topics that could have benefitted from a more in depth discussion. If you are looking for a basic overview of Linux programming features, this book is a good start.