-
1. Re: progress bar pooling and
andrei_exadel Oct 8, 2008 12:09 PM (in response to elik)What RF version do you use?
-
2. Re: progress bar pooling and
elik Oct 8, 2008 12:50 PM (in response to elik)The latest one... 3.2.2.GA
-
3. Re: progress bar pooling and
elik Oct 8, 2008 12:57 PM (in response to elik)Maybe, this is not the problem of the "enabled" attribute. I have the same condition of the "rendered" attribute of the command button, that starts the progress. And this button is not became enabled too... Unfortunatly, I can't determine the main reason of this problem exactly.
-
4. Re: progress bar pooling and
elik Oct 8, 2008 1:02 PM (in response to elik)Sorry, I meant "disabled" attribute of the command button.
-
5. Re: progress bar pooling and
andrei_exadel Oct 9, 2008 5:22 AM (in response to elik)Hi,
When I looked into this I found that progress bar dont stop polling after enabled attribute has been changed on server.
I added this issue to JIRA and fixed it: https://jira.jboss.org/jira/browse/RF-4585.
But I see this is not a cause of your problem because your command button cannot become enabled.
Seems you did not re-render components after process finished.
If you have progress bar all time polling it means that progress bar value never reach to max value.
Anyway I can't say more without server side code posted here. -
6. Re: progress bar pooling and
elik Oct 9, 2008 8:04 AM (in response to elik)Thanks for quick reply :) But as you can see from above code, I reRender progressPanel after progress completion (reRenderAfterComplete="progressPanel..."). This panel contains my button, so I expect to see enabled button after "reRenderAfterComplete" action is completed. So, I think these things are coupled.
-
7. Re: progress bar pooling and
andrei_exadel Oct 9, 2008 9:00 AM (in response to elik)You right in case if you sure that progressBar reaches complete state.
I mean may be server sets enabled to false before max value got.
So, process finished, but progress bar continue polling.
You should be sure that sure that #{pageBean.processLaunched} triggers to false ONLY after complete state has been reached.