The views expressed on this blog are my own and do not necessarily reflect the views of any Organisations owning these products.I keep on doing R & D with different products in and around Middle ware stack and these posts are result of that.Most of the post are result of my own experiments or ideas taken from other blogs .If in any case You feel content is not right you can comment to remove that post. This blog uses the default features,cookies of blogspot.com
Tuesday, May 27, 2014
Understanding the difference between navigation model and the hierarchy model
There is much confusion about the navigation model and hierarchy model in the web center.
There is significant difference between the navigation model and hierarchy model.
Hierarchy model is just used to define you hierarchy for the security.
However navigation model is the one which actually defines how the pages will be navigated this will be clear will a simple example.
I have following entry for my hierarchy
Here as you can see that HelloWorld application also has a security so only after passing the security credentials HelloWorld page will be visible.
What about HelloArpit page? will it be displayed?
No because as we have discussed the hierarchy model defines the security for the pages.
Hence only after passing the security details the HelloWorld and HelloArpit page will be visible but will they appear in the same hierarchy as they appear in the Page hierarchy?
The answer is again no, It depends on the navigation model.
Now lets check out the navigation model. In the navigation model we have not defined any hierarchy and we have simply placed our page in the same level.
Now lets deploy this page and observer the result to understand the difference between hierarchy and navigation model
Before login
AFter login
So it is the navigation model which defines the actual hierarcy of the pages in the portal and the page hierarchy only defines the security prospect of it
No comments:
Post a Comment