Actually, I tried Wicket a couple of times. It is very similar to
JSF but lacks the low-level features (phase listeners, etc.) that
component developers require. But, as an end-user framework, it
allows one to get the job done quickly.
Now, before the rifers burn me at the stake, the fact that I am
still with RIFE after looking at Tapestry, JSF, Wicket and Echo --
all component-based frameworks -- says a lot.
Hi Eddy,
I'd be very interested to get your view on why you prefer to stick
with RIFE after having tried out all these others. Particularly in
the light of some comparison evaluations that will be performed by a
large company next week.
Best regards,
Geert
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
