Hi Dan,

What you could do is adding managed property to the page bean.
That managed property is a session scoped bean (like a business bean).
The getters and setters of the page bean just delegate to the session scoped 
business bean.
That will at least lessen the burden of cleaning up session scoped beans.

Paul

-----Original Message-----
From: Chris Gibbons [mailto:[EMAIL PROTECTED]
Sent: donderdag 5 april 2007 22:15
To: [email protected]
Subject: RE: PPR and request scoping


I don't have to do that will all values, usually just with a form
submission, I noticed an autosubmit triggers a new bean being created,
but the values tend to be persisted into the new bean. I may be way off
though I'm still a struggling newbie in the world of Trinidad.  It's
frustrating, but has some really nice features that don't exist
elsewhere.

Chris

-----Original Message-----
From: Daniel Hannum [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 05, 2007 2:00 PM
To: [email protected]
Subject: RE: PPR and request scoping

Good idea. Does seem like a lot of work though. I want the whole page to
hang around across auto-submits. If that's the only way, I think I'll
have to deal with session, and wish upon a star that someday we may be
able to declare a bean scope of "page" in faces-config.xml! (Or I guess
have a look at Seam or Spring 2.0.)

Are there other options within JSF? 

-----Original Message-----
From: Chris Gibbons [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 05, 2007 3:42 PM
To: [email protected]
Subject: RE: PPR and request scoping

You can put any values that you want to maintain in the pageFlowScope
and in your getter for that value, check to see if it exists in
pageFlowScope first, and if it does, return that value rather than the
initialized value when the bean is created.

Chris

-----Original Message-----
From: Daniel Hannum [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 05, 2007 1:43 PM
To: [email protected]
Subject: PPR and request scoping

Hi,

 

It would appear that if an autoSubmit/PPR happens on a page, any
request-scoped backing beans are recreated. I guess that makes sense...
the extra submit is an extra request.

 

First, am I correct? Second, does that mean that every bean backing a
page that uses autoSubmit (I use it a lot) needs to be session scope?
That brings its own problems. Perhaps there is another option? I even
saw Oracle documentation saying that "page backing beans are usually
request scope", but alas, they cannot be!

 

Any help is appreciated.

 

Dan


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to