You can't dynamically add custom controls that way, so you have to add every possible one to every page you want to use. That can get messy and non-performant. The xp:include allows you to calculate what you want to include, without the extra overhead. 

 

set up param for the same xsp based on your business logic
Product.xsp?productID=1111&&option="yes"

 

different custom control being included can read the value from these GET parameters then do whatever you want

or you can use scope variable as well......

regards

wei

Any further joy with xp:include?

I can't get it to dynamically load a page via the setPageName method. 

Although the property appears to be set correctly, the page does not refresh (even with a Partial Refresh).

Only when I click F5 does it update. 

Any ideas? 

OK, after a bit of experimenting (with a closer look at hints in previous posts), I've been able to get the xp:include working dynamically.

I used the technique of passing parameters along with the xPage address.

 

As an example, bringing up the "menu" page with an included page of "test1" can be done with "/menu.xsp?Page=test1.xsp".

The xp:include "pageName" attribute is calculated from the "Page" parameter passed to the webpage via a 'context.getUrlParameter("Page")' call.

 

Simple when you know how.... 

 

I've tied this to a menu tree on the left hand side of a xPage to allow navigation of various views/forms by clicking items in the tree.

The overall frame of the xPage only needs doing once with the tree navigation, headers, footers, etc. and then each view/form is embedded when the item is clicked. This keeps the real working pages quite small and leaves the surrounding frame separate and consistent across all pages.