JSF 1.2 – A dive into a legacy framework and why I think wicket/stripes still rock =)

So I’ve been doing a lot of java/ajax development recently, and having to compare frameworks was one of the main things I’ve had to do. I used JSF 1.2 actually due to legacy server issues, not 2.0 (which I hear is a lot better) but comparing it with Stripes/Wicket I must say that:

1. JSF has a LOT of issues integrating into existing browsers, 2.0 is probably a bit better but sometimes the pain of having to have ALL tags written for you is VERY troublesome. I recently had to use a rich faces fileupload component and the integration on some browsers has major issues. While it is good to have a very tightly integrated ajax framework it sometimes is painful when trying to integrate in something like the YUI components.

2. Stripes/Wicket are good because they leave a lot of the ajax development to yourself and provide a VERY awesome hands on approach where you can actually write your own code with minimal development time. I find this actually was easier on some other projects.

So in a nut shell… Id stick with Stripes/Wicket for a java serverside application as opposed to straight JSF as it is sometimes painful when dealing with all the pre-written javascript components.

I guess this brings up a philosophy:

1. A java server side framework should NEVER be so tightly binded to the front-end UI logic WHEN you are depending on browser support. Or provide some alternative to use the latest prototype/ajax libraries.

2. If it is tightly binded, there should be a very easy way to extend it and use it smoothly. JSF 1.2 was a nightmare !!! =)

For some reason, stripes/velocity and wicket still remain my top java web frameworks. Oh and forget to mention, integration with other flash/flex projects is a lot smoother without using JSF due to the freedom it gives you.

My 2c =)