Initial assignment to Judy to build a simple test application that shows some of the bookmarking techniques available in JSF 2. We'll use this application to discuss how ICEfaces 2 might be able to support/enhance bookmarking in applications that use Ajax, applications that use a "single page" design, etc.

Although most of the methods used for jsf2.0 navigation are working properly, the main problem seems to be that the current design has buttons or links with full page submit (by not putting <f:ajax/> tag with them), but ICEfaces capability automatically adds ajax-enablement to everything on the page (including these buttons and links), so not full page submit and the URL does not get updated when things like the following are used:-

<h:commandButton value="Go Back" action="redirect"/>

In this case, the redirect will be done to /redirect.xhtml, however, the URI is not updated. So...if you redirect from
http://localhost:8080/navigationLinks/redirecttarget2.jsf
then the correct view is shown, but the URI is still showing the page that was redirectted from --> redirecttarget2.jsf.

We expect that the std. JSF 2 bookmarking support will work with ICEfaces also, perhaps in conjunction with an "<f:ajax disabled-true>" configuration.

In any case, testing and sample application(s) need to be completed.

The only example/resource I could find that illustrates the JSF2 support for bookmarkable links is this one: http://java.dzone.com/print/13695?page=0%2C1

Unfortunately, it will require a dev-team member to assemble this example and get it working in a form that QA can use to verify the feature, by injecting ICEfaces into the configuration, using ICEfaces comps, etc.

Are we using page parameters in the ace-showcase?

We are not currently using page parameters in ace-showcase. I started trying to implement it, but it just didn't make sense as each example had a different xhtml page so different page to navigate/bookmark to.
Otherwise, we might have had something like ...showcase.jsf?example="button"
but that would have complicated the facelets compositions and includes.
So...went for ...../sliderEntry.jsf, etc one for each example.
A better test would be a CRUD example which uses an id for a page parameter or something simliar...perhaps if we wanted to bookmark which tabIndex in an tabSet example???

not sure what you want to do about this now?

So at the moment we have h:link with bookmarkable pages in ace-showcase?

Basic support is in place and demonstrated by the ace-showcase.