This content has been marked as final. Show 1 reply
I think the options are
- create a second graph and hide it at runtime
- create the graph on the fly in a managed bean, wich is quite a bit of code to write, that is justified if the "generated" graph is different (e.g. different model data) for each master selection.
The first approach should be doable by detecting the selected information on the master graph and the query the detail iterator accordingly + displaying it.
The second approach is a deep dive into the graph model APIs because you will have to code this all manually. Note that we don't have documentation for this approach yet