I use pages.xml which, IMO, puts the logic where it belongs as generally
conversations are scoped to a section of the application. As page flow is
defined in the pages.xml file, it makes sense to demarcate the boundaries of
the conversation there.
MSchmidke wrote : 2. Beginning a conversation
Yes ... perhaps this is the problem. Until today I did not understand this page
flow thing.
I've been a WebObjects developer for years, had the luck to skip Struts and
Seam-less JSF.
In WebObjects, every html page is represented by a Java class, and directing to
a particular page from an
MSchmidke wrote : And since I write many beans which rely on
flushmode=MANUAL, I like to have a common base class which sets this for all of
them.
Maybe instead of a common base class, a way to globally configure the flushmode
setting. Say, a way to configure begins to use flushmode=MANUAL by
jacob.orshalick wrote : Say, a way to configure begins to use
flushmode=MANUAL by default. Maybe this could be configured in components.xml.
+1
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121680#4121680
Reply to the post :
JIRA issue raised:
http://jira.jboss.com/jira/browse/JBSEAM-2512
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121684#4121684
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4121684
Sounds like a good idea. Even if it would be the silent default, the natural
think to do would be to start doing explicit flushes when you don't see
anything sticking in the DB...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4121682#4121682
Reply to the post
