Dashboard > RIFE > ... > Web engine > Inheritance control
RIFE Log In | Sign Up   View a printable version of the current page.
Inheritance control


Added by Geert Bevin, last edited by Klaus Meffert on Aug 19, 2006  (view change) show comment
Labels: 
(None)

Normally, when elements are inside an inheritance structure, the inheritance context remains active until all the parent elements correctly activated their child trigger. However, it's quite common to create isolated parts of a site that are 100% independent of the inheritance (navigation frame, embedded login/logout box, ...). While these works, the urls that are generated for their exits aren't nicely readable. This seemed quite artificial and not visitor-friendly since there is no apparent application-related justification for this behaviour.

The flowlinks that originate from these exits now have the possibility to completely cancel the active inheritance stack. This is simply done by adding the inheritance="cancel" attribute to the flowlink declaration.

For example :

<element id="FRAMEMAIN" file="frames/main.xml">
  <flowlink srcexit="framenav" destid="FRAMENAV" inheritance="cancel"/>
  <flowlink srcexit="content" destid="FRAMEMAIN"/>
</element>

Turns the following link in the navigation frame :

http://localhost:8080/05_inheritance/?childrequest=&
triggerlist=AgAAAAIAAAACAAAAZWxlbWVudHMvZnJhbWVzL21haW4ueG1seABlbGVtZW50cy9mcm
FtZXMvbmF2aWdhdGlvbi54bWxkAG5hdmlnYXRpb250AGhvbWVkAGEAZABzAGQAeQA%3D

Into :

http://localhost:8080/05_inheritance/home

Of course all inheritance behaviour is lost, but in this case this is what is actually wanted.



Are you enjoying Confluence? Please consider purchasing it today.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.1a Build:#515 May 19, 2006) - Bug/feature request - Contact Administrators