Single "child" ViewObject with multiple ViewLink "parents"

Question

Hello,
The subject says it all. Is it possible to create View Objects and View Links appropriately such that
ChildVO = View Object child
ParentVO1 = View Object parent of ChildVO
ParentVO2 = View Object parent of ChildVO
both ParentVO1 and ParentVO2 can drive the specific rows detailed in ChildVO?
This occurs when we have a ChildVO used to navigate/browse search results and are providing different search mechanisms via ParentVO1 and ParentVO2 to limits ChildVO's rows.
Any suggestions? Apologies if this is a trivial/oft-posted question,
Joe

Answer 1

We have a similar scenario here - if I understand you correctly.
We have a worklist controlling an elaborated ViewLink cascade during normal operation.
The user can also switch to a demo mode where a different VO takes control over the whole detail shebang.
We do this by removing/creating the ViewLinks at runtime. We have designed the ViewLinks, so that their xml files are created, but we instantiate only one of them in the AM.
In the AM impl when switching to demo mode we do:
ViewLinkImpl link = getWorklistViewLink1(  );
if( link != null ) {
  link.remove(  );
ViewLink newLink = createViewLink( "demoViewLink",
                                         "demopackage.PacsDemoLink",
                                         demoMaster, proxy );
proxy.executeQuery(  );Switching back:
ViewLinkImpl link = (ViewLinkImpl)findViewLink( "demoViewLink" );
if( link != null ) {
  link.remove(  );
ViewLink newLink = createViewLink( "WorklistViewLink1",
                                         "demopackage.WorklistViewLink",
                                         reportMaster, proxy );
proxy.executeQuery(  );In order to make this as easy as possible, we introduced a proxy VO that has no real functionality but that ensures that only one ViewLink has to be "switched".
worklist ---- proxy ----- detail1 ---
                   |-------- detail2 ---
                   --------- detail3 ---In demo mode:
demoMaster -- proxy ----- detail1 ---
                        |-------- detail2 ---
                        --------- detail3 ---Works for us like a charm. Don't know if there is a more elegant solution.