These forums will serve as an alternative to the existing User’s Group mailing lists for PrettyFaces, PrettyTime, and SocialPM.

Take a few moments to register for a forum account; start asking questions!

Please enjoy, and as always: thanks for supporting us!

A new version of PrettyFaces for JSF1.1 (historical support) is now available for download. This version is feature-complete, but we are looking for feedback on compatibility and functionality that may be broken with various implementations, so please post comments!

It should be noted that JSF is now on version 2.0, and PrettyFaces 2.0.x should be used. E.g: PrettyFaces 1.2.x should be used with JSF 1.2.

1.1.0: jar, src

New versions of PrettyFaces for JSF1.2 and JSF2.0 are now available for download:

1.2.4_GA: jar, src

2.0.1_GA: jar, src

Minor Release: 20090613

1. Fixed non-redirecting faces-navigation integration.
2. Enhanced null handling for mis-configured viewIds
3. Now supports browsers with cookies disabled

Version 1.2.3_GA: binary, source, documentation (stable)
Minor Release: 20090415

1. Added optional <action onPostback=”false”> boolean flag to prevent action methods from being called on form postback. Defaults to true;
2. Added optional <query-param decode=”false”> to prevent java.net.URLDecode.decode() from being called on a specific managed query-parameter. Defaults to true;
3. Added unit tests for several critical classes.
4. Minor to moderate refactoring of PrettyFilter/PrettyContext

Version 1.2.3_RC1: binary, source, documentation (stable)
Minor Release: 20090319

1. Managed query-params now accept multiple parameters of the same name: E.g.: String[] names — would accept a list of parameters (with the same name) from the request
2. Enhanced configuration loading — PrettyFaces now looks for /META-INF/pretty-config.xml by default, in addition to accepting a comma-separated list of user config-files in the web.xml init param: com.ocpsoft.pretty.CONFIG_FILES — submitted by Aleksei Valikov
3. JSP support for standard attributes on the pretty:link tag has been fixed. The pretty link will now accept style=’mystyle’ and other attributes — from Derek Hollis at OcpSoft

Well folks, for those of you who were hoping JSF 2.0 would contain the URL rewriting tools that many had asked for, unfortunately it looks like it’s not going to make it into the official spec. Bookmarking a page, or pages in JSF has been a heavily requested feature, but according to this discussion, is currently out of scope.

But that’s ok…

The PrettyFaces JSF Bookmark extension has been updated for JSF 2.0, and is ready for public preview (download below).

Only minor updates were required, and should be stable, but due to the un-finalized nature of JSF 2.0 itself, the extension may change as well.

Please note:

Parsed parameters are now assigned to Managed Beans after the RESTORE_VIEW phase. Previously this had taken place before the RESTORE_VIEW phase.

Version 1.2.0: binary, source

Major Release: 20081231

1. Added managed query-parameter support for URLs and JSF forms
2. New URL Buffer component makes using dynamic URLs easy
3. URL encoding/decoding now complies with W3C standards
4. Dynamic View Ids now allow returning pretty:navigation strings to display another view without issuing redirect or changing the client browser URL
5. Enhanced exception messages for much of the URL Parsing and Building

Design systems which are capable of change, and you will be much more ready for the future.

Always:

• Program by Intention – “begin by focusing on motivation or desire”
• Analyze the the varying objects and forces in your system, encapsulate them
• Favor aggregation/delegation over inheritance
• Seek the Open-Closed principle – “open to extension, closed to modification.”
• Design to interfaces – “couple to interfaces, not implementation”
• Encapsulate the constructor – use Object.getInstance()
• Encapsulate variation – “what is hidden from you, can be changed”
• Think about how you test a design, when you create it.
• When choosing between two designs with similar cost/risk, consider how easy/difficult it would be to refactor from each to the other, should the need arise.

Think:

Think about the forces of the problem (Do we want to use this pattern / design?)

1. Contextual forces – How will the environment around you and your product affect your system/design?
2. Implementation forces – Will this design work? Is it worth it? Is there a better way?
3. Consequences – What will the results of our actions be? What are the trade-offs?

Think about how you test a design, when you create it. When choosing between two designs with similar cost/risk, consider how easy/difficult it would be to refactor from each to the other, should the need arise.

“Good coupling is Intentional, bad coupling is unnecessary or Accidental“

Never:

• Never allow Redundancy – “Redundancy is DEBT; you always pay for it later”
• Never use ‘new Object()’ notation – Use dependency injection / factories / encapsulation.

Coupling Forces:

1. Identity – One type coupled to the fact that another type exists.
2. Representational – One type coupled to the interface of another.
3. Inheritance – Coupling to a superclass. Changes propagate downward.
4. Subclass – Knowledge that an object is part of a polymorphic set… “knowing the implementation of another.”

• Enhanced internal navigation/redirects. Returning “pretty:” from a JSF action method, or Pretty action method will cause a redirect to the current page. Effectively a refresh.
• Added the <pretty:link> component.
• Added attribute to Pretty action method configuration, allowing targeting of action methods to specific JSF phases in the lifecycle.

View the documentation here, for PrettyFaces.

—-

PrettyFaces is an OpenSource JSF extension which enables creation of bookmarkable, pretty URLs made easy. Our goal was to solve this problem as simply as possible, while still enabling a useful set of functions such as: page-load actions, integration with faces navigation, dynamic view-id assignment, and managed parameter parsing. All of this without introducing unnecessary coupling.