JBP 2.2.0 Documentation Question - portal tree?

[bsmithjj]

Next question...

In the documentation, this tag is documented as:

<parent-ref> Indicates whether the object should be hooked in to the portal tree.

What is a portal tree? (I have searched the ref. manual and there is no definition of this term...)

What does it mean to be 'hooked in to the portal tree'?

What are the allowed values, attributes, etc. and their meanings for <parent-ref>?

Thanks

[mholzner]

All PortalObjects make up the 'portal tree'
These are the portals, pages, and portlet windows that are defined in your portal runtime.

A page is a child of a portal, a window is a child of a page. Pages can have children pages. To express where you want a page to be placed in that tree (as a child of what) you can use the paret-ref element.

Let's say you have a portal called 'MioPortale', and a page called 'PaginaMia'
Now you defined a child page of the PaginaMia called 'Picola' (a page that should be navigable only in the context of the 'PaginaMia'; or in other words: a page that has detail information that makes only sense in the context of the 'PaginaMia'; the navigation portlet on the left should only show this child page, when the current page is the 'PaginaMia'; ...)

to achieve that, reference the 'MioPortale.PaginaMia' as the parent ref of this new page, like:

 <parent-ref>MioPortale.PaginaMia</parent-ref>

[pmn92]

By the way, I understand that it is possible to not specify any parent ref for an object. The object is then not a part of the tree and therefore sort of hidden from the admin tree. Correct?

There is also some confusion with the "portal tree", "portal" and "page". As pages can be organised in a tree manner, ie with subpages, it is not crystal clear what makes a difference between "portal" and "page". Could you explain the difference? thanks.

[mholzner]

"PMO" wrote:

By the way, I understand that it is possible to not specify any parent ref for an object. The object is then not a part of the tree and therefore sort of hidden from the admin tree. Correct?

Not sure, I haven't tried that, but it sounds plausible.

"PMO" wrote:

There is also some confusion with the "portal tree", "portal" and "page". As pages can be organised in a tree manner, ie with subpages, it is not crystal clear what makes a difference between "portal" and "page". Could you explain the difference? thanks.

A portal is a 'namespace' to group multiple pages, and set some general features for the group (like the supported modes and window states).

A page is a 'namespace' to group portlets, and arrange them int the way they should be displayed. Since it is anticipated that portals will end up with many pages, a page hierarchy was introduced to better allow grouping and navigation of pages.