n.b.
pageContext.set("foo", "bar");
| assert !pageContext.contains("foo");
passes when you are in the INVOKE APPLICATION phase.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097903#4097903
Reply to the post :
http://www.jboss.com/index.html?module=bb&op
Yes.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097901#4097901
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4097901
___
jboss-user mailing list
jboss-user@lists.jboss.org
Thanks for explanation, Pete.
It seems i'm quite not understanding it completely yet..
Does that mean, during the next request it won't be present anymore?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4097884#4097884
Reply to the post :
http://www.jboss.com
The page context is split over both the previous and the next request when you
are in the INVOKE APPLICATION phase. You read from the previous page context
and write (i.e. remove) from the next page context. So the above is totally
expected.
View the original post :
http://www.jboss.com/inde
I still didn't figure it out.
So i do it using a redirect to the same view id depending on the called action:
|
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095390#4095390
Reply to the post :
http://www.jboss.com/index.
