JSF Bookmark Tools - PrettyFaces improves the experience

Discussions

News: JSF Bookmark Tools - PrettyFaces improves the experience

  1. Visit the PrettyFaces site for complete documentation and downloads. Features:
    1. Replace jsf views (/faces/page.jsf) with pretty URLS (/mapped/page): The client browser never sees your JSF View ID
    2. De-coupling, separation of URL and View ID. Now with dynamic view ID mapping (through El method expressions) you can show different pages for a single URL.
    3. Page load actions call one or more action methods before rendering a view.
    4. Managed parameter parsing: HTTP parameters parsed from URLs are stored in managed beans for easy access from other Java classes, simply get a reference to your parameter bean and you have full access to your HTTP parameters.
    5. Navigation by ID: Define your view IDs in one place, reference them by assigned IDs
    6. Easy to configure. Requires only one consolidated XML configuration file.
    What makes PrettyFaces different: Read the full article, here.

    Threaded Messages (5)

    1. ...

    2. ...

    3. Page load actions call one or more action methods before rendering a view.

    4. Managed parameter parsing: HTTP parameters parsed from URLs are stored in managed beans for easy access from other Java classes, simply get a reference to your parameter bean and you have full access to your HTTP parameters.
    sounds like the section 3.3 (Seam page-oriented life-cycle additives) in the Seam in Action book I'm reading.
  2. PrettyFaces is different[ Go to top ]

    This is the only library avoiding the "POST-REDIRECT-GET" pattern in JSF. Reading the documentation seems that PrettyFaces modify the form action attribute, pointing to a bookmarkable view id instead of the default one (the current view id). This could bring some benefits. But Is there any integration issue with this approach? For example, what about coexistence with RichFaces (or other AJAX library)?
  3. Oracle ADF TaskFlows too[ Go to top ]

    This is the only library avoiding the "POST-REDIRECT-GET" pattern in JSF.
    The Oracle ADF TaskFlow also extends JSF with bookmark support: http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/taskflows_activities.htm#CIHEFDBF And other capabilities: http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/taskflows.htm#BACDBAJF
  4. Re: Oracle ADF TaskFlows too[ Go to top ]

    This is the only library avoiding the "POST-REDIRECT-GET" pattern in JSF.


    The Oracle ADF TaskFlow also extends JSF with bookmark support:
    Read again: I didn't say PrettyFaces is the only library providing bookmarking support for JSF applications.
  5. Re: PrettyFaces is different[ Go to top ]

    But Is there any integration issue with this approach? For example, what about coexistence with RichFaces (or other AJAX library)?
    Prettyfaces was developed for an application using RichFaces and Ajax4Jsf. So far there have been no bugs. PrettyFaces uses request dispatcher forwarding to avoid doing anything nasty to the ServletRequest or FacesContext