This content has been marked as final. Show 2 replies
what about writing a managed bean that acts as the model for the graph instances. Then when instantiating the bean you query the binding layer for the data, cache it in the bean (ArrayList or Hashmap to have the graphs reading from it. This will make one access to the database for all.
Alternatively, if the graph is based on a single iterator in ADF binding then there should be only one query required. You can e.g. set the iterator refresh to refresh if needed.
Thanks for your thoughts.
I'm currently implementing your idea of having the backing bean manage the tabularData.
I think what we will do is write a function in the DB to pull all the data we need and return that data to calling method in the backing bean. It will then be sorted out into tabular data sets and distributed to each graph and gauge as needed.