Page Scope inside a4j:include

[jethroborsje.j.borsje.dji.minjus.nl]

Hi all,

In my project I have a menu.xhtml which shows the menu build using RichFaces components. If I click on a menu item a URL is set on a Seam SESSION scoped component. After this I reRender an a4j:include which shows the selected URL:

<a4j:include id="content" viewId="#{navigationBean.url}" />

The page which I include here (let's call it page A) is backed by a PAGE scoped Seam component. After displaying page A I click on another menu item (let's say for page B) which results in page B being shown. If I now click on the menu item for page A again the PAGE scoped backing bean for page A is not recreated, i.e. its @Create method is not called.

I suspect this happens because using a4j:include does not cause JSF page navigation, therefor the PAGE scoped Seam component stays 'alive'. Is this correct? And if so: how should I use the PAGE scoped component in my case?

Best regards,
Jethro

[amitev]

a4j:include performs a synthetic navigation by changing the part of the view tree without changing the view-id.

[jethroborsje.j.borsje.dji.minjus.nl]

I understand, but is there a way to 'force' a PAGE scoped Seam component to be destroyed and therefor recreated on the next call from an xhtml page?

[amitev]

Try with a4j:keepalive and put the keepalive in the parts that are included in a4j:include.

[jethroborsje.j.borsje.dji.minjus.nl]

Adrian Mitev wrote on Jul 28, 2010 04:33:


Try with a4j:keepalive and put the keepalive in the parts that are included in a4j:include.

I just looked at the a4j:keepalive tag, but it does the opposite of what I want. I don't want the PAGE scoped component to stay alive. I want the PAGE scoped component to be destroyed when I navigate away from an included page to another included page. Is this possible?