Hmm. It simplified our life a lot! (Not just
with master-detail, but with anything that requires maintaining information
across pages.)
But,
with JSF, you can choose to use (or not use) whatever fits you
best.
-
Brendan
-----Original Message-----I really don't like saveState, it make things confuse and complex. We can use it to build a model/component, but not programmer/developer.
From: Zhong Li [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 01, 2005 4:50 PM
To: MyFaces Discussion
Subject: Re: more on architecture really confused on something (shocker:)
Myface can build a master-detail componets it myface can do it.
On 9/1/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED] > wrote:We don't put the bean in the session, but we *do* save it using <t:saveState>- Brendan-----Original Message-----
From: Zhong Li [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 01, 2005 4:42 PM
To: MyFaces Discussion
Subject: Re: more on architecture really confused on something (shocker:)Let us go back master-detail issue, I think we just follow nature way to do it.
1. we define MasterBean, MasterBeanList and DetailBean.
2. we have masterPage.jsp show masterBeanList. have a link <edit> goto detailPage.jsp show DetailBean
3. some editable fields on detailPage.jsp and a <save> button for save it.
4. after save return to masterPage.jsp or detailPage.jsp
Here is question we bump on,
1. how to goto detailPage.js by click <edit> link,
a) by dataTable so you can get detail row by actionListenter, but how to pass it to detailPage.jsp?
b) by a link with detailID parameter, this is easy and clear way to go.( I prefer it)
2. after click <save> button, how to refresh data.
remember, we are in request scope, so the data either retreive from database or you cache it somewhere. If we want still save the data in MasterBeanList, we have to put into session. I don't think it is good way to use JSF life cycle keeping data, I used cache for large data, also OJB has objectCache itself.
anything more?
