3 Replies Latest reply on Sep 9, 2009 2:37 PM by nbelaevski

    multiple progressBars in one dataTable

    asookazian

      I have a JSF page which has a rich:scrollableDataTable in it that has a column which may need to render a rich:progressBar (i.e. if there are 5 rows in the dataTable, then I may need to render 5 progressBars).

      Is this possible to do in JSF/RF? In addition, I have two types of progressBars for two types of actions: one is a call to a web service, the other is a local CRUD operation.

      Once the user clicks the one and only submit button, I would like to show the progressBars "in action" without refreshing the JSF page. Is this possible to do? thx.

        • 1. Re: multiple progressBars in one dataTable
          asookazian

          I'm thinking that I'll have to create a new backing bean instance for each progressBar in a loop.

          If I do this will it work? Or does RF not support this functional requirement?

          • 2. Re: multiple progressBars in one dataTable
            asookazian

            And can I do the local CRUD operation (using EntityManager API) in the progressBar backing bean itself or must I do it in a separate Seam component as I am now doing?

            • 3. Re: multiple progressBars in one dataTable
              nbelaevski

              Hi,

              "asookazian" wrote:
              And can I do the local CRUD operation (using EntityManager API) in the progressBar backing bean itself or must I do it in a separate Seam component as I am now doing?


              This looks like the thing that will break tiers separation.

              Once the user clicks the one and only submit button, I would like to show the progressBars "in action" without refreshing the JSF page. Is this possible to do? thx.

              Yes, re-render it or just make transition it to "started" state using JavaScript API and then back to "stopped".

              And yes, rich:progressBar can be put inside rich:scrollableDataTable. If you have parallel processes, then several bean instances are necessary, otherwise a single one is enough.