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?
- Re: more on architecture really confused on some... Zhong Li
- RE: more on architecture really confused on... CONNER, BRENDAN \(SBCSI\)
- Re: more on architecture really confuse... Zhong Li
- Re: more on architecture really con... Zhong Li
- Re: more on architecture really... Zhong Li
- RE: more on architecture really confused on... CONNER, BRENDAN \(SBCSI\)
- RE: more on architecture really confused on... CONNER, BRENDAN \(SBCSI\)
- RE: more on architecture really confused on... CONNER, BRENDAN \(SBCSI\)
- Re: more on architecture really confuse... Mario Ivankovits
- Re: more on architecture really con... Martin Marinschek

