Sep 6th, 2006, 12:41 PM
Originally Posted by Arno Werr
Jan 29th, 2009, 12:00 PM
The idea of JSF being easy and extendible is the biggest mistake that someone can make actually..
On the surface the technology seems to be fine...but as soon as you try to do things like custom components or try to do something like central exception handling without forcing the developers to deal with runtime exceptions in their mananged bean code, you run against a wall...
JSF is one of the few specs in java that are surely unfinished and one of the technologies that just ignore a lot of the best practices in software development ....
Try to do form based validations where certain fields have a condition to another field in the form etc...
Component based validation is no problem at all but if you want to write a custom validator that should validate a form instead of a component...you're screwed etc..
Just search the net for reviews and you will see that JSF is for sure not the way to go for big projects....
Mar 24th, 2009, 04:06 PM
What are you talking about here? Nobody uses pure JSF these days. None of your mentioned problems is a problem anymore.
Mar 24th, 2009, 04:42 PM
we're using the IBM JSF implementation....
They're solved? Could you explain me in detail how exception handling is solved with runtime exceptions? (No sorry, im working in a portlet environment....web.xml error-page directive wont work for me)
How do you do form based validations with your custom validators?
Im just curious