Monthly Archives: October 2008

JSF 2: ProjectStage only half-baked

In JSF2 there are tons of new and interesting features. Some are big changes and some are really neat small additional things, like the ProjectStage Enum. Especially for tool-vendors (and component libraries) this is useful to specify the “runtime”. (Development

Posted in jsf, myfaces, trinidad

Client-side validation done wrong (with Spring-Faces)

In JSF there is no concept of client-side conversion and validation. All is done on the server, which means you notice some extra round trips in case there is something “wrong”. Eventually JSF 2.0 will change that… In the meantime

Posted in java, javascript, jsf, myfaces, spring, spring-faces, trinidad, web²

REST and JSF ?

JavaServer Faces is a great framework to build rich web applications, as shown in the following screenshot: As you see, the web application in this screenshot is more an APPLICATION, than web… A pretty rich user interfaces, which was composed

Posted in jsf, rest, web²

EJB lite ? I think I need help…

A co-worker pointed me to this article of a EJB 3.1 series. There is something in called “EJB lite”. Reading the section on EJB lite, I think I need some help… First of all, they strip out some of the

Posted in ejb, java

ADF Faces 11g release, demos and autoPPR (ajax)

You eventually noticed that the JDev 11g (including ADF Faces) is now out for production. Also, we updated the ADF Faces demo website: One of the cool, new features is something we call “auto PPR”. Here is the demo.

Posted in adf, apache, java, javascript, jsf, myfaces, oracle, web²

Nice Charts with Trinidad

Apache MyFaces Trinidad provides a lot of cool JSF components; a really nice one it the chart component. It offers several possibilities to visualize your structured data. Like this pie chart: To actual provide such a nice looking chart graphic,

Posted in ajax, apache, java, jsf, myfaces, trinidad, web²

identity checks with JavaScript

Every now and than, somebody asks why I am sometimes using three equal signs (===) instead of two (==), when comparing values. Simple answer is, that I am interested in the identity (type and value) instead of only the value.

Posted in javascript