Craig, Thanks for the explanation.
Historically, "backing bean" is a design idiom, not a required feature of the specification.
OK, but the term "backing bean" is used in a few places of the spec, and it would be nice if the spec defined it on the first encounter (or referred the reader to a glossary). :-) There are other terms, such as a component's "local value" that are used in the spec, without first being defined. Sometimes later, probably by reading the JavaDocs, the reader learns that the local value of a component is the value that is stored in a UIComponent instance's value property (am I right?) but, again, it would be better to have it defined on the first encounter.
Don't tie your design down to someone's definition of an idiom ... look for the patterns that make the most sense for your application architecture.
Actually I have a hard time coming up with a low-level architecture based on JSF. I can see many fellows just make every managed bean session-scoped but that's not a solution, is it? I have to admit that I am a newbie in this area but I thought understanding JSF should be easier than what I am going through. Nevertheless, a JSF blueprint project would be great. Best regards, Behi -- "Science is a differential equation. Religion is a boundary condition" - Alan Turing Behrang Saeedzadeh http://www.jroller.com/page/behrangsa http://my.opera.com/behrangsa
