When I first heard about composite components in JSF 2, I asked "How do I make a date picker that yields a java.util.Date? I was told that can't be done without a custom component and lots of icky code. Not so--it is actually pretty easy. Here are the details."
A few weeks ago, Ed Burns posted a link to a blog on the JSF expert group mailing list, commenting “A nice one, but it doesn't mention JSF 2”. Ever the curmudgeon, I pointed out that it wasn't so nice that the blog's sample code used the JSF API in beans when it wasn't necessary—as does in fact a lot of sample code, even in the official Sun tutorials. Ed's response: “Cay, a blog comment by such an eminent citizen as yourself would certainly be noticed.” So, here is the curmudgeonly eminence's advice on how to stay away from the JSF API.
As I happily wrote about new features of JSF 2.0, my coauthor David Geary kept asking me how to run the examples in Tomcat 6. I kept putting it off—hunting down those JAR files and web.xml fragments is like eating soup with a fork. I finally got around to doing the research and thought that others might benefit from the (unhappy) results, if only to realize that this may be the time for switching to GlassFish.
Java EE 6 makes it pretty straightforward to crunch out a basic web + database application. This semester, my software engineering class is building web apps, and I decided it is simpler to have them use JSF + JPA in Glassfish v3 rather than some technology that seems easy at first and then lets them down. In this blog, I describe the recent simplifications, show how to set up Glassfish, give a sample app, and explain why we haven't quite reached Nirvana
In this blog, I go over a very simple JSF2+AJAX example and show how one can spy on the inner workings with the TCP monitor and debugger.
There are several blogs that tell you how to do fancy things with the upcoming JSF 2 (such as the excellent blogs by Ryan Lubke and Jim Driscoll). In this blog, I look at the other side of the coin--how the simplest things are working out. After all, if Ruby on Rails has taught us anything, it is that a technology that makes the simple things simple has a great shot at getting developer mindshare.
I wrote a quick-and-dirty quiz application to check whether my software engineering students do their reading assignments (or at least google quickly). Can an Elvis-level programmer do this in a couple of days with EJB3 and JSF? Here is my experience report.
I don't do LAMP, I do JELP (Java, EE5, Linux,
PostgreSQL). Here are instructions for installing Java, GlassFish and
PostgreSQL on Ubuntu 6.06 "Dapper Drake" Server Edition. No gotchas, just
a bunch of steps that I hadn't found together in one place.
JPA is the new object-relational mapping standard that you can use in EJB3 or in standalone applications. For the most part, it is phenomenally easy to use. But there is a trap that has bitten more than one developer. If you ever lie because your fibbing won't affect the database, your lies can still come back to haunt you. This blog gives two examples.
I am working on a glossary of EJB 3 terms that gives both the official definitions and explanations that Elvis can understand. (Elvis is the programmer persona who is neither Einstein nor the point-and-click/drag-and-drop "just give me a wizard" Mort.) What other definitions would you like? Do you spot errors or inaccuracies? Please let me know.