Originally posted by Marco Ehrentreich:
what do you think how high is the learning curve for Wicket in contrast to other existing frameworks? A first look at it gives the impression it may be a lot easier to learn than for example Spring, JSF, Seam and all the others. Do you think this is true?
Is it furthermore possible to integrate existing knowledge and technologies like the Java persistence API for example? Or is it bound to Wicket specific technologies?
You know, about 400 Pages isn't too much and a lot of other frameworks are so complex that you soon realize you should have read dozens of other books to be able to actually use the framework or technology.
I think this is really frustrating and of course some technologies just are so complex that it's really no possible to get all information from one book or tutorial.
Can you confirm this first impression regarding your personal experience with it?
Originally posted by Marco Ehrentreich:
a lot of other frameworks are so complex that you soon realize you should have read dozens of other books to be able to actually use the framework or technology.
Visit my blog: http://jnassef.blogspot.com/