My approach is to cache the parameters in a page scoped component.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043434#4043434
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4043434
It looks like page parameters don't get added if the page is redisplayed
(rather than a navigation performed). Gavin really need to look at this.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043198#4043198
Reply to the post :
Yes, page parameters don't seem to keep it.
My use case is more common than a theme change. The user is browsing some
bookmarkable articles, and if he wants to add a comment he has to log in and
stay on the same page. After the log-in the GET params disappear.
One workaround is to use a4j
I think page parameters should do what you are after?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043016#4043016
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4043016
___
The blogEntryId *is* a page parameter in the blog example.
I don't understand the theme stuff well enough to know of any easy way to pass
the page parameters along with the theme re-request.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4043034#4043034
Reply
