Forum Stats

  • 3,837,032 Users
  • 2,262,221 Discussions
  • 7,900,184 Comments

Discussions

Refresh components outside the event root component - Panel Collection

Robert Šajina
Robert Šajina Member Posts: 94
edited Sep 25, 2017 5:07AM in JDeveloper and ADF

Hi,

After reading this post: https://blogs.oracle.com/jdevotnharvest/panelcollection-confusion-or,-what-is-an-event-root i understood what an event root component is and what is it doing.

My request is to refresh components outside the event root component.

We have a declarative component that has a Panel Collection inside. Panel collection is a event root component which means that when i press a button located in the panel collection toolbar, it only refreshes panel collection and it's children.

Because we can have more than one table in the same page, that is more than one declarative component, hence more than one panel collection. All tables on the page are depended on each other and needs to be refresh when an action occurs on each of them.

I know i can do it declarative by adding partialTriggers on each of table, buttons and so on, but this requires a lot of work and requires more work when something changes on the declarative component.

I would like to know if there is some way i can emit that event is occurred in the panel collection to the parent of declarative component so that all components of page(region) are refreshed(rerendered).

Basically i need that the panel collection is no longer an event root component, eater by somehow emitting a event to the parent, or just somehow saying that the panel collection is not a event root.

Thank you.

JDeveloper: 12.2.1.2.0

Tagged:
Robert Šajina

Best Answer

  • SanjeevChauhan
    SanjeevChauhan Member Posts: 1,554 Gold Trophy
    edited Sep 23, 2017 11:10AM Answer ✓

    If you want to refresh complete page, you can remove partialSubmit=true from button itself. That will make full page refresh. Yes its not a good practice as you are unnecessary refreshing all UI components.

    If you want selectively refresh few UI components then you definitely tell ADF, which are those components. The simplest approach is individual components provide partialTrigger pointing to button.

    If you don't want that then, I would suggest find a common parent component for all your tables. Set its partialTrigger pointing to button.

    Thanks

    Sanjeev

Answers

  • Timo Hahn
    Timo Hahn Senior Principal Technical Consultant - Oracle ACE Director Member, Moderator Posts: 38,561 Red Diamond
    edited Sep 22, 2017 8:54AM

    How about adding a global button to the declarative component which you can use to notify the page to refresh. The general implementation can be found here http://www.oracle.com/technetwork/developer-tools/adf/learnmore/24-generic-toolbar-component-169163.pdf

    You add an actionListener to the declarative component which you pass from the outside. When you need to refresh the page you call this listener from inside the declarative component.

    Timo

    Robert ŠajinaRobert Šajina
  • SanjeevChauhan
    SanjeevChauhan Member Posts: 1,554 Gold Trophy
    edited Sep 23, 2017 11:10AM Answer ✓

    If you want to refresh complete page, you can remove partialSubmit=true from button itself. That will make full page refresh. Yes its not a good practice as you are unnecessary refreshing all UI components.

    If you want selectively refresh few UI components then you definitely tell ADF, which are those components. The simplest approach is individual components provide partialTrigger pointing to button.

    If you don't want that then, I would suggest find a common parent component for all your tables. Set its partialTrigger pointing to button.

    Thanks

    Sanjeev

  • Robert Šajina
    Robert Šajina Member Posts: 94
    edited Sep 25, 2017 1:54AM

    Hi Timo,
    Thank you for your reply.
    I had a similar idea, to add a button outside of declarative component and somehow call it. Perhaps it is the best idea to move whole toolbar outside panel collection and somehow make it look that its inside panel collection

    Where would that actionListener point to? would we be required to add a button to every page?

    Robert

  • Robert Šajina
    Robert Šajina Member Posts: 94
    edited Sep 25, 2017 5:07AM

    Hi SanjeevChauhan,

    I have tried to remove the partialSubmit property (set it to false) but it doesn't do anything. I just need to refresh the next root component, and in our case that is <af:region>.

    We are trying to avoid setting partial triggers to components as its to much work, and will require more work if something changes on declarative component.

    Update:

    I have tried to set partial triggers of a common parent(af: region) programmatically to id of a panel collection(panel collection is refreshed every time a button is pressed) and it works very well.
    Now i just need  find a place/method that isn't called too many times, to add partialtriggers to af:region. If i manage to do it, i think we will keep this approach.

    Robert

This discussion has been closed.