RE: design question

[CONNER, BRENDAN \(SBCSI\)]

Title: Message

One thing to be aware of is that, if someone leave the pop-up window open and then starts a new browser that launches the same pop-up, that old window will get re-used (since it has the same name), and JSF will *definitely* get confused at that point.  Our application is a company-internal one, so we just train the people to be aware of that.  I would be hesitant to unleash that on the general public, though.

 

- Brendan

-----Original Message-----
From: CONNER, BRENDAN (SBCSI)
Sent: Tuesday, October 11, 2005 4:06 PM
To: 'MyFaces Discussion'
Subject: RE: design question

You can have both the base page and the pop-up execute under JSF.  What we've done to transfer data back to the base page (and to close the pop-up) is to do that through _javascript_.  Make sure you're using client-side state saving, though.

 

If you do this, your pop-up window can actually consists of several JSF pages in a conversation without difficulty.

 

The trick is getting the pop-up to launch correctly.  See Core JavaServer Faces for an example of that.

 

- Brendan

-----Original Message-----
From: Rafael Nami [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 11, 2005 4:00 PM
To: MyFaces Discussion
Subject: design question

Good afternoon everyone.
Our team is having doubts about a usecase needed in our app.
We have a page, that calls a popup that searches some stuff to add,
and adds this stuff to the parent page. The parent page have to be
responsible to save everything. What is the best practice?
Put the entire backing bean in session scope? Use x:saveState in both
parent and popup pages to save the backing bean?

Thanks

Rafael mauricio Nami