View Source

h2. Overview
_Since 3.0_

You can use the _icecore:push_ tag to configure Ajax Push behavior on a per-view basis.

{tip}See the ICEfaces Showcase [Live Demo|http://icefaces-showcase.icesoft.org/showcase.jsf?grp=aceMenu&exp=pushBean] of this component, complete with source code.{tip}

h2. Getting Started

To use the _icecore:push_ tag, first declare the core namespace:

{panel}
{code:html|borderStyle=dashed}
<html ... xmlns:icecore="http://www.icefaces.org/icefaces/core">
{code}
{panel}

Then add the _icecore:push_ tag to your page markup, setting the required group attribute. A view can be added to one or more push groups by adding one or more occurrences of this tag.

{panel}
{code:xml|borderStyle=dashed}
<h:body>
<icecore:push group="groupNameA"/>
<icecore:push group="groupNameB"/>
...
{code}
{panel}


h2. Attributes
{tip:title=TagLib Documentation}This section covers attributes involved in the typical use-cases for this component. For reference, the complete taglib documentation for this component is available [here|http://res.icesoft.org/docs/v4_latest/core/comps/tld/icecore/push.html].{tip}

{panel}
*group (since ICEfaces 3.0)* Allows control of the current view being added to a push group. This is a mandatory attribute specifying the group the view must be added to.
{panel}

h2. Use

The _icecore:push_ tag allows more fine-grained control than PushRenderer.addCurrentSession() since only the current page is added to the push group, rather than all pages in the session. This makes it best suited to applications where a small subset of pages require push functionality. If you require shared push functionality on all application pages, PushRenderer.addCurrentSession() is preferred.