[TYPO3-ect] MVC Project: CMEV introduction

[Christian Welzel]

Elmar Hinz wrote:

> I don't agree with the model of the 2 phases Faces Request and Faces
> Response. 2 phases are ok so far but I would place the Update Model
> Values into the first phase. I do think of a Store Phase and a Load

Do you refer to the picture in the manual ?
I think you misinterpreted it :) There are no 2 phases but 6 phases
that are processed serially. And the programmer has the possibility 
to force the system to skip certain phases (on error, on forward, etc).

As i understood the JSF (i'm a JSF noobie) the main idea is to build
a tree of UI objects that represent a specific view. In the normal case
this tree is build while rendering the output of a view for a request and
than serialized and saved (on server or client). a subsequent request
deserializes this tree (restore view phase) and the other phases are
applied. if any error occures the same tree is rendered again, but this
time the UI objects contain error descriptions in addition to the data
entered by the user. This way you can present the user a form a second
time with messages without writing any code on your own (assuming the usage
of std validators and stuff).

The self crafted code is only run if the cycle enters the "Invoke
Application" phase. The programmer of business logic does not need to
deal with input validation in this approach... very cool design IMHO.

Would be nice to have such mechanism in typo3...

-- 
 MfG, Christian Welzel

  GPG-Key:     http://www.camlann.de/key.asc
  Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15