For the last two-three months I have been working on JSF (My Faces) with facelets. The experience has been good for most parts. The components available out of the box with JSF implementations (standard, tomahawk, richfaces etc.) have been of great help with development. The decision of using facelets was a good one. It helped to make the view much easier to format for user experience. With all these good things, I found some really seemingly trivial but irritating issues.
- Handling blanks with input fields that are bound to non-string values is a problem (though luckily solutions are available - specific converters).
- There were scenarios where I switched from tomahawk components to standard components for making things work. The reason for which I never could understand.
- A navigation rule syntax which is really very verbose.
- A backing bean which can get quiet large and unwieldy depending on the features to be handled.
- Making pop-up screens for lookups etc. - I could never get it working.
Some of these can get irksome, but I still felt that with Facelets, JSF makes web development far more easier.
I would like the JSF gurus to throw light on how these problems can be handled and also add on to the list of the advantages and issues of JSF. It would be of great help to me and many others