This content has been marked as final.
Show 2 replies
-
1. Re: Conversation ends but new changes arn't reflected from DB
blabno Mar 29, 2010 3:31 PM (in response to shanikaweerapperuma)Have you checked on debug if query gets executed after update?
As to me the condition blocks it :<action execute="#{xxx.query}" if="#{XX.referrer == '/showList.xhtml'}" on-postback="false"/> </page>
If you redirect from i.e. '/details.xhtml' then it will not be fired.
For sure objects from conversation where you do the update are not transfered over redirect (before-redirect=true).
Do you use conversation for browsing the list also? If so, than it is a bad habit (session, and thus memory usage, rows rapidly). It does not cost that much to retrive 20 records from database each time (provided you do not fetch images from DB).
-
2. Re: Conversation ends but new changes arn't reflected from DB
shanikaweerapperuma Mar 30, 2010 2:56 AM (in response to shanikaweerapperuma)Hi Bernard,
Yes, my query method does get executed but still displays the old data.
No, I don't use a specific conversation for querying. What I meant was when @End is specified, it must end the current long running conversation. What I wanted was to make sure that the above issue wasn't due to having the same long running conversation when querying the list back. According to my understanding, @End switches to a temporary conversation (as there is always a conversation involved).
Now I have removed all of the above "action execute="#{xxx.query}"
..." part from pages.xml and am using a factory method (@Factory) for the query method so that it must automatically display the latest results list upon updating a record and loading the list page. But still it gives the old data and untill I open a new browser window I cannot get the changes reflected being in the same browser (session).
Any idea why? Please help.