Head First Servlets & JSP by Basham, Sierra & Bates. (HeiFer'S Joe). Chapter Five Review.

Now I'm toward the middle of reviewing Chapter Five, "Attributes and Listeners", about to look at a list of the Eight Listener Types.

I gotta admit I'm rather enamored with Model-View-Controller (MVC) pattern, so I like to think about listeners from that perspective. I've even printed an MVC diagram as a kind of mental map for these, to decide, where would each kind of listener should go.

Because this is the deal with listeners within MVC: View listens to model changes, and Controller listens to the view's user gestures. But Model doesn't listen to anybody or have a handle on anything outside of itself; it's completely self-contained. Model is what the application would be if it didn't have any user interface.

My sense has been, according to the book, generally servlets are part of the controller and JSP's are part of the view. See Chapter 3, diagram on page 88. Attributes? Usually part of the model, I would think.. But if an attribute were a database connection, that makes it part of the controller's plumbing.

But from looking at these listeners, they don't seem to fit nicely into MVC. For example the servletContextAtributeListener. If context attribute were part of the model, the listener should be view. So, some JSP could be notified maybe. Context attributes wouldn't be part of the view would they? And who listens to the controller? Nobody. Well maybe this just goes to show, there are other places for listeners, outside of MVC. Or maybe I can say it's part of the controller, listening to other parts of the controller...

Reading: Writing Effective Use Cases, by Alistair Cockburn

Need to re-evaluate, re-estimate a project at work. So I'm hoping this book will help, and I've downloaded a notes application to support my plan, the free Requirements Management Database from OpenNTF.org; apparently the application was created by Dave Parillo of Rite Solutions, and now I intend to use the application as I go through the book. Hopefully I can use the application at work --Will it work in ND 6.5? Anyway here goes.

From Chapter 1: Introduction

"...are fundamentally a text form, although they can written using flow charts, sequence charts, Petri nets, or programming languages..." I was just curious about the whole Petri net concept.

I admire this work but.. this is going to put me to sleep. Of course, most tech books have the same effect.. Maybe I'm spoiled by Kathy Sierra and Bert Bates. Oh and I don't think I'm going to have time or energy to do the exercises.

Jaye started teaching at College of Wooster

Beginning and Advanced French.
(retro-posted)

Dave started new job in central OH

I'm very happy; it's exactly my line - Lotus Notes/Domino/Web/Java software development. It's near Marysville which is commuting distance, about 45 minutes from our new residence: Columbus, OH.

(retro-posted in late 2007)