I have read that article a while ago,
one of the two main problems he noticed with JSF are sort
of addressed in MyFaces (and also mentioned in the article).
one being the low number of components, that definitely is addressed
in MyFaces, the other one being the lack of scopes between request and
session, a problem inherited from Struts (and that one inherited it from
the servlet/jsp specification)
MyFaces has addressed it by the introduction if x:saveState which can
extend the scopes to multiple pages by recycling saved objects
as long as it runs into x:saveState tags on the same object again and
again. The article has that one in there.
In my opinion x:saveState is superior to every dialog approach on the
web, because it keeps things small and simple. You do not need
another set of page flow syntax files, you just add an x:saveState and
use the existing page flow syntax of JSF to do your stuff.
The only culprit I have with x:saveState is, that you definitely have
your components serializable and thus you have to do extra work for
complex objects.
But I have discussed the problem with Martin, and he said to me that he
was not sure, but he thinks that the official standards say that the
beans must be serializable anyway.
Rails has a similar approach where you can extend the scope of an object
another request and once it is not extended anymore it drops out
(similarily interesting, because it opens another set of possibilities
of one time data handling upon a given state)
ir. ing. Jan Dockx wrote:
I just found a GREAT article:
<http://bugs.sakaiproject.org/confluence/pages/viewpage.action?pageId=4981&showComments=true>
Thanks, UCB!
Met vriendelijke groeten,
Jan Dockx
PeopleWare NV - Head Office
Cdt.Weynsstraat 85
B-2660 Hoboken
Tel: +32 3 448.33.38
Fax: +32 3 448.32.66
PeopleWare NV - Branch Office Geel
Kleinhoefstraat 5
B-2440 Geel
Tel: +32 14 57.00.90
Fax: +32 14 58.13.25
_
http://www.peopleware.be/
http://www.mobileware.be/_
