thanks for the answer. i did some experiments which seem to confirm it.
the source of my question is in the paging example in the documentation:
http://docs.jboss.com/seam/1.2.1.GA/reference/en/html/framework.html#d0e5897
in the example, the paging parameter (firstResult) is passed as a
solved.
what i was looking for was the @RequestParameter annotation.
best regards
michal
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4081888#4081888
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4081888
files and did not come across anything relevant. Am I missing
something? Is it some default behaviour?
Thanks for any info.
Michal Przadka
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4081524#4081524
Reply to the post :
http://www.jboss.com/index.html?module
hello,
unfortunately i did not manage to solve the problem. in the end i redesigned
the UI so the problematic situation does not even occur. im not happy with it
though...
regards,
michal przadka
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4080529#4080529
| messageUnexpected error, please try again/message
| /redirect
| /exception
|
| /pages
|
best regards!
michal przadka
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4079506#4079506
Reply to the post :
http
hi,
thankts for the reply. unfortunately it does not seem to be the contexts issue.
adding
| Contexts.getConversationContext().remove(research);
|
in the session bean (just before the return call) did not help.
i also tried with:
| Contexts.getPageContext().remove(research);
|
