Dropped in the box via e-mail: Beyond MVC: A New Look at the Servlet Infrastructure. Just some days after making public some of my own views...

And I'm really sold before it even begins:

...my goal with these two articles is to convince the servlet middleware community once and for all to put the dark days of MVC behind us and to lay the groundwork for completely new, nonderivative servlet middleware architectures that better address our common needs...

After reading it:

• Very well written.
• Interesting (historic placement, well argumented) and thought provoking (I like looking through other people's telescopes)
• Nothing less then a must read.
• Still, I'm disapointed enough at this time to be impatiently waiting for the second part :-) So what am I missing:
• Where is the role of the URI in dynamic web apps? (some lessons from ReST?)
• Why not holding on to the Business-Modelling relevance of the C in the MVC approach: realize a 1-1 mapping between the Analists' UseCases and the coded Controllers. The biggest challenge IMHO offered by the stateless nature of the web, is to re-create this logical spot to technically encode the clear sequential user-system interaction-scenario as written down in the UseCase.
• Why so easily going by at the presentation problem? At Javapolis I saw Craig McClanahan tell about JSF: "this stuff is view only, we're not looking into controller issues ATM". In this story I see the other extreme and I really think we should take a more holistic approach first. (That is in fact another lesson to learn from classic MVC, no?) Don't get me wrong. We do need sound SoC. But you can NOT get there by ignoring those concerns you don't like in the picture. So while not wanting to (sic) 'replicate those extremely advanced presentation techniques' the current approach very much lacks the contract to integrate those.
• I guess my disapointment should go away after taking some more time and actually getting into the nuts and bolts of this shocks thingy

Meanwhile I'm left to wonder if this article will really set the bomb under this overdue web-MVC-mantra. Given my earliest posting on this topic last year (almost the very day even) I'm sure I'm ready to wait some longer :-)