Sorry, I haven't had my morning coffee (GMT-6.00), so left in some extraneous words in the last e-mail that made it difficult to read. It was *supposed* to read:
I know that this doesn't answer your immediate question, but wouldn't it be easier and more explicit to put the common elements inside a JSP, and then to include that JSP inside each of two other JSPs, each with its own button that has its own action (update vs. create)? Then you wouldn't have this flag-setting and control issue happening underneath. - Brendan -----Original Message----- From: CONNER, BRENDAN (SBCSI) Sent: Thursday, March 02, 2006 9:44 AM To: MyFaces Discussion Subject: RE: JSF Bean Life Cycle Question I know that this doesn't answer your immediate question, but wouldn't it be easier and explicit to do put the common elements inside a JSP, and then to include that JSP inside each of two other JSPs, each with its own button that has its own action (update vs. create)? Then you wouldn't have this flag-setting and control issue happening underneath. - Brendan -----Original Message----- From: Anthony Hong [mailto:[EMAIL PROTECTED] Sent: Thursday, March 02, 2006 7:39 AM To: MyFaces Discussion Subject: JSF Bean Life Cycle Question I have a page for creating an object. I found update page have same fields except an internal ID and its button is updaing not creating. So I add a boolean field in control bean to represent current action is update or create. My control bean scope is "request" in faces-config.xml I enter create page, click save button, In that function, I change status to true which means edit mode. Then the update botton is displayed, but click that button has no effect, control bean method was not invoked. but boolean flag is OKAY, its true in that time What's wrong with it? -- Anthony Hong
