Home » Java » Apache Wicket vs. JSF PrimeFaces Evaluation

Apache Wicket vs. JSF PrimeFaces Evaluation

My team was recently tasked with selecting a replacement for GWT (Google Web Toolkit). We have a few pet peeves about GWT but our biggest is the compilation time.

It turns out there are quite a few options.  However, we didn’t have the luxury of trying out every tool.  Instead, we chose 2.

We decided that Apache Wicket and JSF PrimeFaces would be the most viable candidates taking into account the state of the current application.

We also decided that we needed to put together a proof of concept that was to be evaluated by the team and the client.  We had 2 teams of 2.  Each team replicated the same existing application screen with their chosen UI framework.

The evaluation was based on:

Reduced Compile Time

Overall Effort

Performance

Look n Feel

Support/Documentation

Extendability

Widget Set

Developer Experience

While JSF did not win in every category it was the overall winner by the team and the client.

Given our time constraints it was difficult to determine which framework had better performance.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s