Minor Release: 20090331
- Servlet forwards are working
Minor Release: 20090319
- 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
- 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
- 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
Setting up PrettyFaces is simple.
Add a comment with your experience or “gotcha!”
Java Server Faces is currently full of relatively undocumented features and behavior. As part of the JSF2 release, OcpSoft is working with a few folks at Seam/Redhat to try to address these issues and provide better documentation.
So you need a way to instantiate the 2.0 FacesContext in a Filter, but when you use the same method that you have in the past, you get NullPointerExceptions all over the place when attempting to access any values through El. The ScopedAttributeElResolver bombs when attempting to set values or access methods in backing beans.) It’s not too hard to get this working again.
A new major release of the PrettyFaces
JSF extension for Bookmarkable/Pretty URLs is now available for download.
A new release of the PrettyFaces
JSF extension for Bookmarkable/Pretty URLs is now availible for download. This release includes several new features.
What makes Pretty URLs in JSF so hard, and so slow?
Speed up development, reduce bandwidth, enhance user experience. This article gives a brief overview of JSF navigation, some of the problems, and potentially how to solve them by enabling bookmarkable, pretty URLs. Put simply… in my view, out of the box, JSF is a web framework designed for web-applications
, not designed for web-sites. PrettyFaces addresses most of these issues.
Target audience for this article:
- The reader is familiar with JSF navigation.
- The reader is attempting to create a JSF app with bookmarkable “pretty” URLs. E.g.: …/mysite/archives/2008/11/11/
- The reader is familiar with HTTP request/response at a basic level.
We’ve gotten a good number of comments from Lincoln’s
latest post on Spring Security and JSF
. A few comments have asked for further code samples on how to get this example working.
We created a runnable project for this example, and it can be downloaded here
Tutorials – What a nightmare
Everyone seems to be going through hell to get a fully functional JSF login page working with Spring Security (formerly Acegi,) and yes, I did too, but there’s an EASY
way to make this happen. And get this:
- It takes just five clear and well written lines of Java code.
First, the solution. Afterwards, the dirty details. (Spring 2.5.2 was used for this example, but this documentation is still relevant for Spring 3.x)
You can find a downloadable working example here
. There is also a followup article on post-authentication redirecting, here